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.9 by tdb, Wed Feb 28 16:53:17 2001 UTC vs.
Revision 1.41 by tdb, Sun Jun 8 12:14:21 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 <        Most i-scream components are now functioning to initial
16 <        design parameters and data can now be passed through the
17 <        system and displayed successfully. Documentation is still
18 <        being generated, to allow for future development of the
19 <        i-scream project. Detailed information can usually be
20 <        found in the meeting minutes. Code is viewable via CVS
22 <        to UKC 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.
18 >        <a href="http://www.freebsd.org">
19 >         <img src="/powerlogo.gif border="0" alt="Powered By FreeBSD">
20 >        </a>
21         </p>
22  
23         <p align="justify">
24 <        The i-scream Distributed Central Monitoring System <a href="http://raptor.ukc.ac.uk/~pjm2/reports/browser.php">Reports</a>
25 <        are now visible on the web.  You may view all reports
26 <        available for each day, but please remember that this is
27 <        work in progress still, so the only data currently viewable
28 <        is our own data that has been harvested by our own testing.
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 <        Our current host development allows us to pass machine statistics
48 <        to our distributed filter arrangement, which then processes the
49 <        data and stores it for later use.  An example of such use is the
50 <        historical report generator which produces graphs of machine
51 <        usage over periods of time (viewable in a web browser).  Realtime
52 <        clients are also currently being developed - one Java Swing GUI
53 <        version and also a command line version that can run in a terminal
54 <        window. Alerting mechanisms are being put in place to complete the
41 <        i-scream system.
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 <        Builds of the i-scream Distributed Central Monitoring System
87 <        are now available for <a href="/builds/">download</a> from this
88 <        website. These are still very much in development, are should
89 <        only be used by people who have been in communication with the
90 <        development team.
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 <        The project deadline is 4pm on 29 March. As such, we plan to
158 <        complete the coding process by (at the latest) the end of the
159 <        project week (26/2 - 2/3). This allows time for documentation
160 <        to be tidied up and completed, and printing of the project.
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.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">
169 <        As can be seen in the "problem domain" document, the project
169 >        <a href="screenshots/"><img border="0" src="screenshots/thumbnail-ihost-main.gif" width="100" height="51" align="right"></a>
170 >        As can be seen in our &quot;<a href="/probdomain.shtml">problem domain</a>&quot; document, the project
171          was aimed at the UKC Computer Science department, and as such
172 <        we believe a demonstration to the "customer" is important. We
173 <        plan to do this over the next two weeks, and the feedback given
174 <        will allow any "last minute" alterations to be completed.
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 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  
70       <p>&nbsp;</p>
71       <center><h3>Naming History</h3></center>
72
182         <p align="justify">
183 <        The name <b>i-scream</b> arose from a meeting whereupon one member
184 <        of our group randomly chose to draw an ice cream on the white board.
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
185 >        of the <a href="acknowledgements.shtml">development team</a> felt a strange urge to draw an ice cream on the discussion board.
186          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 <        so we had to settle for <b>i-scream</b>. And thus, we were left with a cunning
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