ViewVC Help
View File | Revision Log | Show Annotations | Revision Graph | Root Listing
root/i-scream/web/www/cms/index.xhtml
Revision: 1.11
Committed: Wed Jun 5 10:49:40 2013 UTC (11 years, 4 months ago) by tdb
Branch: MAIN
CVS Tags: HEAD
Changes since 1.10: +0 -1 lines
Error occurred while calculating annotation data.
Log Message:
Remove adverts.

File Contents

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