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.25 by tdb, Wed Oct 24 10:37:25 2001 UTC vs.
Revision 1.28 by tdb, Sat Feb 9 15:00:42 2002 UTC

# Line 1 | Line 1
1  
2   <!--
3 <    contents.inc
4 <    Created by pjm2 14/10/2000
5 <    Last edited 16/01/2001
3 >    $Author$
4 >    $Id$
5   -->
6  
7      <table border="0" width="500">
# Line 10 | Line 9
9        <td>
10         <font size="2" face="arial,sans-serif">
11        
12 <       <center><h3>Current Status</h3></center>
13 <
12 >       <center><h3>Project News</h3></center>
13 >      
14         <p align="justify">
15 <        <a href="screenshots/"><img border="0" src="screenshots/thumbnail-reports-raptor-load15.gif" width="100" height="107" align="left"></a>
16 <        All i-scream components now function to initial
17 <        design parameters and our system is regarded to be complete.
18 <        <b><a href="documentation/">Documentation</a></b> 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.
22 <        Code is viewable via <a href="cvs.shtml">CVS</a>.
15 >        <b>Thursday 7 Feb 2002</b><br><br>
16 >        The alerting section of the i-scream monitoring system now makes
17 >        full use of an externally developed IRC bot for it's IRC
18 >        connectivity. To find out more about this IRC bot, please visit
19 >        the authors website at <a href="http://www.jibble.org">
20 >        http://www.jibble.org</a>.
21         </p>
22 <
22 >      
23         <p align="justify">
24 <        <a href="screenshots/"><img border="0" src="screenshots/thumbnail-winhost-main.gif" width="100" height="62" align="right"></a>
25 <        
26 <        The i-scream Distributed Central Monitoring System Reports
27 <        are now visible on the web.  If you are <b>not</b> a local user, then you may
28 <        view some of the output in the <b><a href="screenshots/">screen shots</a></b> section or you may view some
29 <        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>
24 >        <b>Tuesday 8 Jan 2002</b><br><br>
25 >        Java ACL (Access Control List) code has been added to the util
26 >        package of the i-scream server. This code will ultimately allow
27 >        the server to be more secure when exposed to the Internet. More
28 >        details can be found <a href="http://www.cs.ukc.ac.uk/people/staff/tdb/#acl">
29 >        here</a> on the authors website.
30         </p>
31 <
31 >      
32         <p align="justify">
33 <        <a href="screenshots/"><img border="0" src="screenshots/thumbnail-conient-main.gif" width="100" height="107" align="left"></a>
34 <        Our current host development allows us to pass machine statistics
35 <        to our distributed filter arrangement, which then processes the
36 <        data and stores it for later use.  An example of such use is the
37 <        historical report generator which produces graphs of machine
38 <        usage over periods of time.  A real-time
39 <        client is also available (Conient) and alert information can be
47 <        displayed to the public via dynamic web pages.
33 >        <b>Tuesday 18 Dec 2001</b><br><br>
34 >        The i-scream ihost package has undergone significant changes to
35 >        make it more flexible and modular. It now incorporates plugins
36 >        which can be written in any language, and automatically XML
37 >        encodes data it is given (as opposed to the hardcoded approach
38 >        in the old version). It has also been made more robust, and
39 >        where possible optimised to reduce the load on the host system.
40         </p>
41        
42 +       <p>&nbsp;</p>
43 +       <center><h3>About i-scream</h3></center>
44 +      
45         <p align="justify">
46 <        <a href="screenshots/"><img border="0" src="screenshots/thumbnail-alerter-email.gif" width="100" height="107" align="right"></a>
47 <        The latest builds of the i-scream Distributed Central Monitoring System
48 <        are now available for <b><a href="/downloads/">download</a></b> from this
49 <        website.  To assist in our addition of features to the system, we
50 <        would be extremely grateful to receive feedback from anybody who has
51 <        any comments about the system.  You may email the development team
52 <        at <a href="mailto:dev@i-scream.org.uk">dev@i-scream.org.uk</a>
46 >        <a href="screenshots/"><img border="0" src="screenshots/thumbnail-alerter-email.gif" width="100" height="107" align="left"></a>
47 >        Details of the i-scream central monitoring system can be found
48 >        on the <b><a href="features.shtml">features and overview</a></b> page.
49 >        A variety of <b><a href="screenshots">screen shots</a></b> from the
50 >        system show some of the key features in use. The <b><a href="reports">reports demo</a></b>
51 >        page provides a static example of what the i-scream reports (alerts,
52 >        historical graphs, and live data) could look like on a production system.
53         </p>
54 <
54 >      
55 >       <p align="justify">
56 >        <a href="screenshots/"><img border="0" src="screenshots/thumbnail-conient-main.gif" width="100" height="107" align="right"></a>
57 >        The latest source code is available in the <b><a href="cvs.shtml">CVS</a></b>
58 >        repository, with binary downloads on the downloads page. The
59 >        <b><a href="documentation">documentation</a></b> page has details of
60 >        installation, use and maintenance for the end user and developer.
61 >        We value feedback and comments from you, so please drop us an e-mail
62 >        to <a href="mailto:dev@i-scream.org.uk">dev@i-scream.org.uk</a>.
63 >       </p>
64 >      
65         <p>&nbsp;</p>
66 <       <center><h3>Project Completion</h3></center>
66 >       <center><h3>Current Work</h3></center>
67 >      
68 >       <p align="justify">
69 >        <b>Historical/Realtime graphing package</b><br><br>
70 >        <a href="screenshots/"><img border="0" src="screenshots/thumbnail-reports-raptor-load15.gif" width="100" height="107" align="left"></a>
71 >        The current system for graphing i-scream data  from the i-scream
72 >        system is good, but proving to be unscalable and very resource
73 >        hungry. This is mostly due to the MySQL database backend,
74 >        and the vast quantity of data recorded. The new system
75 >        in development makes use of <a href="http://rrdtool.eu.org/">
76 >        RRDtool</a> to generate the graphs in realtime. This reduces
77 >        the peak loads of the system, and allows generation of more
78 >        flexible graphs. This work is nearing completetion.
79 >       </p>
80 >      
81 >       <p align="justify">
82 >        <b>Server security</b><br><br>
83 >        Security was something mostly overlooked in the original stage
84 >        of this project (due to the academic nature of the work). However,
85 >        once in production use this has become an issue, and is being
86 >        addressed. Initially the plan is to lock down the external points
87 >        of access (TCP & UDP) in the server to specific hosts. In the
88 >        longer term, encryption of data would be nice, but would take a
89 >        lot more time and work.
90 >       </p>
91 >      
92 >       <p align="justify">
93 >        <b>Testing and Development</b><br><br>
94 >        <a href="screenshots/"><img border="0" src="screenshots/thumbnail-winhost-main.gif" width="100" height="62" align="right"></a>
95 >        The i-scream system is being tested and developed within the
96 >        Univeristy of Kent Computer Science department by the Systems
97 >        Group. This has led to many bug fixes and minor feature
98 >        enhancements, and will hopefully help to aid the long term
99 >        development of the system.
100 >       </p>
101 >      
102 >       <p>&nbsp;</p>
103 >       <center><h3>Project History</h3></center>
104  
105         <p align="justify">
106          <a href="screenshots/"><img border="0" src="screenshots/thumbnail-reports-raptor-latest-misc.gif" width="100" height="104" align="left"></a>
107          The i-scream Distributed Central Monitoring System started off as
108 <        a final year project for a group of <a href="http://www.cs.ukc.ac.uk">Computer Science</a> students at
109 <        the <a href="http://www.ukc.ac.uk">University of Kent at Canterbury</a>, UK.
110 <        The project deadline was 4pm on 29th March 2001.  Most of the group
111 <        met very early that morning to compile the project into five
112 <        lever arch folders.  The project, consisting of source code, user,
113 <        maintenance and other documents, was handed in at 3pm.  The CVS
114 <        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.
108 >        a final year project for a group of <a href="http://www.cs.ukc.ac.uk">
109 >        Computer Science</a> students at the <a href="http://www.ukc.ac.uk">
110 >        University of Kent at Canterbury</a>, UK. The project was completed at
111 >        4pm on 29 March 2001. It consisted of five lever-arch folders containing
112 >        mostly source code and documentation. The CVS repository was tagged to
113 >        signify this even, however, the project is still being developed by the
114 >        <a href="acknowledgements.shtml">core development team</a>.
115         </p>
116        
117         <p align="justify">
# Line 82 | Line 120
120          was aimed at the UKC Computer Science department, and as such
121          we believed that a demonstration to the &quot;customer&quot; was important. The
122          feedback from our demonstation was more positive than we had
123 <        anticipated. We believe that the system may now be of great
124 <        interest to anybody who wishes to monitor a number of machines
125 <        on their network using a central configuration.
123 >        anticipated. We believe that the system may now be of interest
124 >        to anybody who wishes to monitor a number of machines on their
125 >        network using a central configuration. The i-scream central
126 >        monitoring system is now being used by the UKC Computer Science
127 >        department, and their feedback is being used to further improve
128 >        the product.
129         </p>
130  
90       <p>&nbsp;</p>
91       <center><h3>Naming History</h3></center>
92
131         <p align="justify">
132          <a href="screenshots/"><img border="0" src="screenshots/thumbnail-conient-config.gif" width="100" height="48" align="left"></a>
133          The name <i>i-scream</i> arose from a meeting whereupon one member
# Line 100 | Line 138
138          Copyright issues immediately ruled out anything involving Mr Whippy,
139          so we had to settle for <i>i-scream</i>. And thus, we were left with a cunning
140          play on words - it still sounded like <i>ice cream</i>, yet also
141 <        served as a functional decription of our system - namely, one which
141 >        served as a functional description of our system - namely, one which
142          screams at somebody if something has gone wrong...
143         </p>
144         <p align="justify">
145        
146         <p>&nbsp;</p>
147 <       <center><h3>Searching</h3></center>
147 >       <center><h3>Searching i-scream</h3></center>
148        
149         <!-- Search Google -->
150         <center>
151 <       <FORM method=GET action=http://www.google.com/custom>
152 <       <TABLE bgcolor=#FFFFFF cellspacing=0 border=0>
153 <       <tr valign=top><td>
154 <       <A HREF=http://www.google.com/search>
155 <       <IMG SRC=http://www.google.com/logos/Logo_40wht.gif border=0 ALT=Google align=middle width="128" height="53"></A>
156 <       </td>
157 <       <td>
158 <       <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>
159 <       <INPUT TYPE=text name=q size=35 maxlength=255 value="">
160 <       <INPUT type=submit name=sa VALUE="Search">
161 <       <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;">
162 <       </td></tr></TABLE>
163 <       </FORM>
151 >        <FORM method=GET action=http://www.google.com/custom>
152 >         <TABLE bgcolor=#FFFFFF cellspacing=0 border=0>
153 >          <tr>
154 >           <td valign="middle">
155 >            <A HREF=http://www.google.com/search>
156 >            <IMG SRC=http://www.google.com/logos/Logo_40wht.gif border=0 ALT=Google align=middle width="128" height="53"></A>
157 >           </td>
158 >           <td valign="middle">
159 >            <input type=hidden name=domains value="i-scream.org.uk">
160 >            <input type=hidden name=sitesearch value="i-scream.org.uk">
161 >            <INPUT TYPE=text name=q size=35 maxlength=255 value="">
162 >            <INPUT type=submit name=sa VALUE="Search">
163 >            <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;">
164 >           </td>
165 >          </tr>
166 >         </TABLE>
167 >        </FORM>
168         </center>
169         <!-- Search Google -->
170        

Diff Legend

Removed lines
+ Added lines
< Changed lines
> Changed lines