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

Diff Legend

Removed lines
+ Added lines
< Changed lines
> Changed lines