<!--
- contents.inc
- Created by pjm2 14/10/2000
- Last edited 16/01/2001
+ $Author$
+ $Id$
-->
<table border="0" width="500">
<td>
<font size="2" face="arial,sans-serif">
- <center><h3>Current Status</h3></center>
-
+ <center><h3>Project News</h3></center>
+
<p align="justify">
- Most i-scream components are now functioning to initial
- design parameters and data can now be passed through the
- system and displayed successfully. Documentation is still
- being generated, to allow for future development of the
- i-scream project. Detailed information can usually be
- found in the meeting minutes. Code is viewable via CVS
- to UKC users only.
+ <b>Thursday 7 Feb 2002</b><br><br>
+ The alerting section of the i-scream central monitoring system
+ now makes full use of an externally developed IRC bot for it's IRC
+ connectivity. To find out more about this IRC bot, please visit
+ the author's website at <a href="http://www.jibble.org">
+ http://www.jibble.org</a>.
</p>
-
+
<p align="justify">
- The i-scream Distributed Central Monitoring System <a href="http://raptor.ukc.ac.uk/~pjm2/reports/browser.php">Reports</a>
- are now visible on the web. You may view all reports
- available for each day, but please remember that this is
- work in progress still, so the only data currently viewable
- is our own data that has been harvested by our own testing.
-
+ <b>Tuesday 8 Jan 2002</b><br><br>
+ Java ACL (Access Control List) code has been added to the util
+ package of the i-scream server. This code will ultimately allow
+ the server to be more secure when exposed to the Internet. More
+ details can be found <a href="http://www.cs.ukc.ac.uk/people/staff/tdb/#acl">
+ here</a> on the author's website.
+ </p>
+
<p align="justify">
- Our current host development allows us to pass machine statistics
- to our distributed filter arrangement, which then processes the
- data and stores it for later use. An example of such use is the
- historical report generator which produces graphs of machine
- usage over periods of time (viewable in a web browser). Realtime
- clients are also currently being developed - one Java Swing GUI
- version and also a command line version that can run in a terminal
- window. Alerting mechanisms are being put in place to complete the
- i-scream system.
+ <b>Tuesday 18 Dec 2001</b><br><br>
+ The i-scream ihost package has undergone significant changes to
+ make it more flexible and modular. It now incorporates plugins
+ which can be written in any language, and automatically XML
+ encodes data it is given (as opposed to the hardcoded approach
+ in the old version). It has also been made more robust, and
+ where possible optimised to reduce the load on the host system.
</p>
-
+
+ <p> </p>
+ <center><h3>About i-scream</h3></center>
+
+ <p align="justify">
+ <a href="screenshots/"><img border="0" src="screenshots/thumbnail-alerter-email.gif" width="100" height="107" align="left"></a>
+ Details of the i-scream central monitoring system can be found
+ on the <b><a href="features.shtml">features and overview</a></b> page.
+ A variety of <b><a href="screenshots">screen shots</a></b> from the
+ system show some of the key features in use. The <b><a href="reports">reports demo</a></b>
+ page provides a static example of what the i-scream reports (alerts,
+ historical graphs, and live data) could look like on a production system.
+ </p>
+
+ <p align="justify">
+ <a href="screenshots/"><img border="0" src="screenshots/thumbnail-conient-main.gif" width="100" height="107" align="right"></a>
+ The latest source code is available in the <b><a href="cvs.shtml">CVS</a></b>
+ repository, with binary downloads on the downloads page. The
+ <b><a href="documentation">documentation</a></b> page has details of
+ installation, use and maintenance for the end user and developer.
+ We value feedback and comments from you, so please drop us an e-mail
+ to <a href="mailto:dev@i-scream.org.uk">dev@i-scream.org.uk</a>.
+ </p>
+
<p> </p>
- <center><h3>Project Completion</h3></center>
+ <center><h3>Current Work</h3></center>
+
+ <p align="justify">
+ <b>Historical/Realtime graphing package</b><br><br>
+ <a href="screenshots/"><img border="0" src="screenshots/thumbnail-reports-raptor-load15.gif" width="100" height="107" align="left"></a>
+ The current system for graphing i-scream data from the i-scream
+ system is good, but proving to be unscalable and very resource
+ hungry. This is mostly due to the MySQL database backend,
+ and the vast quantity of data recorded. The new system
+ in development makes use of <a href="http://rrdtool.eu.org/">
+ RRDtool</a> to generate the graphs in realtime. This reduces
+ the peak loads of the system, and allows generation of more
+ flexible graphs. This work is nearing completetion.
+ </p>
+
+ <p align="justify">
+ <b>Server security</b><br><br>
+ Security was something mostly overlooked in the original stage
+ of this project (due to the academic nature of the work). However,
+ once in production use this has become an issue, and is being
+ addressed. Initially the plan is to lock down the external points
+ of access (TCP & UDP) in the server to specific hosts. In the
+ longer term, encryption of data would be nice, but would take a
+ lot more time and work.
+ </p>
+
+ <p align="justify">
+ <b>Testing and Development</b><br><br>
+ <a href="screenshots/"><img border="0" src="screenshots/thumbnail-winhost-main.gif" width="100" height="62" align="right"></a>
+ The i-scream system is being tested and developed within the
+ Univeristy of Kent Computer Science department by the Systems
+ Group. This has led to many bug fixes and minor feature
+ enhancements, and will hopefully help to aid the long term
+ development of the system.
+ </p>
+
+ <p> </p>
+ <center><h3>Project History</h3></center>
<p align="justify">
- The project deadline is 4pm on 29 March. As such, we plan to
- complete the coding process by (at the latest) the end of the
- project week (26/2 - 2/3). This allows time for documentation
- to be tidied up and completed, and printing of the project.
+ <a href="screenshots/"><img border="0" src="screenshots/thumbnail-reports-raptor-latest-misc.gif" width="100" height="104" align="left"></a>
+ The i-scream Distributed Central Monitoring System started off as
+ a final year project for a group of <a href="http://www.cs.ukc.ac.uk">
+ Computer Science</a> students at the <a href="http://www.ukc.ac.uk">
+ University of Kent at Canterbury</a>, UK. The project was completed at
+ 4pm on 29 March 2001. It consisted of five lever-arch folders containing
+ mostly source code and documentation. The CVS repository was tagged to
+ signify this even, however, the project is still being developed by the
+ <a href="acknowledgements.shtml">core development team</a>.
</p>
<p align="justify">
- As can be seen in the "problem domain" document, the project
+ <a href="screenshots/"><img border="0" src="screenshots/thumbnail-ihost-main.gif" width="100" height="51" align="right"></a>
+ As can be seen in our "<a href="/probdomain.shtml">problem domain</a>" document, the project
was aimed at the UKC Computer Science department, and as such
- we believe a demonstration to the "customer" is important. We
- plan to do this over the next two weeks, and the feedback given
- will allow any "last minute" alterations to be completed.
+ we believed that a demonstration to the "customer" was important. The
+ feedback from our demonstation was more positive than we had
+ anticipated. We believe that the system may now be of interest
+ to anybody who wishes to monitor a number of machines on their
+ network using a central configuration. The i-scream central
+ monitoring system is now being used by the UKC Computer Science
+ department, and their feedback is being used to further improve
+ the product.
</p>
- <p> </p>
- <center><h3>Naming History</h3></center>
-
<p align="justify">
- The name <b>i-scream</b> arose from a meeting whereupon one member
- of our group randomly chose to draw an ice cream on the white board.
+ <a href="screenshots/"><img border="0" src="screenshots/thumbnail-conient-config.gif" width="100" height="48" align="left"></a>
+ The name <i>i-scream</i> arose from a meeting whereupon one member
+ of the <a href="acknowledgements.shtml">development team</a> felt a strange urge to draw an ice cream on the discussion board.
It later became apparent that we had no name for our project (other
than 'The Project'). It seemed only natural to name our project after
the ice cream that had been oh-so-randomly drawn on the white board.
Copyright issues immediately ruled out anything involving Mr Whippy,
- 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
play on words - it still sounded like <i>ice cream</i>, yet also
- served as a functional decription of our system - namely, one which
+ served as a functional description of our system - namely, one which
screams at somebody if something has gone wrong...
</p>
<p align="justify">
-
+
+ <p> </p>
+ <center><h3>Searching i-scream</h3></center>
+
+ <!-- Search Google -->
+ <center>
+ <FORM method=GET action=http://www.google.com/custom>
+ <TABLE bgcolor=#FFFFFF cellspacing=0 border=0>
+ <tr>
+ <td valign="middle">
+ <A HREF=http://www.google.com/search>
+ <IMG SRC=http://www.google.com/logos/Logo_40wht.gif border=0 ALT=Google align=middle width="128" height="53"></A>
+ </td>
+ <td valign="middle">
+ <input type=hidden name=domains value="i-scream.org.uk">
+ <input type=hidden name=sitesearch value="i-scream.org.uk">
+ <INPUT TYPE=text name=q size=35 maxlength=255 value="">
+ <INPUT type=submit name=sa VALUE="Search">
+ <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;">
+ </td>
+ </tr>
+ </TABLE>
+ </FORM>
+ </center>
+ <!-- Search Google -->
+
</p>
</font>
</td>
i-scream / www.i-scream.org.git / blobdiff