web/www/contents.inc


<!--
    $Author: tdb $
    $Id: contents.inc,v 1.48 2003/08/28 22:36:43 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>Tuesday 09 September 2003</b><br><br>
        We're pleased to announce a new release of libstatgrab. You
        can download version 0.5.1 from
        <a href="ftp://ftp.i-scream.org/pub/i-scream/libstatgrab">here</a>.
        This release fixes some bugs, and adds a new tool 'statgrab'.
       </p>

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