web/www/contents.inc


<!--
    $Author: tdb $
    $Id: contents.inc,v 1.47 2003/08/28 22:30:01 tdb Exp $
-->

    <table border="0" width="500">
     <tr>
      <td>
       <font size="2" face="arial,sans-serif">
       
       <center><h3>Project News</h3></center>

       <p align="justify">
        <b>Monday 25 August 2003</b><br><br>
        We're pleased to announce a new release of libstatgrab. You
        can download version 0.5 from
        <a href="ftp://ftp.i-scream.org/pub/i-scream/libstatgrab">here</a>.
        This release provides both documentation and examples, which
        we hope will make the package more useable. Stay tuned for the
        next release with some useful tools.
       </p>

       <p align="justify">
        <b>Tuesday 15 July 2003</b><br><br>
        We have moved the i-scream support and bug tracking to a new
        facility on the i-scream server. For further details please
        see <a href="/support.shtml">this</a> page.
       </p>
       
       <p align="justify">
        <b>Sunday 8 June 2003</b><br><br>
        The i-scream website, email, and cvs facilities are now all
        run from a <a href="http://www.freebsd.org">FreeBSD</a> server.<br>
        <a href="http://www.freebsd.org">
         <img src="/powerlogo.gif" width="171" height="64" border="0" alt="Powered By FreeBSD">
        </a>
       </p>
       
       <p align="justify">
        <b>Tuesday 4 February 2003</b><br><br>
        Over the coming week we will be making snapshot builds of the
        i-scream central monitoring system from the CVS repository.
        These builds will have quite a few changes from the downloads
        currently available (a document detailing them will be
        released later on), so please give them a whirl. We would be
        grateful if you <a href="mailto:dev@i-scream.org">contacted</a>
        us with any questions or bugs.<br><br>
        The downloads will be available on our snapshot server :-<br>
        <a href="http://snapshots.i-scream.org/">
        http://snapshots.i-scream.org/</a>.
       </p>

       <p align="justify">
        <b>Saturday 1 June 2002</b><br><br>
        Work has now been finished on a new ihost written in C. This has
        been in the pipeline for a long time, and we're glad to finally
        see an efficient native host! Credit goes to our new developer
        <a href="/who.shtml">Pete</a>. Until we update the downloads
        pages you can download the new ihost 
        <a href="ftp://ftp.i-scream.org/pub/i-scream/ihost/">
        here</a>.
       </p>

       <p align="justify">
        <b>Tuesday 21 May 2002</b><br><br>
        We've finally put the finishing touches to the new
        <a href="http://rrdtool.eu.org">RRDtool</a> based graphing system.
        It's working well, and has done away with the MySQL database
        backend which took up far too many resources. This new system
        generates the graphs in a more realtime nature, allowing more
        flexible graphs to be generated. This is currently only available
        through <a href="http://cvs.i-scream.org/cms/source/reports/rrdgraphing/">
        CVS</a>.
       </p>

       <p align="justify">
        <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.kent.ac.uk/people/staff/tdb/#acl">
        here</a> on the author's website.
       </p>
       
       <p>&nbsp;</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">dev@i-scream.org</a>.
       </p>
       
       <p>&nbsp;</p>
       <center><h3>Current Work</h3></center>
       
       <p align="justify">
        <b>Extending monitoring facilites</b><br><br>
        <a href="screenshots/"><img border="0" src="screenshots/thumbnail-reports-raptor-load15.gif" width="100" height="107" align="left"></a>
        Work is continuing, in conjunction with the new ihost, to extend
        the range of i-scream's monitoring. Currently we are adding new
        features to more accurately monitoring memory and swap usage,
        along with more disk statistics. We are also planning to improve
        the rather basic service monitors which are currently in place.
        There are also many more subtle changes that need to be made to
        improve the reliability and usefulness of i-scream's monitoring.
       </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>&nbsp;</p>
       <center><h3>Project History</h3></center>

       <p align="justify">
        <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.kent.ac.uk">
        Computer Science</a> students at the <a href="http://www.kent.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">
        <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 &quot;<a href="/probdomain.shtml">problem domain</a>&quot; document, the project
        was aimed at the UKC Computer Science department, and as such
        we believed that a demonstration to the &quot;customer&quot; 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 align="justify">
        <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 <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 description of our system - namely, one which
        screams at somebody if something has gone wrong...
       </p>
       <p align="justify">
       
       <p>&nbsp;</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;i-scream.org.uk">
            <input type=hidden name=sitesearch value="i-scream.org">
            <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/i-scream.gif;LC:#0000ff;LH:37;BGC:#ffffff;AH:left;VLC:#3333cc;GL:0;S:http://www.i-scream.org/;AWFID:d646a9fd69e7d9cb;">
           </td>
          </tr>
         </TABLE>
        </FORM>
       </center>
       <!-- Search Google --> 
       
       </p>
       </font>
      </td>
     </tr>   
    </table>
