ViewVC logotype

Contents of /web/www/contents.inc

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

Revision 1.14 - (show annotations)
Sun May 27 18:39:31 2001 UTC (18 years, 2 months ago) by pjm2
Branch: MAIN
Changes since 1.13: +38 -27 lines
Quite an overhaul of the main homepage contents as they were a little out
of date (so quickly!).  Put in a lot more links to the important things of
the project - who we are, documents, screenshots etc.  Also added a few of
the screenshots to make the page try and look at least a little bit more
exciting.  Also fixed some badass HTML (! -> ")

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 <img src="screenshots/thumbnail-winhost-main.gif" width="100" height="62" align="left">
17 All i-scream components now function to initial
18 design parameters and our system is regarded to be complete.
19 <b><a href="worddocs/">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 users only.
23 </p>
25 <p align="justify">
26 <img src="screenshots/thumbnail-reports-raptor-load15.gif" width="100" height="107" align="right">
27 The i-scream Distributed Central Monitoring System <a href="http://raptor.ukc.ac.uk/~pjm2/reports">Reports</a>
28 are now visible on the web. If you are <b>not</b> a local user, then you may
29 view some of the output in the <b><a href="screenshots/">screenshots</a></b> section.
30 You may view the latest information about each machine, historical 24-hour
31 reports and alerts for each machine. Our own i-scream server is running constantly,
32 along with several hosts to enable plenty of data harvesting. If you would
33 like your i-scream web reports to be linked from this site, then please email us
34 at <a href="mailto:dev@i-scream.org.uk">dev@i-scream.org.uk</a>
35 </p>
37 <p align="justify">
38 <img src="screenshots/thumbnail-conient-main.gif" width="100" height="107" align="left">
39 Our current host development allows us to pass machine statistics
40 to our distributed filter arrangement, which then processes the
41 data and stores it for later use. An example of such use is the
42 historical report generator which produces graphs of machine
43 usage over periods of time. A real-time
44 client is also available (Conient) and alert information can be
45 displayed to the public via dynamic web pages.
46 </p>
48 <p align="justify">
49 <img src="screenshots/thumbnail-alerter-email.gif" width="100" height="107" align="right">
50 The latest builds of the i-scream Distributed Central Monitoring System
51 are now available for <b><a href="/downloads/">download</a></b> from this
52 website. To assist in our addition of features to the system, we
53 would be extremely grateful to receive feedback from anybody who has
54 any comments about the system. You may email the development team
55 at <a href="mailto:dev@i-scream.org.uk">dev@i-scream.org.uk</a>
56 </p>
58 <p>&nbsp;</p>
59 <center><h3>Project Completion</h3></center>
61 <p align="justify">
62 <img src="screenshots/thumbnail-reports-raptor-latest-misc.gif" width="100" height="104" align="left">
63 The i-scream Distributed Central Monitoring System started off as
64 a final year project for a group of <a href="http://www.cs.ukc.ac.uk">Computer Science</a> students at
65 the <a href="http://www.ukc.ac.uk">University of Kent at Canterbury</a>, UK.
66 The project deadline was 4pm on 29th March 2001. Most of the group
67 met very early that morning to compile the project into five
68 lever arch folders. The project, consisting of source code, user,
69 maintenance and other documents, was handed in at 3pm. The CVS
70 repository was tagged to signify the project's completion, however,
71 the project is still being developed by the <a href="acknowledgments.shtml">core development team</a>
72 as we have found the system to be very useful in practice. We would
73 love to hear of ideas for extra features that we may include in the
74 next builds.
75 </p>
77 <p align="justify">
78 <img src="screenshots/thumbnail-ihost-main.gif" width="100" height="51" align="right">
79 As can be seen in our &quot;<a href="worddocs/">problem domain</a>&quot; document, the project
80 was aimed at the UKC Computer Science department, and as such
81 we believed that a demonstration to the &quotcustomer&quot was important. The
82 feedback from our demonstation was more positive than we had
83 anticipated. We believe that the system may now be of great
84 interest to anybody who wishes to monitor a number of machines
85 on their network using a central configuration.
86 </p>
88 <p>&nbsp;</p>
89 <center><h3>Naming History</h3></center>
91 <p align="justify">
92 <img src="screenshots/thumbnail-conient-config.gif" width="100" height="48" align="left">
93 The name <i>i-scream</i> arose from a meeting whereupon one member
94 of the <a href="acknowledgements.shtml">development team</a> felt a strange urge to draw an ice cream on the discussion board.
95 It later became apparent that we had no name for our project (other
96 than 'The Project'). It seemed only natural to name our project after
97 the ice cream that had been oh-so-randomly drawn on the white board.
98 Copyright issues immediately ruled out anything involving Mr Whippy,
99 so we had to settle for <i>i-scream</i>. And thus, we were left with a cunning
100 play on words - it still sounded like <i>ice cream</i>, yet also
101 served as a functional decription of our system - namely, one which
102 screams at somebody if something has gone wrong...
103 </p>
104 <p align="justify">
106 </p>
107 </font>
108 </td>
109 </tr>
110 </table>

  ViewVC Help
Powered by ViewVC 1.1.26