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.10 by pjm2, Thu Mar 8 22:37:32 2001 UTC vs.
Revision 1.13 by pjm2, Fri May 25 17:27:40 2001 UTC

# Line 13 | Line 13
13         <center><h3>Current Status</h3></center>
14  
15         <p align="justify">
16 <        Most i-scream components are now functioning to initial
17 <        design parameters and data can now be passed through the
18 <        system and displayed successfully. Documentation is still
19 <        being generated, to allow for future development of the
20 <        i-scream project. Detailed information can usually be
21 <        found in the meeting minutes. Code is viewable via CVS
22 <        to UKC users only.
16 >        All i-scream components are now functioning to initial
17 >        design parameters and our system is regarded to be complete.
18 >        Documentation is available to assist third party programmers
19 >        in producing Hosts for use with the i-scream server.
20 >        Our progress during the project can be found in the meeting minutes.
21 >        Code is viewable via CVS to UKC users only.
22         </p>
23  
24         <p align="justify">
25          The i-scream Distributed Central Monitoring System <a href="http://raptor.ukc.ac.uk/~pjm2/reports">Reports</a>
26 <        are now visible on the web.  You may view all reports
27 <        available for each day, but please remember that this is
28 <        work in progress still, so the only data currently viewable
29 <        is our own data that has been harvested by our own testing.
26 >        are now visible on the web.  You may view the latest information
27 >        about each machine, historical 24-hour reports and alerts for
28 >        each machine.  Please remember that this is work in progress
29 >        still, so the only data currently viewable is our own data that
30 >        has been harvested by our own testing.  Also note that historical
31 >        reports are only available for periods during which our server
32 >        was running.
33 >       </p>
34  
35         <p align="justify">
36          Our current host development allows us to pass machine statistics
37          to our distributed filter arrangement, which then processes the
38          data and stores it for later use.  An example of such use is the
39          historical report generator which produces graphs of machine
40 <        usage over periods of time (viewable in a web browser).  Realtime
41 <        clients are also currently being developed - one Java Swing GUI
42 <        version and also a command line version that can run in a terminal
40 <        window. Alerting mechanisms are being put in place to complete the
41 <        i-scream system.
40 >        usage over periods of time.  A real-time
41 >        client is also available (Conient) and alert information can be
42 >        displayed to the public via dynamic web pages.
43         </p>
44        
45         <p align="justify">
46          Builds of the i-scream Distributed Central Monitoring System
47 <        are now available for <a href="/builds/">download</a> from this
48 <        website. These are still very much in development, are should
47 >        are now available for <a href="/downloads/">download</a> from this
48 >        website. These are still very much in development and should
49          only be used by people who have been in communication with the
50 <        development team.
50 >        development team. Please email us if you wish to use any i-scream
51 >        software, as we are interested to know who is using it and we may
52 >        be able to help you out with any problems you encounter.
53         </p>
54  
55         <p>&nbsp;</p>
56         <center><h3>Project Completion</h3></center>
57  
58         <p align="justify">
59 <        The project deadline is 4pm on 29 March. As such, we plan to
60 <        complete the coding process by (at the latest) the end of the
61 <        project week (26/2 - 2/3). This allows time for documentation
62 <        to be tidied up and completed, and printing of the project.
59 >        The project deadline was 4pm on 29 March 2001. Most of the group
60 >        met very early that morning to compile the project into five
61 >        lever arch folders. The project, consisting of source code, user,
62 >        maintenance and other documents, was handed in at 3pm.  The CVS
63 >        repository was tagged to signify the project's completion, however,
64 >        development and enhancements to the system shall be continued
65 >        in the near future.
66         </p>
67        
68         <p align="justify">
69          As can be seen in the "problem domain" document, the project
70          was aimed at the UKC Computer Science department, and as such
71 <        we believe a demonstration to the "customer" is important. We
72 <        plan to do this over the next two weeks, and the feedback given
73 <        will allow any "last minute" alterations to be completed.
71 >        we believe a demonstration to the "customer" is important. The
72 >        feedback from our demonstation was more positive than we had
73 >        anticipated. We believe that our project may now be of great
74 >        interest to anybody who wishes to monitor a number of machines
75 >        on their network using a central configuration.
76         </p>
77  
78         <p>&nbsp;</p>

Diff Legend

Removed lines
+ Added lines
< Changed lines
> Changed lines