ViewVC Help
View File | Revision Log | Show Annotations | Revision Graph | Root Listing
root/i-scream/web/www/contents.inc
(Generate patch)

Comparing web/www/contents.inc (file contents):
Revision 1.12 by pjm2, Fri Mar 30 08:08:46 2001 UTC vs.
Revision 1.20 by pjm2, Mon May 28 11:55:57 2001 UTC

# Line 13 | Line 13
13         <center><h3>Current Status</h3></center>
14  
15         <p align="justify">
16 <        All i-scream components are now functioning to initial
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 <        Documentation is available to assist third party programmers
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 CVS to UKC users only.
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>
24  
25         <p align="justify">
26 +        <a href="screenshots/"><img border="0" src="screenshots/thumbnail-winhost-main.gif" width="100" height="62" align="right"></a>
27 +        
28          The i-scream Distributed Central Monitoring System <a href="http://raptor.ukc.ac.uk/~pjm2/reports">Reports</a>
29 <        are now visible on the web.  You may view the latest information
30 <        about each machine, historical 24-hour reports and alerts for
31 <        each machine.  Please remember that this is work in progress
32 <        still, so the only data currently viewable is our own data that
33 <        has been harvested by our own testing.  Also note that historical
34 <        reports are only available for periods during which our server
35 <        was running.
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/">screenshots</a></b> section.
31 >        You may view the latest information about each machine, historical 24-hour
32 >        reports and alerts for each machine.  Our own i-scream server is running constantly,
33 >        along with several hosts to enable plenty of data harvesting.  If you would
34 >        like your i-scream web reports to be linked from this site, then please email us
35 >        at <a href="mailto:dev@i-scream.org.uk">dev@i-scream.org.uk</a>
36         </p>
37  
38         <p align="justify">
39 +        <a href="screenshots/"><img border="0" src="screenshots/thumbnail-conient-main.gif" width="100" height="107" align="left"></a>
40          Our current host development allows us to pass machine statistics
41          to our distributed filter arrangement, which then processes the
42          data and stores it for later use.  An example of such use is the
# Line 43 | Line 47
47         </p>
48        
49         <p align="justify">
50 <        Builds of the i-scream Distributed Central Monitoring System
51 <        are now available for <a href="/builds/">download</a> from this
52 <        website. These are still very much in development and should
53 <        only be used by people who have been in communication with the
54 <        development team. Please email us if you wish to use any i-scream
55 <        software, as we are interested to know who is using it and we may
56 <        be able to help you out with any problems you encounter.
50 >        <a href="screenshots/"><img border="0" src="screenshots/thumbnail-alerter-email.gif" width="100" height="107" align="right"></a>
51 >        The latest builds of the i-scream Distributed Central Monitoring System
52 >        are now available for <b><a href="/downloads/">download</a></b> from this
53 >        website.  To assist in our addition of features to the system, we
54 >        would be extremely grateful to receive feedback from anybody who has
55 >        any comments about the system.  You may email the development team
56 >        at <a href="mailto:dev@i-scream.org.uk">dev@i-scream.org.uk</a>
57         </p>
58  
59         <p>&nbsp;</p>
60         <center><h3>Project Completion</h3></center>
61  
62         <p align="justify">
63 <        The project deadline was 4pm on 29 March 2001. Most of the group
63 >        <a href="screenshots/"><img border="0" src="screenshots/thumbnail-reports-raptor-latest-misc.gif" width="100" height="104" align="left"></a>
64 >        The i-scream Distributed Central Monitoring System started off as
65 >        a final year project for a group of <a href="http://www.cs.ukc.ac.uk">Computer Science</a> students at
66 >        the <a href="http://www.ukc.ac.uk">University of Kent at Canterbury</a>, UK.
67 >        The project deadline was 4pm on 29th March 2001.  Most of the group
68          met very early that morning to compile the project into five
69 <        lever arch folders. The project, consisting of source code, user,
69 >        lever arch folders.  The project, consisting of source code, user,
70          maintenance and other documents, was handed in at 3pm.  The CVS
71          repository was tagged to signify the project's completion, however,
72 <        development and enhancements to the system shall be continued
73 <        in the near future.
72 >        the project is still being developed by the <a href="acknowledgements.shtml">core development team</a>
73 >        as we have found the system to be very useful in practice.  We would
74 >        love to hear of ideas for extra features that we may include in the
75 >        next builds.
76         </p>
77        
78         <p align="justify">
79 <        As can be seen in the "problem domain" document, the project
79 >        <a href="screenshots/"><img border="0" src="screenshots/thumbnail-ihost-main.gif" width="100" height="51" align="right"></a>
80 >        As can be seen in our &quot;<a href="/probdomain.shtml">problem domain</a>&quot; document, the project
81          was aimed at the UKC Computer Science department, and as such
82 <        we believe a demonstration to the "customer" is important. The
82 >        we believed that a demonstration to the &quotcustomer&quot was important. The
83          feedback from our demonstation was more positive than we had
84 <        anticipated. We believe that our project may now be of great
84 >        anticipated. We believe that the system may now be of great
85          interest to anybody who wishes to monitor a number of machines
86          on their network using a central configuration.
87         </p>
# Line 79 | Line 90
90         <center><h3>Naming History</h3></center>
91  
92         <p align="justify">
93 <        The name <b>i-scream</b> arose from a meeting whereupon one member
94 <        of our group randomly chose to draw an ice cream on the white board.
93 >        <a href="screenshots/"><img border="0" src="screenshots/thumbnail-conient-config.gif" width="100" height="48" align="left"></a>
94 >        The name <i>i-scream</i> arose from a meeting whereupon one member
95 >        of the <a href="acknowledgements.shtml">development team</a> felt a strange urge to draw an ice cream on the discussion board.
96          It later became apparent that we had no name for our project (other
97          than 'The Project'). It seemed only natural to name our project after
98          the ice cream that had been oh-so-randomly drawn on the white board.
99          Copyright issues immediately ruled out anything involving Mr Whippy,
100 <        so we had to settle for <b>i-scream</b>. And thus, we were left with a cunning
100 >        so we had to settle for <i>i-scream</i>. And thus, we were left with a cunning
101          play on words - it still sounded like <i>ice cream</i>, yet also
102          served as a functional decription of our system - namely, one which
103          screams at somebody if something has gone wrong...

Diff Legend

Removed lines
+ Added lines
< Changed lines
> Changed lines