ViewVC logotype

Contents of /web/www/contents.inc

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

Revision 1.51 - (show annotations)
Fri Oct 10 10:42:55 2003 UTC (15 years, 10 months ago) by tdb
Branch: MAIN
Changes since 1.50: +8 -11 lines
Update website to announce 0.6 release of libstatgrab.

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

  ViewVC Help
Powered by ViewVC 1.1.26