1 |
tdb |
1.1 |
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" |
2 |
|
|
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> |
3 |
|
|
|
4 |
|
|
<html> |
5 |
|
|
|
6 |
|
|
<head> |
7 |
|
|
<title>i-scream CMS homepage</title> |
8 |
|
|
<!--#include virtual="/style.inc" --> |
9 |
|
|
</head> |
10 |
|
|
|
11 |
|
|
<body> |
12 |
|
|
|
13 |
|
|
<div id="container"> |
14 |
|
|
|
15 |
|
|
<div id="main"> |
16 |
|
|
|
17 |
|
|
<!--#include virtual="/header.inc" --> |
18 |
|
|
|
19 |
|
|
<div id="contents"> |
20 |
|
|
<h1 class="top">i-scream CMS homepage</h1> |
21 |
|
|
|
22 |
|
|
<div id="topnav"> |
23 |
|
|
<ul> |
24 |
|
|
<li><a href="#overview">Overview</a></li> |
25 |
|
|
<li><a href="#screenshots">Screen Shots</a></li> |
26 |
|
|
<li><a href="#demo">Reports Demo</a></li> |
27 |
|
|
<li><a href="#downloads">Downloads</a></li> |
28 |
|
|
<li><a href="#documentation">Documentation</a></li> |
29 |
|
|
<li><a href="#history">Project History</a></li> |
30 |
|
|
</ul> |
31 |
|
|
</div> |
32 |
|
|
|
33 |
|
|
<h2><a name="overview">Overview</a></h2> |
34 |
|
|
<p> |
35 |
|
|
The i-scream central monitoring system provides a free, centrally |
36 |
|
|
configurable distributed server to monitor the status and |
37 |
|
|
performance of Solaris, Linux, FreeBSD and Windows machines |
38 |
|
|
on a network. The server can raise alerts using email, IRC or |
39 |
|
|
a large public information display. Information may also be |
40 |
|
|
browsed interactively via the web or using our multi-platform |
41 |
|
|
client. |
42 |
|
|
</p> |
43 |
|
|
<ul> |
44 |
|
|
<li><a href="features.shtml">Features</a></li> |
45 |
|
|
</ul> |
46 |
|
|
<p> |
47 |
|
|
Follow the link above for the original problem specification |
48 |
|
|
we were given to develop the i-scream CMS, and the feature set |
49 |
|
|
of the CMS after it was finished. |
50 |
|
|
</p> |
51 |
|
|
|
52 |
|
|
<h2><a name="screenshots">Screen Shots</a></h2> |
53 |
|
|
<ul> |
54 |
|
|
<li><a href="screenshots/">Screen Shots</a></li> |
55 |
|
|
</ul> |
56 |
|
|
<p> |
57 |
|
|
These screenshots were taken at the end of the project, and |
58 |
|
|
therefore show the old build given below, and none of our new |
59 |
|
|
features. |
60 |
|
|
</p> |
61 |
|
|
|
62 |
|
|
<h2><a name="demo">Reports Demo</a></h2> |
63 |
|
|
<ul> |
64 |
|
|
<li><a href="reports/">Demo</a></li> |
65 |
|
|
</ul> |
66 |
|
|
<p> |
67 |
|
|
This is a demo of the web-based reports that the i-scream system |
68 |
|
|
can do. It's taken from the old builds, so doesn't show any of |
69 |
|
|
the new RRDTool based features. |
70 |
|
|
</p> |
71 |
|
|
|
72 |
|
|
<h2><a name="downloads">Downloads</a></h2> |
73 |
|
|
|
74 |
|
|
<h3>Snapshot Builds</h3> |
75 |
|
|
<ul> |
76 |
|
|
<li><a href="http://snapshots.i-scream.org">Snapshots</a></li> |
77 |
|
|
</ul> |
78 |
|
|
<p> |
79 |
|
|
Since the project was completed various changes have happened |
80 |
|
|
in the CMS. These are undocumented, but fairly straightforward. |
81 |
|
|
We'd strongly suggest you use this version of the CMS rather |
82 |
|
|
than the builds from the end of the project. |
83 |
|
|
</p> |
84 |
|
|
<p> |
85 |
|
|
We've done a fair amount of work on the graphing/database side |
86 |
|
|
of the CMS, and fixed numerous bugs. Also, the new ihost/libstatgrab |
87 |
|
|
combination requires the snapshot builds. |
88 |
|
|
</p> |
89 |
|
|
|
90 |
|
|
<h3>Old Builds (from project completion)</h3> |
91 |
|
|
<ul> |
92 |
|
|
<li><a href="/pub/i-scream/cms/">Old Builds</a></li> |
93 |
|
|
</ul> |
94 |
|
|
<p> |
95 |
|
|
These builds were completed at the end of the project itself. |
96 |
|
|
They match with the documentation below, and work. But we've |
97 |
|
|
done a fair amount of work since creating them. |
98 |
|
|
</p> |
99 |
|
|
|
100 |
|
|
<h2><a name="documentation">Documentation</a></h2> |
101 |
|
|
|
102 |
|
|
<h3>Product documentation</h3> |
103 |
|
|
<ul> |
104 |
|
|
<li><a href="documentation/">Documentation</a></li> |
105 |
|
|
</ul> |
106 |
|
|
<p> |
107 |
|
|
This documentation was written as the CMS project was completed. |
108 |
|
|
It therefore applies to the downloads available from the time |
109 |
|
|
the project finished. There will definately be descrepences |
110 |
|
|
between this documentation and the snapshot builds. |
111 |
|
|
</p> |
112 |
|
|
|
113 |
|
|
<h3>Javadoc documentation</h3> |
114 |
|
|
<ul> |
115 |
|
|
<li><a href="javadoc/">Javadoc</a></li> |
116 |
|
|
</ul> |
117 |
|
|
<p> |
118 |
|
|
Each component of the CMS written in java has fairly extensive |
119 |
|
|
javadoc documentation that helps to explain the code and API's. |
120 |
|
|
</p> |
121 |
|
|
|
122 |
|
|
<h3>Process documentation</h3> |
123 |
|
|
<ul> |
124 |
|
|
<li><a href="minutes.shtml">Meeting Minutes</a></li> |
125 |
|
|
<li><a href="projectpapers.shtml">Documentation</a></li> |
126 |
|
|
</ul> |
127 |
|
|
<p> |
128 |
|
|
Various pieces of documentation were generated during the project |
129 |
|
|
that were intended for internal use. They're not required reading |
130 |
|
|
for running the CMS, but might be interesting if you're curious |
131 |
|
|
about the project itself. |
132 |
|
|
</p> |
133 |
|
|
|
134 |
|
|
<h2><a name="history">Project History</a></h2> |
135 |
|
|
|
136 |
|
|
<p> |
137 |
|
|
The i-scream Distributed Central Monitoring System started off |
138 |
|
|
as a final year project for a group of <a |
139 |
|
|
href="http://www.cs.kent.ac.uk/"> Computer Science</a> students |
140 |
|
|
at the <a href="http://www.kent.ac.uk/"> University of Kent</a>, |
141 |
|
|
UK. The project was completed at 4pm on 29 March 2001. It |
142 |
|
|
consisted of five lever-arch folders containing mostly source |
143 |
|
|
code and documentation. The CVS repository was tagged to signify |
144 |
|
|
this event, however. |
145 |
|
|
</p> |
146 |
|
|
<p> |
147 |
|
|
As can be seen in our "<a href="features.shtml">problem |
148 |
|
|
domain</a>" document, the project was aimed at the UKC |
149 |
|
|
Computer Science department, and as such we believed that a |
150 |
|
|
demonstration to the "customer" was important. The |
151 |
|
|
feedback from our demonstation was more positive than we had |
152 |
|
|
anticipated. We believe that the system may now be of interest |
153 |
|
|
to anybody who wishes to monitor a number of machines on their |
154 |
|
|
network using a central configuration. The i-scream central |
155 |
|
|
monitoring system is now being used by the UKC Computer Science |
156 |
|
|
department, and their feedback is being used to further improve |
157 |
|
|
the product. |
158 |
|
|
</p> |
159 |
|
|
<p> |
160 |
|
|
The name <i>i-scream</i> arose from a meeting whereupon one |
161 |
|
|
member of the development team felt a strange urge to draw an |
162 |
|
|
ice cream on the discussion board. It later became apparent |
163 |
|
|
that we had no name for our project (other than 'The Project'). |
164 |
|
|
It seemed only natural to name our project after the ice cream |
165 |
|
|
that had been oh-so-randomly drawn on the white board. Copyright |
166 |
|
|
issues immediately ruled out anything involving Mr Whippy, so |
167 |
|
|
we had to settle for <i>i-scream</i>. And thus, we were left |
168 |
|
|
with a cunning play on words - it still sounded like <i>ice |
169 |
|
|
cream</i>, yet also served as a functional description of our |
170 |
|
|
system - namely, one which screams at somebody if something has |
171 |
|
|
gone wrong... |
172 |
|
|
</p> |
173 |
|
|
|
174 |
|
|
</div> |
175 |
|
|
|
176 |
|
|
<!--#include virtual="/footer.inc" --> |
177 |
|
|
|
178 |
|
|
</div> |
179 |
|
|
|
180 |
|
|
<!--#include virtual="/menu.inc" --> |
181 |
|
|
|
182 |
|
|
</div> |
183 |
|
|
|
184 |
|
|
</body> |
185 |
|
|
</html> |