ViewVC Help
View File | Revision Log | Show Annotations | Revision Graph | Root Listing
root/i-scream/web/www/contents.inc
(Generate patch)

Comparing web/www/contents.inc (file contents):
Revision 1.24 by tdb, Tue Jul 10 08:54:30 2001 UTC vs.
Revision 1.51 by tdb, Fri Oct 10 10:42:55 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
18 <        design parameters and our system is regarded to be complete.
19 <        <b><a href="documentation/">Documentation</a></b> is available to assist third party programmers
20 <        in producing Hosts for use with the i-scream server.
21 <        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>Thursday 09 October 2003</b><br><br>
16 >        <a href="/libstatgrab">libstatgrab</a> 0.6 has been released.
17         </p>
18  
19         <p align="justify">
20 <        <a href="screenshots/"><img border="0" src="screenshots/thumbnail-winhost-main.gif" width="100" height="62" align="right"></a>
21 <        
28 <        The i-scream Distributed Central Monitoring System Reports
29 <        are now visible on the web.  If you are <b>not</b> a local user, then you may
30 <        view some of the output in the <b><a href="screenshots/">screen shots</a></b> section or you may view some
31 <        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>
20 >        <b>Tuesday 09 September 2003</b><br><br>
21 >        <a href="/libstatgrab">libstatgrab</a> 0.5.1 has been released.
22         </p>
23  
24         <p align="justify">
25 <        <a href="screenshots/"><img border="0" src="screenshots/thumbnail-conient-main.gif" width="100" height="107" align="left"></a>
26 <        Our current host development allows us to pass machine statistics
42 <        to our distributed filter arrangement, which then processes the
43 <        data and stores it for later use.  An example of such use is the
44 <        historical report generator which produces graphs of machine
45 <        usage over periods of time.  A real-time
46 <        client is also available (Conient) and alert information can be
47 <        displayed to the public via dynamic web pages.
25 >        <b>Monday 25 August 2003</b><br><br>
26 >        <a href="/libstatgrab">libstatgrab</a> 0.5 has been released.
27         </p>
28 +
29 +       <p align="justify">
30 +        <b>Tuesday 15 July 2003</b><br><br>
31 +        We have moved the i-scream support and bug tracking to a new
32 +        facility on the i-scream server. For further details please
33 +        see <a href="/support.shtml">this</a> page.
34 +       </p>
35        
36         <p align="justify">
37 <        <a href="screenshots/"><img border="0" src="screenshots/thumbnail-alerter-email.gif" width="100" height="107" align="right"></a>
38 <        The latest builds of the i-scream Distributed Central Monitoring System
39 <        are now available for <b><a href="/downloads/">download</a></b> from this
40 <        website.  To assist in our addition of features to the system, we
41 <        would be extremely grateful to receive feedback from anybody who has
42 <        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>
37 >        <b>Sunday 8 June 2003</b><br><br>
38 >        The i-scream website, email, and cvs facilities are now all
39 >        run from a <a href="http://www.freebsd.org">FreeBSD</a> server.<br>
40 >        <a href="http://www.freebsd.org">
41 >         <img src="/powerlogo.gif" width="171" height="64" border="0" alt="Powered By FreeBSD">
42 >        </a>
43         </p>
44 +      
45 +       <p align="justify">
46 +        <b>Tuesday 4 February 2003</b><br><br>
47 +        Over the coming week we will be making snapshot builds of the
48 +        i-scream central monitoring system from the CVS repository.
49 +        These builds will have quite a few changes from the downloads
50 +        currently available (a document detailing them will be
51 +        released later on), so please give them a whirl. We would be
52 +        grateful if you <a href="mailto:dev@i-scream.org">contacted</a>
53 +        us with any questions or bugs.<br><br>
54 +        The downloads will be available on our snapshot server :-<br>
55 +        <a href="http://snapshots.i-scream.org/">
56 +        http://snapshots.i-scream.org/</a>.
57 +       </p>
58  
59 +       <p align="justify">
60 +        <b>Saturday 1 June 2002</b><br><br>
61 +        Work has now been finished on a new ihost written in C. This has
62 +        been in the pipeline for a long time, and we're glad to finally
63 +        see an efficient native host! Credit goes to our new developer
64 +        <a href="/who.shtml">Pete</a>. Until we update the downloads
65 +        pages you can download the new ihost
66 +        <a href="ftp://ftp.i-scream.org/pub/i-scream/ihost/">
67 +        here</a>.
68 +       </p>
69 +
70 +       <p align="justify">
71 +        <b>Tuesday 21 May 2002</b><br><br>
72 +        We've finally put the finishing touches to the new
73 +        <a href="http://rrdtool.eu.org">RRDtool</a> based graphing system.
74 +        It's working well, and has done away with the MySQL database
75 +        backend which took up far too many resources. This new system
76 +        generates the graphs in a more realtime nature, allowing more
77 +        flexible graphs to be generated. This is currently only available
78 +        through <a href="http://cvs.i-scream.org/cms/source/reports/rrdgraphing/">
79 +        CVS</a>.
80 +       </p>
81 +
82 +       <p align="justify">
83 +        <b>Tuesday 8 Jan 2002</b><br><br>
84 +        Java ACL (Access Control List) code has been added to the util
85 +        package of the i-scream server. This code will ultimately allow
86 +        the server to be more secure when exposed to the Internet. More
87 +        details can be found <a href="http://www.cs.kent.ac.uk/people/staff/tdb/#acl">
88 +        here</a> on the author's website.
89 +       </p>
90 +      
91         <p>&nbsp;</p>
92 <       <center><h3>Project Completion</h3></center>
92 >       <center><h3>About i-scream</h3></center>
93 >      
94 >       <p align="justify">
95 >        <a href="screenshots/"><img border="0" src="screenshots/thumbnail-alerter-email.gif" width="100" height="107" align="left"></a>
96 >        Details of the i-scream central monitoring system can be found
97 >        on the <b><a href="features.shtml">features and overview</a></b> page.
98 >        A variety of <b><a href="screenshots">screen shots</a></b> from the
99 >        system show some of the key features in use. The <b><a href="reports">reports demo</a></b>
100 >        page provides a static example of what the i-scream reports (alerts,
101 >        historical graphs, and live data) could look like on a production system.
102 >       </p>
103 >      
104 >       <p align="justify">
105 >        <a href="screenshots/"><img border="0" src="screenshots/thumbnail-conient-main.gif" width="100" height="107" align="right"></a>
106 >        The latest source code is available in the <b><a href="cvs.shtml">CVS</a></b>
107 >        repository, with binary downloads on the downloads page. The
108 >        <b><a href="documentation">documentation</a></b> page has details of
109 >        installation, use and maintenance for the end user and developer.
110 >        We value feedback and comments from you, so please drop us an e-mail
111 >        to <a href="mailto:dev@i-scream.org">dev@i-scream.org</a>.
112 >       </p>
113 >      
114 >       <p>&nbsp;</p>
115 >       <center><h3>Current Work</h3></center>
116 >      
117 >       <p align="justify">
118 >        <b>Extending monitoring facilites</b><br><br>
119 >        <a href="screenshots/"><img border="0" src="screenshots/thumbnail-reports-raptor-load15.gif" width="100" height="107" align="left"></a>
120 >        Work is continuing, in conjunction with the new ihost, to extend
121 >        the range of i-scream's monitoring. Currently we are adding new
122 >        features to more accurately monitoring memory and swap usage,
123 >        along with more disk statistics. We are also planning to improve
124 >        the rather basic service monitors which are currently in place.
125 >        There are also many more subtle changes that need to be made to
126 >        improve the reliability and usefulness of i-scream's monitoring.
127 >       </p>
128  
129         <p align="justify">
130 +        <b>Server security</b><br><br>
131 +        Security was something mostly overlooked in the original stage
132 +        of this project (due to the academic nature of the work). However,
133 +        once in production use this has become an issue, and is being
134 +        addressed. Initially the plan is to lock down the external points
135 +        of access (TCP & UDP) in the server to specific hosts. In the
136 +        longer term, encryption of data would be nice, but would take a
137 +        lot more time and work.
138 +       </p>
139 +      
140 +       <p align="justify">
141 +        <b>Testing and Development</b><br><br>
142 +        <a href="screenshots/"><img border="0" src="screenshots/thumbnail-winhost-main.gif" width="100" height="62" align="right"></a>
143 +        The i-scream system is being tested and developed within the
144 +        Univeristy of Kent Computer Science department by the Systems
145 +        Group. This has led to many bug fixes and minor feature
146 +        enhancements, and will hopefully help to aid the long term
147 +        development of the system.
148 +       </p>
149 +      
150 +       <p>&nbsp;</p>
151 +       <center><h3>Project History</h3></center>
152 +
153 +       <p align="justify">
154          <a href="screenshots/"><img border="0" src="screenshots/thumbnail-reports-raptor-latest-misc.gif" width="100" height="104" align="left"></a>
155          The i-scream Distributed Central Monitoring System started off as
156 <        a final year project for a group of <a href="http://www.cs.ukc.ac.uk">Computer Science</a> students at
157 <        the <a href="http://www.ukc.ac.uk">University of Kent at Canterbury</a>, UK.
158 <        The project deadline was 4pm on 29th March 2001.  Most of the group
159 <        met very early that morning to compile the project into five
160 <        lever arch folders.  The project, consisting of source code, user,
161 <        maintenance and other documents, was handed in at 3pm.  The CVS
162 <        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.
156 >        a final year project for a group of <a href="http://www.cs.kent.ac.uk">
157 >        Computer Science</a> students at the <a href="http://www.kent.ac.uk">
158 >        University of Kent at Canterbury</a>, UK. The project was completed at
159 >        4pm on 29 March 2001. It consisted of five lever-arch folders containing
160 >        mostly source code and documentation. The CVS repository was tagged to
161 >        signify this even, however, the project is still being developed by the
162 >        <a href="acknowledgements.shtml">core development team</a>.
163         </p>
164        
165         <p align="justify">
# Line 82 | Line 168
168          was aimed at the UKC Computer Science department, and as such
169          we believed that a demonstration to the &quot;customer&quot; was important. The
170          feedback from our demonstation was more positive than we had
171 <        anticipated. We believe that the system may now be of great
172 <        interest to anybody who wishes to monitor a number of machines
173 <        on their network using a central configuration.
171 >        anticipated. We believe that the system may now be of interest
172 >        to anybody who wishes to monitor a number of machines on their
173 >        network using a central configuration. The i-scream central
174 >        monitoring system is now being used by the UKC Computer Science
175 >        department, and their feedback is being used to further improve
176 >        the product.
177         </p>
178  
90       <p>&nbsp;</p>
91       <center><h3>Naming History</h3></center>
92
179         <p align="justify">
180          <a href="screenshots/"><img border="0" src="screenshots/thumbnail-conient-config.gif" width="100" height="48" align="left"></a>
181          The name <i>i-scream</i> arose from a meeting whereupon one member
# Line 100 | Line 186
186          Copyright issues immediately ruled out anything involving Mr Whippy,
187          so we had to settle for <i>i-scream</i>. And thus, we were left with a cunning
188          play on words - it still sounded like <i>ice cream</i>, yet also
189 <        served as a functional decription of our system - namely, one which
189 >        served as a functional description of our system - namely, one which
190          screams at somebody if something has gone wrong...
191         </p>
192         <p align="justify">
193        
194         <p>&nbsp;</p>
195 <       <center><h3>Searching</h3></center>
195 >       <center><h3>Searching i-scream</h3></center>
196        
197         <!-- Search Google -->
198         <center>
199 <       <FORM method=GET action=http://www.google.com/custom>
200 <       <TABLE bgcolor=#FFFFFF cellspacing=0 border=0>
201 <       <tr valign=top><td>
202 <       <A HREF=http://www.google.com/search>
203 <       <IMG SRC=http://www.google.com/logos/Logo_40wht.gif border=0 ALT=Google align=middle width="128" height="53"></A>
204 <       </td>
205 <       <td>
206 <       <font face=arial,sans-serif size=-1><input type=hidden name=domains value="i-scream.org.uk"><input type=radio name=sitesearch value="i-scream.org.uk" checked> search i-scream <input type=radio name=sitesearch value=""> search google </font><br>
207 <       <INPUT TYPE=text name=q size=35 maxlength=255 value="">
208 <       <INPUT type=submit name=sa VALUE="Search">
209 <       <INPUT type=hidden name=cof VALUE="T:#000066;LW:502;ALC:#3333cc;L:http://www.i-scream.org.uk/i-scream.gif;LC:#0000ff;LH:37;BGC:#ffffff;AH:left;VLC:#3333cc;AWFID:d646a9fd69e7d9cb;">
210 <       </td></tr></TABLE>
211 <       </FORM>
199 >        <FORM method=GET action=http://www.google.com/custom>
200 >         <TABLE bgcolor=#FFFFFF cellspacing=0 border=0>
201 >          <tr>
202 >           <td valign="middle">
203 >            <A HREF=http://www.google.com/search>
204 >            <IMG SRC=http://www.google.com/logos/Logo_40wht.gif border=0 ALT=Google align=middle width="128" height="53"></A>
205 >           </td>
206 >           <td valign="middle">
207 >            <input type=hidden name=domains value="i-scream.org;i-scream.org.uk">
208 >            <input type=hidden name=sitesearch value="i-scream.org">
209 >            <INPUT TYPE=text name=q size=35 maxlength=255 value="">
210 >            <INPUT type=submit name=sa VALUE="Search">
211 >            <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;">
212 >           </td>
213 >          </tr>
214 >         </TABLE>
215 >        </FORM>
216         </center>
217         <!-- Search Google -->
218        

Diff Legend

Removed lines
+ Added lines
< Changed lines
> Changed lines