ViewVC logotype

Contents of /web/www/contents.inc

Parent Directory Parent Directory | Revision Log Revision Log | View Revision Graph Revision Graph

Revision 1.24 - (show annotations)
Tue Jul 10 08:54:30 2001 UTC (18 years, 1 month ago) by tdb
Branch: MAIN
Changes since 1.23: +3 -0 lines
Adding a heading for the searching.

2 <!--
3 contents.inc
4 Created by pjm2 14/10/2000
5 Last edited 16/01/2001
6 -->
8 <table border="0" width="500">
9 <tr>
10 <td>
11 <font size="2" face="arial,sans-serif">
13 <center><h3>Current Status</h3></center>
15 <p align="justify">
16 <a href="screenshots/"><img border="0" src="screenshots/thumbnail-reports-raptor-load15.gif" width="100" height="107" align="left"></a>
17 All i-scream components now function to initial
18 design parameters and our system is regarded to be complete.
19 <b><a href="documentation/">Documentation</a></b> is available to assist third party programmers
20 in producing Hosts for use with the i-scream server.
21 Our progress during the project can be found in the meeting minutes.
22 Code is viewable via <a href="http://raptor.ukc.ac.uk/~tdb1/cgi-bin/viewcvs.cgi">CVS</a> to local users only.
23 </p>
25 <p align="justify">
26 <a href="screenshots/"><img border="0" src="screenshots/thumbnail-winhost-main.gif" width="100" height="62" align="right"></a>
28 The i-scream Distributed Central Monitoring System Reports
29 are now visible on the web. If you are <b>not</b> a local user, then you may
30 view some of the output in the <b><a href="screenshots/">screen shots</a></b> section or you may view some
31 static example content on the <a href="reports/"><b>Reports Demo</b></a> pages.
32 You may view the latest information about each machine, historical 24-hour
33 reports and alerts for each machine. Our own i-scream server is running constantly,
34 along with several hosts to enable plenty of data harvesting. If you would
35 like your i-scream web reports to be linked from this site, then please email us
36 at <a href="mailto:dev@i-scream.org.uk">dev@i-scream.org.uk</a>
37 </p>
39 <p align="justify">
40 <a href="screenshots/"><img border="0" src="screenshots/thumbnail-conient-main.gif" width="100" height="107" align="left"></a>
41 Our current host development allows us to pass machine statistics
42 to our distributed filter arrangement, which then processes the
43 data and stores it for later use. An example of such use is the
44 historical report generator which produces graphs of machine
45 usage over periods of time. A real-time
46 client is also available (Conient) and alert information can be
47 displayed to the public via dynamic web pages.
48 </p>
50 <p align="justify">
51 <a href="screenshots/"><img border="0" src="screenshots/thumbnail-alerter-email.gif" width="100" height="107" align="right"></a>
52 The latest builds of the i-scream Distributed Central Monitoring System
53 are now available for <b><a href="/downloads/">download</a></b> from this
54 website. To assist in our addition of features to the system, we
55 would be extremely grateful to receive feedback from anybody who has
56 any comments about the system. You may email the development team
57 at <a href="mailto:dev@i-scream.org.uk">dev@i-scream.org.uk</a>
58 </p>
60 <p>&nbsp;</p>
61 <center><h3>Project Completion</h3></center>
63 <p align="justify">
64 <a href="screenshots/"><img border="0" src="screenshots/thumbnail-reports-raptor-latest-misc.gif" width="100" height="104" align="left"></a>
65 The i-scream Distributed Central Monitoring System started off as
66 a final year project for a group of <a href="http://www.cs.ukc.ac.uk">Computer Science</a> students at
67 the <a href="http://www.ukc.ac.uk">University of Kent at Canterbury</a>, UK.
68 The project deadline was 4pm on 29th March 2001. Most of the group
69 met very early that morning to compile the project into five
70 lever arch folders. The project, consisting of source code, user,
71 maintenance and other documents, was handed in at 3pm. The CVS
72 repository was tagged to signify the project's completion, however,
73 the project is still being developed by the <a href="acknowledgements.shtml">core development team</a>
74 as we have found the system to be very useful in practice. We would
75 love to hear of ideas for extra features that we may include in the
76 next builds.
77 </p>
79 <p align="justify">
80 <a href="screenshots/"><img border="0" src="screenshots/thumbnail-ihost-main.gif" width="100" height="51" align="right"></a>
81 As can be seen in our &quot;<a href="/probdomain.shtml">problem domain</a>&quot; document, the project
82 was aimed at the UKC Computer Science department, and as such
83 we believed that a demonstration to the &quot;customer&quot; was important. The
84 feedback from our demonstation was more positive than we had
85 anticipated. We believe that the system may now be of great
86 interest to anybody who wishes to monitor a number of machines
87 on their network using a central configuration.
88 </p>
90 <p>&nbsp;</p>
91 <center><h3>Naming History</h3></center>
93 <p align="justify">
94 <a href="screenshots/"><img border="0" src="screenshots/thumbnail-conient-config.gif" width="100" height="48" align="left"></a>
95 The name <i>i-scream</i> arose from a meeting whereupon one member
96 of the <a href="acknowledgements.shtml">development team</a> felt a strange urge to draw an ice cream on the discussion board.
97 It later became apparent that we had no name for our project (other
98 than 'The Project'). It seemed only natural to name our project after
99 the ice cream that had been oh-so-randomly drawn on the white board.
100 Copyright issues immediately ruled out anything involving Mr Whippy,
101 so we had to settle for <i>i-scream</i>. And thus, we were left with a cunning
102 play on words - it still sounded like <i>ice cream</i>, yet also
103 served as a functional decription of our system - namely, one which
104 screams at somebody if something has gone wrong...
105 </p>
106 <p align="justify">
108 <p>&nbsp;</p>
109 <center><h3>Searching</h3></center>
111 <!-- Search Google -->
112 <center>
113 <FORM method=GET action=http://www.google.com/custom>
114 <TABLE bgcolor=#FFFFFF cellspacing=0 border=0>
115 <tr valign=top><td>
116 <A HREF=http://www.google.com/search>
117 <IMG SRC=http://www.google.com/logos/Logo_40wht.gif border=0 ALT=Google align=middle width="128" height="53"></A>
118 </td>
119 <td>
120 <font face=arial,sans-serif size=-1><input type=hidden name=domains value="i-scream.org.uk"><input type=radio name=sitesearch value="i-scream.org.uk" checked> search i-scream <input type=radio name=sitesearch value=""> search google </font><br>
121 <INPUT TYPE=text name=q size=35 maxlength=255 value="">
122 <INPUT type=submit name=sa VALUE="Search">
123 <INPUT type=hidden name=cof VALUE="T:#000066;LW:502;ALC:#3333cc;L:http://www.i-scream.org.uk/i-scream.gif;LC:#0000ff;LH:37;BGC:#ffffff;AH:left;VLC:#3333cc;AWFID:d646a9fd69e7d9cb;">
124 </td></tr></TABLE>
125 </FORM>
126 </center>
127 <!-- Search Google -->
129 </p>
130 </font>
131 </td>
132 </tr>
133 </table>

  ViewVC Help
Powered by ViewVC 1.1.26