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.11 by pjm2, Sat Mar 17 20:29:44 2001 UTC vs.
Revision 1.24 by tdb, Tue Jul 10 08:54:30 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 >        <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>
24  
25         <p align="justify">
26 <        The i-scream Distributed Central Monitoring System <a href="http://raptor.ukc.ac.uk/~pjm2/reports">Reports</a>
27 <        are now visible on the web.  You may view the latest information
28 <        about each machine, historical 24-hour reports and alerts for
29 <        each machine.  Please remember that this is work in progress
30 <        still, so the only data currently viewable is our own data that
31 <        has been harvested by our own testing.  Also note that historical
32 <        reports are only available for periods during which our server
33 <        was running.
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 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>
38  
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 (viewable in a web browser).  Realtime
46 <        clients are also currently being developed - one Java Swing GUI
47 <        version and also a command line version that can run in a terminal
44 <        window. Alerting mechanisms are being put in place to complete the
45 <        i-scream system.
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>
49        
50         <p align="justify">
51 <        Builds of the i-scream Distributed Central Monitoring System
52 <        are now available for <a href="/builds/">download</a> from this
53 <        website. These are still very much in development and should
54 <        only be used by people who have been in communication with the
55 <        development team.
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>
59  
60         <p>&nbsp;</p>
61         <center><h3>Project Completion</h3></center>
62  
63         <p align="justify">
64 <        The project deadline is 4pm on 29 March. As such, we plan to
65 <        complete the coding process by (at the latest) the end of the
66 <        project week (26/2 - 2/3). This allows time for documentation
67 <        to be tidied up and completed, and printing of the project.
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>
78        
79         <p align="justify">
80 <        As can be seen in the "problem domain" document, the project
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 believe a demonstration to the "customer" is important. We
84 <        plan to do this over the next two weeks, and the feedback given
85 <        will allow any "last minute" alterations to be completed.
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>
89  
90         <p>&nbsp;</p>
91         <center><h3>Naming History</h3></center>
92  
93         <p align="justify">
94 <        The name <b>i-scream</b> arose from a meeting whereupon one member
95 <        of our group randomly chose to draw an ice cream on the white board.
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 <b>i-scream</b>. And thus, we were left with a cunning
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">
107 <        
107 >      
108 >       <p>&nbsp;</p>
109 >       <center><h3>Searching</h3></center>
110 >      
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 -->
128 >      
129         </p>
130         </font>
131        </td>

Diff Legend

Removed lines
+ Added lines
< Changed lines
> Changed lines