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.18 by tdb, Sun May 27 18:56:24 2001 UTC vs.
Revision 1.36 by tdb, Tue Feb 4 09:33:55 2003 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>
12 >       <center><h3>Project News</h3></center>
13 >      
14 >       <p align="justify">
15 >        <b>Tuesday 4 February 2003</b><br><br>
16 >        Over the coming week we will be making snapshot builds of the
17 >        i-scream central monitoring system from the CVS repository.
18 >        These builds will have quite a few changes from the downloads
19 >        currently available (a document detailing them will be
20 >        released later on), so please give them a whirl. We would be
21 >        grateful if you <a href="mailto:dev@i-scream.org.uk">contacted</a>
22 >        us with any questions or bugs.<br><br>
23 >        The downloads will be available on our snapshot server :-<br>
24 >        <a href="http://snapshots.i-scream.org.uk/">
25 >        http://snapshots.i-scream.org.uk/</a>.
26 >       </p>
27  
28         <p align="justify">
29 <        <a href="screenshots/"><img border="0" src="screenshots/thumbnail-reports-raptor-load15.gif" width="100" height="107" align="left"></a>
30 <        All i-scream components now function to initial
31 <        design parameters and our system is regarded to be complete.
32 <        <b><a href="worddocs/">Documentation</a></b> is available to assist third party programmers
33 <        in producing Hosts for use with the i-scream server.
34 <        Our progress during the project can be found in the meeting minutes.
35 <        Code is viewable via <a href="http://raptor.ukc.ac.uk/~tdb1/cgi-bin/viewcvs.cgi">CVS</a> to local users users only.
29 >        <b>Saturday 1 June 2002</b><br><br>
30 >        Work has now been finished on a new ihost written in C. This has
31 >        been in the pipeline for a long time, and we're glad to finally
32 >        see an efficient native host! Credit goes to our new developer
33 >        <a href="/who.shtml">Pete</a>. Until we update the downloads
34 >        pages you can download the new ihost
35 >        <a href="http://snapshots.i-scream.org.uk/ihost-1.0rc1.tar.gz">
36 >        here</a>.
37         </p>
38  
39         <p align="justify">
40 <        <a href="screenshots/"><img border="0" src="screenshots/thumbnail-winhost-main.gif" width="100" height="62" align="right"></a>
41 <        
42 <        The i-scream Distributed Central Monitoring System <a href="http://raptor.ukc.ac.uk/~pjm2/reports">Reports</a>
43 <        are now visible on the web.  If you are <b>not</b> a local user, then you may
44 <        view some of the output in the <b><a href="screenshots/">screenshots</a></b> section.
45 <        You may view the latest information about each machine, historical 24-hour
46 <        reports and alerts for each machine.  Our own i-scream server is running constantly,
47 <        along with several hosts to enable plenty of data harvesting.  If you would
48 <        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>
40 >        <b>Tuesday 21 May 2002</b><br><br>
41 >        We've finally put the finishing touches to the new
42 >        <a href="http://rrdtool.eu.org">RRDtool</a> based graphing system.
43 >        It's working well, and has done away with the MySQL database
44 >        backend which took up far too many resources. This new system
45 >        generates the graphs in a more realtime nature, allowing more
46 >        flexible graphs to be generated. This is currently only available
47 >        through <a href="http://www.i-scream.org.uk/cgi-bin/cvs/viewcvs.cgi/cms/source/reports/rrdgraphing/">
48 >        CVS</a>.
49         </p>
50  
51         <p align="justify">
52 <        <a href="screenshots/"><img border="0" src="screenshots/thumbnail-conient-main.gif" width="100" height="107" align="left"></a>
53 <        Our current host development allows us to pass machine statistics
54 <        to our distributed filter arrangement, which then processes the
55 <        data and stores it for later use.  An example of such use is the
43 <        historical report generator which produces graphs of machine
44 <        usage over periods of time.  A real-time
45 <        client is also available (Conient) and alert information can be
46 <        displayed to the public via dynamic web pages.
52 >        <b>Saturday 18 May 2002</b><br><br>
53 >        The i-scream central monitoring system is now <a href="/license.shtml">
54 >        licensed</a> under the GNU Public License. We are currently working
55 >        to make full downloads, including source, available on this site.
56         </p>
57 +
58 +       <p align="justify">
59 +        <b>Thursday 7 Feb 2002</b><br><br>
60 +        The alerting section of the i-scream central monitoring system
61 +        now makes full use of an externally developed IRC bot for it's IRC
62 +        connectivity. To find out more about this IRC bot, please visit
63 +        the author's website at <a href="http://www.jibble.org">
64 +        http://www.jibble.org</a>.
65 +       </p>
66        
67         <p align="justify">
68 <        <a href="screenshots/"><img border="0" src="screenshots/thumbnail-alerter-email.gif" width="100" height="107" align="right"></a>
69 <        The latest builds of the i-scream Distributed Central Monitoring System
70 <        are now available for <b><a href="/downloads/">download</a></b> from this
71 <        website.  To assist in our addition of features to the system, we
72 <        would be extremely grateful to receive feedback from anybody who has
73 <        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>
68 >        <b>Tuesday 8 Jan 2002</b><br><br>
69 >        Java ACL (Access Control List) code has been added to the util
70 >        package of the i-scream server. This code will ultimately allow
71 >        the server to be more secure when exposed to the Internet. More
72 >        details can be found <a href="http://www.cs.ukc.ac.uk/people/staff/tdb/#acl">
73 >        here</a> on the author's website.
74         </p>
75 +      
76 +       <p>&nbsp;</p>
77 +       <center><h3>About i-scream</h3></center>
78 +      
79 +       <p align="justify">
80 +        <a href="screenshots/"><img border="0" src="screenshots/thumbnail-alerter-email.gif" width="100" height="107" align="left"></a>
81 +        Details of the i-scream central monitoring system can be found
82 +        on the <b><a href="features.shtml">features and overview</a></b> page.
83 +        A variety of <b><a href="screenshots">screen shots</a></b> from the
84 +        system show some of the key features in use. The <b><a href="reports">reports demo</a></b>
85 +        page provides a static example of what the i-scream reports (alerts,
86 +        historical graphs, and live data) could look like on a production system.
87 +       </p>
88 +      
89 +       <p align="justify">
90 +        <a href="screenshots/"><img border="0" src="screenshots/thumbnail-conient-main.gif" width="100" height="107" align="right"></a>
91 +        The latest source code is available in the <b><a href="cvs.shtml">CVS</a></b>
92 +        repository, with binary downloads on the downloads page. The
93 +        <b><a href="documentation">documentation</a></b> page has details of
94 +        installation, use and maintenance for the end user and developer.
95 +        We value feedback and comments from you, so please drop us an e-mail
96 +        to <a href="mailto:dev@i-scream.org.uk">dev@i-scream.org.uk</a>.
97 +       </p>
98 +      
99 +       <p>&nbsp;</p>
100 +       <center><h3>Current Work</h3></center>
101 +      
102 +       <p align="justify">
103 +        <b>Extending monitoring facilites</b><br><br>
104 +        <a href="screenshots/"><img border="0" src="screenshots/thumbnail-reports-raptor-load15.gif" width="100" height="107" align="left"></a>
105 +        Work is continuing, in conjunction with the new ihost, to extend
106 +        the range of i-scream's monitoring. Currently we are adding new
107 +        features to more accurately monitoring memory and swap usage,
108 +        along with more disk statistics. We are also planning to improve
109 +        the rather basic service monitors which are currently in place.
110 +        There are also many more subtle changes that need to be made to
111 +        improve the reliability and usefulness of i-scream's monitoring.
112 +       </p>
113  
114 +       <p align="justify">
115 +        <b>Server security</b><br><br>
116 +        Security was something mostly overlooked in the original stage
117 +        of this project (due to the academic nature of the work). However,
118 +        once in production use this has become an issue, and is being
119 +        addressed. Initially the plan is to lock down the external points
120 +        of access (TCP & UDP) in the server to specific hosts. In the
121 +        longer term, encryption of data would be nice, but would take a
122 +        lot more time and work.
123 +       </p>
124 +      
125 +       <p align="justify">
126 +        <b>Testing and Development</b><br><br>
127 +        <a href="screenshots/"><img border="0" src="screenshots/thumbnail-winhost-main.gif" width="100" height="62" align="right"></a>
128 +        The i-scream system is being tested and developed within the
129 +        Univeristy of Kent Computer Science department by the Systems
130 +        Group. This has led to many bug fixes and minor feature
131 +        enhancements, and will hopefully help to aid the long term
132 +        development of the system.
133 +       </p>
134 +      
135         <p>&nbsp;</p>
136 <       <center><h3>Project Completion</h3></center>
136 >       <center><h3>Project History</h3></center>
137  
138         <p align="justify">
139          <a href="screenshots/"><img border="0" src="screenshots/thumbnail-reports-raptor-latest-misc.gif" width="100" height="104" align="left"></a>
140          The i-scream Distributed Central Monitoring System started off as
141 <        a final year project for a group of <a href="http://www.cs.ukc.ac.uk">Computer Science</a> students at
142 <        the <a href="http://www.ukc.ac.uk">University of Kent at Canterbury</a>, UK.
143 <        The project deadline was 4pm on 29th March 2001.  Most of the group
144 <        met very early that morning to compile the project into five
145 <        lever arch folders.  The project, consisting of source code, user,
146 <        maintenance and other documents, was handed in at 3pm.  The CVS
147 <        repository was tagged to signify the project's completion, however,
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.
141 >        a final year project for a group of <a href="http://www.cs.ukc.ac.uk">
142 >        Computer Science</a> students at the <a href="http://www.ukc.ac.uk">
143 >        University of Kent at Canterbury</a>, UK. The project was completed at
144 >        4pm on 29 March 2001. It consisted of five lever-arch folders containing
145 >        mostly source code and documentation. The CVS repository was tagged to
146 >        signify this even, however, the project is still being developed by the
147 >        <a href="acknowledgements.shtml">core development team</a>.
148         </p>
149        
150         <p align="justify">
151          <a href="screenshots/"><img border="0" src="screenshots/thumbnail-ihost-main.gif" width="100" height="51" align="right"></a>
152          As can be seen in our &quot;<a href="/probdomain.shtml">problem domain</a>&quot; document, the project
153          was aimed at the UKC Computer Science department, and as such
154 <        we believed that a demonstration to the &quotcustomer&quot was important. The
154 >        we believed that a demonstration to the &quot;customer&quot; was important. The
155          feedback from our demonstation was more positive than we had
156 <        anticipated. We believe that the system may now be of great
157 <        interest to anybody who wishes to monitor a number of machines
158 <        on their network using a central configuration.
156 >        anticipated. We believe that the system may now be of interest
157 >        to anybody who wishes to monitor a number of machines on their
158 >        network using a central configuration. The i-scream central
159 >        monitoring system is now being used by the UKC Computer Science
160 >        department, and their feedback is being used to further improve
161 >        the product.
162         </p>
163  
89       <p>&nbsp;</p>
90       <center><h3>Naming History</h3></center>
91
164         <p align="justify">
165          <a href="screenshots/"><img border="0" src="screenshots/thumbnail-conient-config.gif" width="100" height="48" align="left"></a>
166          The name <i>i-scream</i> arose from a meeting whereupon one member
# Line 99 | Line 171
171          Copyright issues immediately ruled out anything involving Mr Whippy,
172          so we had to settle for <i>i-scream</i>. And thus, we were left with a cunning
173          play on words - it still sounded like <i>ice cream</i>, yet also
174 <        served as a functional decription of our system - namely, one which
174 >        served as a functional description of our system - namely, one which
175          screams at somebody if something has gone wrong...
176         </p>
177         <p align="justify">
178 <        
178 >      
179 >       <p>&nbsp;</p>
180 >       <center><h3>Searching i-scream</h3></center>
181 >      
182 >       <!-- Search Google -->
183 >       <center>
184 >        <FORM method=GET action=http://www.google.com/custom>
185 >         <TABLE bgcolor=#FFFFFF cellspacing=0 border=0>
186 >          <tr>
187 >           <td valign="middle">
188 >            <A HREF=http://www.google.com/search>
189 >            <IMG SRC=http://www.google.com/logos/Logo_40wht.gif border=0 ALT=Google align=middle width="128" height="53"></A>
190 >           </td>
191 >           <td valign="middle">
192 >            <input type=hidden name=domains value="i-scream.org.uk">
193 >            <input type=hidden name=sitesearch value="i-scream.org.uk">
194 >            <INPUT TYPE=text name=q size=35 maxlength=255 value="">
195 >            <INPUT type=submit name=sa VALUE="Search">
196 >            <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;">
197 >           </td>
198 >          </tr>
199 >         </TABLE>
200 >        </FORM>
201 >       </center>
202 >       <!-- Search Google -->
203 >      
204         </p>
205         </font>
206        </td>

Diff Legend

Removed lines
+ Added lines
< Changed lines
> Changed lines