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

Diff Legend

Removed lines
+ Added lines
< Changed lines
> Changed lines