ViewVC logotype

Contents of /web/www/contents.inc

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

Revision 1.48 - (show annotations)
Thu Aug 28 22:36:43 2003 UTC (15 years, 11 months ago) by tdb
Branch: MAIN
Changes since 1.47: +3 -3 lines
Even I can't remember the URL's ;-)

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

  ViewVC Help
Powered by ViewVC 1.1.26