web/www/contents.inc


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