ViewVC Help

View File | Revision Log | Show Annotations | Revision Graph | Root Listing

root/i-scream/web/www/contents.inc

Comparing web/www/contents.inc (file contents):
Revision 1.22 by pjm2, Wed May 30 20:32:38 2001 UTC vs.
Revision 1.43 by tdb, Sun Jun 8 12:34:49 2003 UTC

#	Line 1 | Line 1
1
2		<!--
3	<	contents.inc
4	<	Created by pjm2 14/10/2000
5	<	Last edited 16/01/2001
3	>	$Author$
4	>	$Id$
5		-->
6
7		<table border="0" width="500">
#	Line 10 | Line 9
9		<td>
10		<font size="2" face="arial,sans-serif">
11
12	<	<center><h3>Current Status</h3></center>
12	>	<center><h3>Project News</h3></center>
13
14		<p align="justify">
15	<	<a href="screenshots/"><img border="0" src="screenshots/thumbnail-reports-raptor-load15.gif" width="100" height="107" align="left"></a>
16	<	All i-scream components now function to initial
17	<	design parameters and our system is regarded to be complete.
18	<	<b><a href="documentation/">Documentation</a></b> is available to assist third party programmers
19	<	in producing Hosts for use with the i-scream server.
20	<	Our progress during the project can be found in the meeting minutes.
22	<	Code is viewable via <a href="http://raptor.ukc.ac.uk/~tdb1/cgi-bin/viewcvs.cgi">CVS</a> to local users only.
15	>	<b>Sunday 8 June 2003</b><br><br>
16	>	The i-scream website, email, and cvs facilities are now all
17	>	run from a <a href="http://www.freebsd.org">FreeBSD</a> server.<br>
18	>	<a href="http://www.freebsd.org">
19	>	<img src="/powerlogo.gif" width="171" height="64" border="0" alt="Powered By FreeBSD">
20	>	</a>
21		</p>
22
23		<p align="justify">
24	<	<a href="screenshots/"><img border="0" src="screenshots/thumbnail-winhost-main.gif" width="100" height="62" align="right"></a>
25	<
26	<	The i-scream Distributed Central Monitoring System Reports
27	<	are now visible on the web.  If you are <b>not</b> a local user, then you may
28	<	view some of the output in the <b><a href="screenshots/">screen shots</a></b> section or you may view some
29	<	static example content on the <a href="reports/"><b>Reports Demo</b></a> pages.
32	<	You may view the latest information about each machine, historical 24-hour
33	<	reports and alerts for each machine.  Our own i-scream server is running constantly,
34	<	along with several hosts to enable plenty of data harvesting.  If you would
35	<	like your i-scream web reports to be linked from this site, then please email us
36	<	at <a href="mailto:dev@i-scream.org.uk">dev@i-scream.org.uk</a>
24	>	<b>Wednesday 7 May 2003</b><br><br>
25	>	We've <a href="http://www.freshmeat.net/projects/libstatgrab">
26	>	released</a> libstatgrab 0.4 as an individual product. You can
27	>	download it <a href="http://snapshots.i-scream.org/libstatgrab">
28	>	here</a>. This release is functionally complete, but lacks
29	>	documentation. We hope to rectify this in the next release.
30		</p>
31	+
32	+	<p align="justify">
33	+	<b>Tuesday 4 February 2003</b><br><br>
34	+	Over the coming week we will be making snapshot builds of the
35	+	i-scream central monitoring system from the CVS repository.
36	+	These builds will have quite a few changes from the downloads
37	+	currently available (a document detailing them will be
38	+	released later on), so please give them a whirl. We would be
39	+	grateful if you <a href="mailto:dev@i-scream.org">contacted</a>
40	+	us with any questions or bugs.<br><br>
41	+	The downloads will be available on our snapshot server :-<br>
42	+	<a href="http://snapshots.i-scream.org/">
43	+	http://snapshots.i-scream.org/</a>.
44	+	</p>
45
46		<p align="justify">
47	<	<a href="screenshots/"><img border="0" src="screenshots/thumbnail-conient-main.gif" width="100" height="107" align="left"></a>
48	<	Our current host development allows us to pass machine statistics
49	<	to our distributed filter arrangement, which then processes the
50	<	data and stores it for later use.  An example of such use is the
51	<	historical report generator which produces graphs of machine
52	<	usage over periods of time.  A real-time
53	<	client is also available (Conient) and alert information can be
54	<	displayed to the public via dynamic web pages.
47	>	<b>Saturday 1 June 2002</b><br><br>
48	>	Work has now been finished on a new ihost written in C. This has
49	>	been in the pipeline for a long time, and we're glad to finally
50	>	see an efficient native host! Credit goes to our new developer
51	>	<a href="/who.shtml">Pete</a>. Until we update the downloads
52	>	pages you can download the new ihost
53	>	<a href="http://snapshots.i-scream.org/ihost/">
54	>	here</a>.
55		</p>
56	+
57	+	<p align="justify">
58	+	<b>Tuesday 21 May 2002</b><br><br>
59	+	We've finally put the finishing touches to the new
60	+	<a href="http://rrdtool.eu.org">RRDtool</a> based graphing system.
61	+	It's working well, and has done away with the MySQL database
62	+	backend which took up far too many resources. This new system
63	+	generates the graphs in a more realtime nature, allowing more
64	+	flexible graphs to be generated. This is currently only available
65	+	through <a href="http://cvs.i-scream.org/cms/source/reports/rrdgraphing/">
66	+	CVS</a>.
67	+	</p>
68	+
69	+	<p align="justify">
70	+	<b>Saturday 18 May 2002</b><br><br>
71	+	The i-scream central monitoring system is now <a href="/license.shtml">
72	+	licensed</a> under the GNU Public License. We are currently working
73	+	to make full downloads, including source, available on this site.
74	+	</p>
75	+
76	+	<p align="justify">
77	+	<b>Thursday 7 Feb 2002</b><br><br>
78	+	The alerting section of the i-scream central monitoring system
79	+	now makes full use of an externally developed IRC bot for it's IRC
80	+	connectivity. To find out more about this IRC bot, please visit
81	+	the author's website at <a href="http://www.jibble.org">
82	+	http://www.jibble.org</a>.
83	+	</p>
84
85		<p align="justify">
86	<	<a href="screenshots/"><img border="0" src="screenshots/thumbnail-alerter-email.gif" width="100" height="107" align="right"></a>
87	<	The latest builds of the i-scream Distributed Central Monitoring System
88	<	are now available for <b><a href="/downloads/">download</a></b> from this
89	<	website.  To assist in our addition of features to the system, we
90	<	would be extremely grateful to receive feedback from anybody who has
91	<	any comments about the system.  You may email the development team
57	<	at <a href="mailto:dev@i-scream.org.uk">dev@i-scream.org.uk</a>
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	>	details can be found <a href="http://www.cs.kent.ac.uk/people/staff/tdb/#acl">
91	>	here</a> on the author's website.
92		</p>
93	+
94	+	<p>&nbsp;</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	+	<p align="justify">
108	+	<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	+	to <a href="mailto:dev@i-scream.org">dev@i-scream.org</a>.
115	+	</p>
116	+
117	+	<p>&nbsp;</p>
118	+	<center><h3>Current Work</h3></center>
119	+
120	+	<p align="justify">
121	+	<b>Extending monitoring facilites</b><br><br>
122	+	<a href="screenshots/"><img border="0" src="screenshots/thumbnail-reports-raptor-load15.gif" width="100" height="107" align="left"></a>
123	+	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	+	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	+	</p>
131
132	+	<p align="justify">
133	+	<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	+	</p>
142	+
143	+	<p align="justify">
144	+	<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	+	</p>
152	+
153		<p>&nbsp;</p>
154	<	<center><h3>Project Completion</h3></center>
154	>	<center><h3>Project History</h3></center>
155
156		<p align="justify">
157		<a href="screenshots/"><img border="0" src="screenshots/thumbnail-reports-raptor-latest-misc.gif" width="100" height="104" align="left"></a>
158		The i-scream Distributed Central Monitoring System started off as
159	<	a final year project for a group of <a href="http://www.cs.ukc.ac.uk">Computer Science</a> students at
160	<	the <a href="http://www.ukc.ac.uk">University of Kent at Canterbury</a>, UK.
161	<	The project deadline was 4pm on 29th March 2001.  Most of the group
162	<	met very early that morning to compile the project into five
163	<	lever arch folders.  The project, consisting of source code, user,
164	<	maintenance and other documents, was handed in at 3pm.  The CVS
165	<	repository was tagged to signify the project's completion, however,
73	<	the project is still being developed by the <a href="acknowledgements.shtml">core development team</a>
74	<	as we have found the system to be very useful in practice.  We would
75	<	love to hear of ideas for extra features that we may include in the
76	<	next builds.
159	>	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	>	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		</p>
167
168		<p align="justify">
#	Line 82 | Line 171
171		was aimed at the UKC Computer Science department, and as such
172		we believed that a demonstration to the &quot;customer&quot; was important. The
173		feedback from our demonstation was more positive than we had
174	<	anticipated. We believe that the system may now be of great
175	<	interest to anybody who wishes to monitor a number of machines
176	<	on their network using a central configuration.
174	>	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		</p>
181
90	–	<p>&nbsp;</p>
91	–	<center><h3>Naming History</h3></center>
92	–
182		<p align="justify">
183		<a href="screenshots/"><img border="0" src="screenshots/thumbnail-conient-config.gif" width="100" height="48" align="left"></a>
184		The name <i>i-scream</i> arose from a meeting whereupon one member
#	Line 100 | Line 189
189		Copyright issues immediately ruled out anything involving Mr Whippy,
190		so we had to settle for <i>i-scream</i>. And thus, we were left with a cunning
191		play on words - it still sounded like <i>ice cream</i>, yet also
192	<	served as a functional decription of our system - namely, one which
192	>	served as a functional description of our system - namely, one which
193		screams at somebody if something has gone wrong...
194		</p>
195		<p align="justify">
196	<
196	>
197	>	<p>&nbsp;</p>
198	>	<center><h3>Searching i-scream</h3></center>
199	>
200	>	<!-- Search Google -->
201	>	<center>
202	>	<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	>	<input type=hidden name=domains value="i-scream.org">
211	>	<input type=hidden name=sitesearch value="i-scream.org">
212	>	<INPUT TYPE=text name=q size=35 maxlength=255 value="">
213	>	<INPUT type=submit name=sa VALUE="Search">
214	>	<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;AWFID:d646a9fd69e7d9cb;">
215	>	</td>
216	>	</tr>
217	>	</TABLE>
218	>	</FORM>
219	>	</center>
220	>	<!-- Search Google -->
221	>
222		</p>
223		</font>
224		</td>

Diff Legend

–	Removed lines
+	Added lines
<	Changed lines
>	Changed lines