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

Diff Legend

Removed lines
+ Added lines
< Changed lines
> Changed lines