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

Diff Legend

Removed lines
+ Added lines
< Changed lines
> Changed lines