ViewVC logotype

Contents of /web/www/contents.inc

Parent Directory Parent Directory | Revision Log Revision Log | View Revision Graph Revision Graph

Revision 1.39 - (show annotations)
Sun May 25 13:36:52 2003 UTC (16 years, 3 months ago) by tdb
Branch: MAIN
Changes since 1.38: +10 -1 lines
Added mention of libstatgrab release to main page.

2 <!--
3 $Author: tdb $
4 $Id: contents.inc,v 1.38 2003/05/15 20:48:01 tdb Exp $
5 -->
7 <table border="0" width="500">
8 <tr>
9 <td>
10 <font size="2" face="arial,sans-serif">
12 <center><h3>Project News</h3></center>
14 <p align="justify">
15 <b>Wednesday 7 May 2003</b><br><br>
16 We've <a href="http://www.freshmeat.net/projects/libstatgrab>
17 released</a> libstatgrab 0.4 as an individual product. You can
18 download it <a href="http://snapshots.i-scream.org/libstatgrab">
19 here</a>. This release is functionally complete, but lacks
20 documentation. We hope to rectify this in the next release.
21 </p>
23 <p align="justify">
24 <b>Tuesday 4 February 2003</b><br><br>
25 Over the coming week we will be making snapshot builds of the
26 i-scream central monitoring system from the CVS repository.
27 These builds will have quite a few changes from the downloads
28 currently available (a document detailing them will be
29 released later on), so please give them a whirl. We would be
30 grateful if you <a href="mailto:dev@i-scream.org">contacted</a>
31 us with any questions or bugs.<br><br>
32 The downloads will be available on our snapshot server :-<br>
33 <a href="http://snapshots.i-scream.org/">
34 http://snapshots.i-scream.org/</a>.
35 </p>
37 <p align="justify">
38 <b>Saturday 1 June 2002</b><br><br>
39 Work has now been finished on a new ihost written in C. This has
40 been in the pipeline for a long time, and we're glad to finally
41 see an efficient native host! Credit goes to our new developer
42 <a href="/who.shtml">Pete</a>. Until we update the downloads
43 pages you can download the new ihost
44 <a href="http://snapshots.i-scream.org/ihost/">
45 here</a>.
46 </p>
48 <p align="justify">
49 <b>Tuesday 21 May 2002</b><br><br>
50 We've finally put the finishing touches to the new
51 <a href="http://rrdtool.eu.org">RRDtool</a> based graphing system.
52 It's working well, and has done away with the MySQL database
53 backend which took up far too many resources. This new system
54 generates the graphs in a more realtime nature, allowing more
55 flexible graphs to be generated. This is currently only available
56 through <a href="http://cvs.i-scream.org/cms/source/reports/rrdgraphing/">
57 CVS</a>.
58 </p>
60 <p align="justify">
61 <b>Saturday 18 May 2002</b><br><br>
62 The i-scream central monitoring system is now <a href="/license.shtml">
63 licensed</a> under the GNU Public License. We are currently working
64 to make full downloads, including source, available on this site.
65 </p>
67 <p align="justify">
68 <b>Thursday 7 Feb 2002</b><br><br>
69 The alerting section of the i-scream central monitoring system
70 now makes full use of an externally developed IRC bot for it's IRC
71 connectivity. To find out more about this IRC bot, please visit
72 the author's website at <a href="http://www.jibble.org">
73 http://www.jibble.org</a>.
74 </p>
76 <p align="justify">
77 <b>Tuesday 8 Jan 2002</b><br><br>
78 Java ACL (Access Control List) code has been added to the util
79 package of the i-scream server. This code will ultimately allow
80 the server to be more secure when exposed to the Internet. More
81 details can be found <a href="http://www.cs.kent.ac.uk/people/staff/tdb/#acl">
82 here</a> on the author's website.
83 </p>
85 <p>&nbsp;</p>
86 <center><h3>About i-scream</h3></center>
88 <p align="justify">
89 <a href="screenshots/"><img border="0" src="screenshots/thumbnail-alerter-email.gif" width="100" height="107" align="left"></a>
90 Details of the i-scream central monitoring system can be found
91 on the <b><a href="features.shtml">features and overview</a></b> page.
92 A variety of <b><a href="screenshots">screen shots</a></b> from the
93 system show some of the key features in use. The <b><a href="reports">reports demo</a></b>
94 page provides a static example of what the i-scream reports (alerts,
95 historical graphs, and live data) could look like on a production system.
96 </p>
98 <p align="justify">
99 <a href="screenshots/"><img border="0" src="screenshots/thumbnail-conient-main.gif" width="100" height="107" align="right"></a>
100 The latest source code is available in the <b><a href="cvs.shtml">CVS</a></b>
101 repository, with binary downloads on the downloads page. The
102 <b><a href="documentation">documentation</a></b> page has details of
103 installation, use and maintenance for the end user and developer.
104 We value feedback and comments from you, so please drop us an e-mail
105 to <a href="mailto:dev@i-scream.org">dev@i-scream.org</a>.
106 </p>
108 <p>&nbsp;</p>
109 <center><h3>Current Work</h3></center>
111 <p align="justify">
112 <b>Extending monitoring facilites</b><br><br>
113 <a href="screenshots/"><img border="0" src="screenshots/thumbnail-reports-raptor-load15.gif" width="100" height="107" align="left"></a>
114 Work is continuing, in conjunction with the new ihost, to extend
115 the range of i-scream's monitoring. Currently we are adding new
116 features to more accurately monitoring memory and swap usage,
117 along with more disk statistics. We are also planning to improve
118 the rather basic service monitors which are currently in place.
119 There are also many more subtle changes that need to be made to
120 improve the reliability and usefulness of i-scream's monitoring.
121 </p>
123 <p align="justify">
124 <b>Server security</b><br><br>
125 Security was something mostly overlooked in the original stage
126 of this project (due to the academic nature of the work). However,
127 once in production use this has become an issue, and is being
128 addressed. Initially the plan is to lock down the external points
129 of access (TCP & UDP) in the server to specific hosts. In the
130 longer term, encryption of data would be nice, but would take a
131 lot more time and work.
132 </p>
134 <p align="justify">
135 <b>Testing and Development</b><br><br>
136 <a href="screenshots/"><img border="0" src="screenshots/thumbnail-winhost-main.gif" width="100" height="62" align="right"></a>
137 The i-scream system is being tested and developed within the
138 Univeristy of Kent Computer Science department by the Systems
139 Group. This has led to many bug fixes and minor feature
140 enhancements, and will hopefully help to aid the long term
141 development of the system.
142 </p>
144 <p>&nbsp;</p>
145 <center><h3>Project History</h3></center>
147 <p align="justify">
148 <a href="screenshots/"><img border="0" src="screenshots/thumbnail-reports-raptor-latest-misc.gif" width="100" height="104" align="left"></a>
149 The i-scream Distributed Central Monitoring System started off as
150 a final year project for a group of <a href="http://www.cs.kent.ac.uk">
151 Computer Science</a> students at the <a href="http://www.kent.ac.uk">
152 University of Kent at Canterbury</a>, UK. The project was completed at
153 4pm on 29 March 2001. It consisted of five lever-arch folders containing
154 mostly source code and documentation. The CVS repository was tagged to
155 signify this even, however, the project is still being developed by the
156 <a href="acknowledgements.shtml">core development team</a>.
157 </p>
159 <p align="justify">
160 <a href="screenshots/"><img border="0" src="screenshots/thumbnail-ihost-main.gif" width="100" height="51" align="right"></a>
161 As can be seen in our &quot;<a href="/probdomain.shtml">problem domain</a>&quot; document, the project
162 was aimed at the UKC Computer Science department, and as such
163 we believed that a demonstration to the &quot;customer&quot; was important. The
164 feedback from our demonstation was more positive than we had
165 anticipated. We believe that the system may now be of interest
166 to anybody who wishes to monitor a number of machines on their
167 network using a central configuration. The i-scream central
168 monitoring system is now being used by the UKC Computer Science
169 department, and their feedback is being used to further improve
170 the product.
171 </p>
173 <p align="justify">
174 <a href="screenshots/"><img border="0" src="screenshots/thumbnail-conient-config.gif" width="100" height="48" align="left"></a>
175 The name <i>i-scream</i> arose from a meeting whereupon one member
176 of the <a href="acknowledgements.shtml">development team</a> felt a strange urge to draw an ice cream on the discussion board.
177 It later became apparent that we had no name for our project (other
178 than 'The Project'). It seemed only natural to name our project after
179 the ice cream that had been oh-so-randomly drawn on the white board.
180 Copyright issues immediately ruled out anything involving Mr Whippy,
181 so we had to settle for <i>i-scream</i>. And thus, we were left with a cunning
182 play on words - it still sounded like <i>ice cream</i>, yet also
183 served as a functional description of our system - namely, one which
184 screams at somebody if something has gone wrong...
185 </p>
186 <p align="justify">
188 <p>&nbsp;</p>
189 <center><h3>Searching i-scream</h3></center>
191 <!-- Search Google -->
192 <center>
193 <FORM method=GET action=http://www.google.com/custom>
194 <TABLE bgcolor=#FFFFFF cellspacing=0 border=0>
195 <tr>
196 <td valign="middle">
197 <A HREF=http://www.google.com/search>
198 <IMG SRC=http://www.google.com/logos/Logo_40wht.gif border=0 ALT=Google align=middle width="128" height="53"></A>
199 </td>
200 <td valign="middle">
201 <input type=hidden name=domains value="i-scream.org">
202 <input type=hidden name=sitesearch value="i-scream.org">
203 <INPUT TYPE=text name=q size=35 maxlength=255 value="">
204 <INPUT type=submit name=sa VALUE="Search">
205 <INPUT type=hidden name=cof VALUE="T:#000066;LW:502;ALC:#3333cc;L:http://www.i-scream.org/i-scream.gif;LC:#0000ff;LH:37;BGC:#ffffff;AH:left;VLC:#3333cc;AWFID:d646a9fd69e7d9cb;">
206 </td>
207 </tr>
208 </TABLE>
209 </FORM>
210 </center>
211 <!-- Search Google -->
213 </p>
214 </font>
215 </td>
216 </tr>
217 </table>

  ViewVC Help
Powered by ViewVC 1.1.26