Revision:	1.48
Committed:	Thu Aug 28 22:36:43 2003 UTC (21 years, 4 months ago) by tdb
Branch:	MAIN
Changes since 1.47:	+3 -3 lines
Log Message:	Even I can't remember the URL's ;-)
#	User	Rev	Content
1	tdb	1.1
2			<!--
3	tdb	1.29	$Author: tdb $
4	tdb	1.48	$Id: contents.inc,v 1.47 2003/08/28 22:30:01 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	tdb	1.41
14			<p align="justify">
15	tdb	1.46	<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	tdb	1.48	<a href="ftp://ftp.i-scream.org/pub/i-scream/libstatgrab">here</a>.
19	tdb	1.46	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>
23
24			<p align="justify">
25	tdb	1.45	<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>
30
31			<p align="justify">
32	tdb	1.41	<b>Sunday 8 June 2003</b><br><br>
33			The i-scream website, email, and cvs facilities are now all
34	tdb	1.42	run from a <a href="http://www.freebsd.org">FreeBSD</a> server.<br>
35	tdb	1.41	<a href="http://www.freebsd.org">
36	tdb	1.43	<img src="/powerlogo.gif" width="171" height="64" border="0" alt="Powered By FreeBSD">
37	tdb	1.41	</a>
38			</p>
39	tdb	1.45
40	tdb	1.39	<p align="justify">
41	tdb	1.36	<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	tdb	1.38	grateful if you <a href="mailto:dev@i-scream.org">contacted</a>
48	tdb	1.36	us with any questions or bugs.<br><br>
49			The downloads will be available on our snapshot server :-<br>
50	tdb	1.38	<a href="http://snapshots.i-scream.org/">
51			http://snapshots.i-scream.org/</a>.
52	tdb	1.36	</p>
53
54	tdb	1.28	<p align="justify">
55	tdb	1.31	<b>Saturday 1 June 2002</b><br><br>
56			Work has now been finished on a new ihost written in C. This has
57	tdb	1.32	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	tdb	1.31	<a href="/who.shtml">Pete</a>. Until we update the downloads
60			pages you can download the new ihost
61	tdb	1.48	<a href="ftp://ftp.i-scream.org/pub/i-scream/ihost/">
62	tdb	1.31	here</a>.
63			</p>
64
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	tdb	1.38	through <a href="http://cvs.i-scream.org/cms/source/reports/rrdgraphing/">
74	tdb	1.31	CVS</a>.
75			</p>
76
77	tdb	1.28	<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	tdb	1.38	details can be found <a href="http://www.cs.kent.ac.uk/people/staff/tdb/#acl">
83	tdb	1.29	here</a> on the author's website.
84	tdb	1.28	</p>
85
86			<p> </p>
87			<center><h3>About i-scream</h3></center>
88
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>
98
99	tdb	1.1	<p align="justify">
100	tdb	1.28	<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	tdb	1.38	to <a href="mailto:dev@i-scream.org">dev@i-scream.org</a>.
107	pjm2	1.5	</p>
108	tdb	1.28
109			<p> </p>
110			<center><h3>Current Work</h3></center>
111
112	pjm2	1.5	<p align="justify">
113	tdb	1.31	<b>Extending monitoring facilites</b><br><br>
114	tdb	1.28	<a href="screenshots/"><img border="0" src="screenshots/thumbnail-reports-raptor-load15.gif" width="100" height="107" align="left"></a>
115	tdb	1.31	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	tdb	1.32	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	pjm2	1.11	</p>
123	tdb	1.31
124	pjm2	1.7	<p align="justify">
125	tdb	1.28	<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	tdb	1.1	</p>
134	tdb	1.9
135			<p align="justify">
136	tdb	1.28	<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	tdb	1.9	</p>
144	tdb	1.28
145	tdb	1.1	<p> </p>
146	tdb	1.28	<center><h3>Project History</h3></center>
147	tdb	1.1
148			<p align="justify">
149	pjm2	1.15	<a href="screenshots/"><img border="0" src="screenshots/thumbnail-reports-raptor-latest-misc.gif" width="100" height="104" align="left"></a>
150	pjm2	1.14	The i-scream Distributed Central Monitoring System started off as
151	tdb	1.38	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	tdb	1.28	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	tdb	1.6	</p>
159
160			<p align="justify">
161	pjm2	1.15	<a href="screenshots/"><img border="0" src="screenshots/thumbnail-ihost-main.gif" width="100" height="51" align="right"></a>
162	tdb	1.18	As can be seen in our "<a href="/probdomain.shtml">problem domain</a>" document, the project
163	tdb	1.6	was aimed at the UKC Computer Science department, and as such
164	pjm2	1.22	we believed that a demonstration to the "customer" was important. The
165	pjm2	1.12	feedback from our demonstation was more positive than we had
166	tdb	1.27	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	tdb	1.1	</p>
173
174			<p align="justify">
175	pjm2	1.15	<a href="screenshots/"><img border="0" src="screenshots/thumbnail-conient-config.gif" width="100" height="48" align="left"></a>
176	pjm2	1.14	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	tdb	1.1	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	pjm2	1.14	so we had to settle for <i>i-scream</i>. And thus, we were left with a cunning
183	tdb	1.1	play on words - it still sounded like <i>ice cream</i>, yet also
184	tdb	1.26	served as a functional description of our system - namely, one which
185	tdb	1.1	screams at somebody if something has gone wrong...
186			</p>
187			<p align="justify">
188	tdb	1.23
189	tdb	1.24	<p> </p>
190	tdb	1.28	<center><h3>Searching i-scream</h3></center>
191	tdb	1.24
192	tdb	1.23	<!-- Search Google -->
193			<center>
194	tdb	1.28	<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	tdb	1.44	<input type=hidden name=domains value="i-scream.org;i-scream.org.uk">
203	tdb	1.38	<input type=hidden name=sitesearch value="i-scream.org">
204	tdb	1.28	<INPUT TYPE=text name=q size=35 maxlength=255 value="">
205			<INPUT type=submit name=sa VALUE="Search">
206	tdb	1.44	<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	tdb	1.28	</td>
208			</tr>
209			</TABLE>
210			</FORM>
211	tdb	1.23	</center>
212			<!-- Search Google -->
213
214	tdb	1.1	</p>
215			</font>
216			</td>
217			</tr>
218			</table>