ViewVC Help
View File | Revision Log | Show Annotations | Revision Graph | Root Listing
root/i-scream/web/www/cms/index.xhtml
Revision: 1.3
Committed: Tue Mar 23 20:22:31 2004 UTC (20 years, 7 months ago) by tdb
Branch: MAIN
Changes since 1.2: +5 -8 lines
Log Message:
Move to .xhtml files instead of .shtml. They still use SSI.

We're now validating as XHTML 1.1 (or, at least we will be when I've tested
every page of the site to make sure it validates). I've put the necessary
frigs in the webserver so it returns the content-type as text/html if the
web browser doesn't make any claims to know about application/xhtml+xml
(which is the content type defined by the XHTML standards).

File Contents

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