/[i-scream]/web/www/contents.inc
ViewVC logotype

Diff of /web/www/contents.inc

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

revision 1.13 by pjm2, Fri May 25 17:27:40 2001 UTC revision 1.14 by pjm2, Sun May 27 18:39:31 2001 UTC
# Line 13  Line 13 
13         <center><h3>Current Status</h3></center>         <center><h3>Current Status</h3></center>
14    
15         <p align="justify">         <p align="justify">
16          All i-scream components are now functioning to initial          <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.          design parameters and our system is regarded to be complete.
19          Documentation is available to assist third party programmers          <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.          in producing Hosts for use with the i-scream server.
21          Our progress during the project can be found in the meeting minutes.          Our progress during the project can be found in the meeting minutes.
22          Code is viewable via CVS to UKC users only.          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>         </p>
24    
25         <p align="justify">         <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>          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.  You may view the latest information          are now visible on the web.  If you are <b>not</b> a local user, then you may
29          about each machine, historical 24-hour reports and alerts for          view some of the output in the <b><a href="screenshots/">screenshots</a></b> section.
30          each machine.  Please remember that this is work in progress          You may view the latest information about each machine, historical 24-hour
31          still, so the only data currently viewable is our own data that          reports and alerts for each machine.  Our own i-scream server is running constantly,
32          has been harvested by our own testing.  Also note that historical          along with several hosts to enable plenty of data harvesting.  If you would
33          reports are only available for periods during which our server          like your i-scream web reports to be linked from this site, then please email us
34          was running.          at <a href="mailto:dev@i-scream.org.uk">dev@i-scream.org.uk</a>
35         </p>         </p>
36    
37         <p align="justify">         <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          Our current host development allows us to pass machine statistics
40          to our distributed filter arrangement, which then processes the          to our distributed filter arrangement, which then processes the
41          data and stores it for later use.  An example of such use is the          data and stores it for later use.  An example of such use is the
# Line 43  Line 46 
46         </p>         </p>
47                
48         <p align="justify">         <p align="justify">
49          Builds of the i-scream Distributed Central Monitoring System          <img src="screenshots/thumbnail-alerter-email.gif" width="100" height="107" align="right">
50          are now available for <a href="/downloads/">download</a> from this          The latest builds of the i-scream Distributed Central Monitoring System
51          website. These are still very much in development and should          are now available for <b><a href="/downloads/">download</a></b> from this
52          only be used by people who have been in communication with the          website.  To assist in our addition of features to the system, we
53          development team. Please email us if you wish to use any i-scream          would be extremely grateful to receive feedback from anybody who has
54          software, as we are interested to know who is using it and we may          any comments about the system.  You may email the development team
55          be able to help you out with any problems you encounter.          at <a href="mailto:dev@i-scream.org.uk">dev@i-scream.org.uk</a>
56         </p>         </p>
57    
58         <p>&nbsp;</p>         <p>&nbsp;</p>
59         <center><h3>Project Completion</h3></center>         <center><h3>Project Completion</h3></center>
60    
61         <p align="justify">         <p align="justify">
62          The project deadline was 4pm on 29 March 2001. Most of the group          <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          met very early that morning to compile the project into five
68          lever arch folders. The project, consisting of source code, user,          lever arch folders.  The project, consisting of source code, user,
69          maintenance and other documents, was handed in at 3pm.  The CVS          maintenance and other documents, was handed in at 3pm.  The CVS
70          repository was tagged to signify the project's completion, however,          repository was tagged to signify the project's completion, however,
71          development and enhancements to the system shall be continued          the project is still being developed by the <a href="acknowledgments.shtml">core development team</a>
72          in the near future.          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>         </p>
76                
77         <p align="justify">         <p align="justify">
78          As can be seen in the "problem domain" document, the project          <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          was aimed at the UKC Computer Science department, and as such
81          we believe a demonstration to the "customer" is important. The          we believed that a demonstration to the &quotcustomer&quot was important. The
82          feedback from our demonstation was more positive than we had          feedback from our demonstation was more positive than we had
83          anticipated. We believe that our project may now be of great          anticipated. We believe that the system may now be of great
84          interest to anybody who wishes to monitor a number of machines          interest to anybody who wishes to monitor a number of machines
85          on their network using a central configuration.          on their network using a central configuration.
86         </p>         </p>
# Line 79  Line 89 
89         <center><h3>Naming History</h3></center>         <center><h3>Naming History</h3></center>
90    
91         <p align="justify">         <p align="justify">
92          The name <b>i-scream</b> arose from a meeting whereupon one member          <img src="screenshots/thumbnail-conient-config.gif" width="100" height="48" align="left">
93          of our group randomly chose to draw an ice cream on the white board.          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          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          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.          the ice cream that had been oh-so-randomly drawn on the white board.
98          Copyright issues immediately ruled out anything involving Mr Whippy,          Copyright issues immediately ruled out anything involving Mr Whippy,
99          so we had to settle for <b>i-scream</b>. And thus, we were left with a cunning          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          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          served as a functional decription of our system - namely, one which
102          screams at somebody if something has gone wrong...          screams at somebody if something has gone wrong...

Legend:
Removed from v.1.13  
changed lines
  Added in v.1.14

  ViewVC Help
Powered by ViewVC 1.1.26