ViewVC Help
View File | Revision Log | Show Annotations | Revision Graph | Root Listing
root/i-scream/web/www/contents.inc
Revision: 1.36
Committed: Tue Feb 4 09:33:55 2003 UTC (21 years, 10 months ago) by tdb
Branch: MAIN
Changes since 1.35: +15 -1 lines
Log Message:
Added news item about snapshot server.

File Contents

# User Rev Content
1 tdb 1.1
2     <!--
3 tdb 1.29 $Author: tdb $
4 tdb 1.36 $Id: contents.inc,v 1.35 2002/06/14 10:29:02 tdb Exp $
5 tdb 1.1 -->
6    
7     <table border="0" width="500">
8     <tr>
9     <td>
10     <font size="2" face="arial,sans-serif">
11    
12 tdb 1.28 <center><h3>Project News</h3></center>
13    
14 tdb 1.36 <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 tdb 1.28 <p align="justify">
29 tdb 1.31 <b>Saturday 1 June 2002</b><br><br>
30     Work has now been finished on a new ihost written in C. This has
31 tdb 1.32 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 tdb 1.31 <a href="/who.shtml">Pete</a>. Until we update the downloads
34     pages you can download the new ihost
35 tdb 1.35 <a href="http://snapshots.i-scream.org.uk/ihost-1.0rc1.tar.gz">
36 tdb 1.31 here</a>.
37     </p>
38    
39     <p align="justify">
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 tdb 1.32 through <a href="http://www.i-scream.org.uk/cgi-bin/cvs/viewcvs.cgi/cms/source/reports/rrdgraphing/">
48 tdb 1.31 CVS</a>.
49     </p>
50    
51     <p align="justify">
52     <b>Saturday 18 May 2002</b><br><br>
53     The i-scream central monitoring system is now <a href="/license.shtml">
54 tdb 1.33 licensed</a> under the GNU Public License. We are currently working
55 tdb 1.31 to make full downloads, including source, available on this site.
56     </p>
57    
58     <p align="justify">
59 tdb 1.28 <b>Thursday 7 Feb 2002</b><br><br>
60 tdb 1.30 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 tdb 1.28 connectivity. To find out more about this IRC bot, please visit
63 tdb 1.29 the author's website at <a href="http://www.jibble.org">
64 tdb 1.28 http://www.jibble.org</a>.
65     </p>
66    
67     <p align="justify">
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 tdb 1.29 here</a> on the author's website.
74 tdb 1.28 </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 tdb 1.1 <p align="justify">
90 tdb 1.28 <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 pjm2 1.5 </p>
98 tdb 1.28
99     <p>&nbsp;</p>
100     <center><h3>Current Work</h3></center>
101    
102 pjm2 1.5 <p align="justify">
103 tdb 1.31 <b>Extending monitoring facilites</b><br><br>
104 tdb 1.28 <a href="screenshots/"><img border="0" src="screenshots/thumbnail-reports-raptor-load15.gif" width="100" height="107" align="left"></a>
105 tdb 1.31 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 tdb 1.32 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 pjm2 1.11 </p>
113 tdb 1.31
114 pjm2 1.7 <p align="justify">
115 tdb 1.28 <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 tdb 1.1 </p>
124 tdb 1.9
125     <p align="justify">
126 tdb 1.28 <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 tdb 1.9 </p>
134 tdb 1.28
135 tdb 1.1 <p>&nbsp;</p>
136 tdb 1.28 <center><h3>Project History</h3></center>
137 tdb 1.1
138     <p align="justify">
139 pjm2 1.15 <a href="screenshots/"><img border="0" src="screenshots/thumbnail-reports-raptor-latest-misc.gif" width="100" height="104" align="left"></a>
140 pjm2 1.14 The i-scream Distributed Central Monitoring System started off as
141 tdb 1.28 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 tdb 1.6 </p>
149    
150     <p align="justify">
151 pjm2 1.15 <a href="screenshots/"><img border="0" src="screenshots/thumbnail-ihost-main.gif" width="100" height="51" align="right"></a>
152 tdb 1.18 As can be seen in our &quot;<a href="/probdomain.shtml">problem domain</a>&quot; document, the project
153 tdb 1.6 was aimed at the UKC Computer Science department, and as such
154 pjm2 1.22 we believed that a demonstration to the &quot;customer&quot; was important. The
155 pjm2 1.12 feedback from our demonstation was more positive than we had
156 tdb 1.27 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 tdb 1.1 </p>
163    
164     <p align="justify">
165 pjm2 1.15 <a href="screenshots/"><img border="0" src="screenshots/thumbnail-conient-config.gif" width="100" height="48" align="left"></a>
166 pjm2 1.14 The name <i>i-scream</i> arose from a meeting whereupon one member
167     of the <a href="acknowledgements.shtml">development team</a> felt a strange urge to draw an ice cream on the discussion board.
168 tdb 1.1 It later became apparent that we had no name for our project (other
169     than 'The Project'). It seemed only natural to name our project after
170     the ice cream that had been oh-so-randomly drawn on the white board.
171     Copyright issues immediately ruled out anything involving Mr Whippy,
172 pjm2 1.14 so we had to settle for <i>i-scream</i>. And thus, we were left with a cunning
173 tdb 1.1 play on words - it still sounded like <i>ice cream</i>, yet also
174 tdb 1.26 served as a functional description of our system - namely, one which
175 tdb 1.1 screams at somebody if something has gone wrong...
176     </p>
177     <p align="justify">
178 tdb 1.23
179 tdb 1.24 <p>&nbsp;</p>
180 tdb 1.28 <center><h3>Searching i-scream</h3></center>
181 tdb 1.24
182 tdb 1.23 <!-- Search Google -->
183     <center>
184 tdb 1.28 <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 tdb 1.23 </center>
202     <!-- Search Google -->
203    
204 tdb 1.1 </p>
205     </font>
206     </td>
207     </tr>
208     </table>