www/cms/index.xhtml

<!--#include virtual="/doctype.inc" -->
  <head>
    <title>
      i-scream CMS homepage
    </title>
<!--#include virtual="/style.inc" -->
  </head>
  <body>
    <div id="container">
      <div id="main">
<!--#include virtual="/header.inc" -->
        <div id="contents">
          <h1 class="top">
            i-scream CMS homepage
          </h1>
          <div id="topnav">
            <ul>
              <li>
                <a href="#overview">Overview</a>
              </li>
              <li>
                <a href="#screenshots">Screen Shots</a>
              </li>
              <li>
                <a href="#demo">Reports Demo</a>
              </li>
              <li>
                <a href="#downloads">Downloads</a>
              </li>
              <li>
                <a href="#documentation">Documentation</a>
              </li>
              <li>
                <a href="#history">Project History</a>
              </li>
            </ul>
          </div>
          <h2>
            <a id="overview">Overview</a>
          </h2>
          <p>
            The i-scream central monitoring system provides a free,
            centrally configurable distributed server to monitor the
            status and performance of Solaris, Linux, FreeBSD and
            Windows machines on a network. The server can raise alerts
            using email, IRC or a large public information display.
            Information may also be browsed interactively via the web
            or using our multi-platform client.
          </p>
          <ul>
            <li>
              <a href="features.xhtml">Features</a>
            </li>
          </ul>
          <p>
            Follow the link above for the original problem
            specification we were given to develop the i-scream CMS,
            and the feature set of the CMS after it was finished.
          </p>
          <h2>
            <a id="screenshots">Screen Shots</a>
          </h2>
          <ul>
            <li>
              <a href="screenshots/">Screen Shots</a>
            </li>
          </ul>
          <p>
            These screenshots were taken at the end of the project, and
            therefore show the old build given below, and none of our
            new features.
          </p>
          <h2>
            <a id="demo">Reports Demo</a>
          </h2>
          <ul>
            <li>
              <a href="reports/">Demo</a>
            </li>
          </ul>
          <p>
            This is a demo of the web-based reports that the i-scream
            system can do. It's taken from the old builds, so doesn't
            show any of the new RRDTool based features.
          </p>
          <h2>
            <a id="downloads">Downloads</a>
          </h2>
          <h3>
            Snapshot Builds
          </h3>
          <ul>
            <li>
              <a href="http://snapshots.i-scream.org">Snapshots</a>
            </li>
          </ul>
          <p>
            Since the project was completed various changes have
            happened in the CMS. These are undocumented, but fairly
            straightforward. We'd strongly suggest you use this version
            of the CMS rather than the builds from the end of the
            project.
          </p>
          <p>
            We've done a fair amount of work on the graphing/database
            side of the CMS, and fixed numerous bugs. Also, the new
            ihost/libstatgrab combination requires the snapshot builds.
          </p>
          <h3>
            Old Builds (from project completion)
          </h3>
          <ul>
            <li>
              <a href="http://www.mirrorservice.org/sites/ftp.i-scream.org/pub/i-scream/cms/">
              Old Builds</a>
            </li>
          </ul>
          <p>
            These builds were completed at the end of the project
            itself. They match with the documentation below, and work.
            But we've done a fair amount of work since creating them.
          </p>
          <h2>
            <a id="documentation">Documentation</a>
          </h2>
          <h3>
            Product documentation
          </h3>
          <ul>
            <li>
              <a href="documentation/">Documentation</a>
            </li>
          </ul>
          <p>
            This documentation was written as the CMS project was
            completed. It therefore applies to the downloads available
            from the time the project finished. There will definately
            be descrepencies between this documentation and the snapshot
            builds.
          </p>
          <h3>
            Javadoc documentation
          </h3>
          <ul>
            <li>
              <a href="javadoc/">Javadoc</a>
            </li>
          </ul>
          <p>
            Each component of the CMS written in java has fairly
            extensive javadoc documentation that helps to explain the
            code and API's.
          </p>
          <h3>
            Process documentation
          </h3>
          <ul>
            <li>
              <a href="minutes.xhtml">Meeting Minutes</a>
            </li>
            <li>
              <a href="projectpapers.xhtml">Documentation</a>
            </li>
          </ul>
          <p>
            Various pieces of documentation were generated during the
            project that were intended for internal use. They're not
            required reading for running the CMS, but might be
            interesting if you're curious about the project itself.
          </p>
          <h2>
            <a id="history">Project History</a>
          </h2>
          <p>
            The i-scream Distributed Central Monitoring System
            started off as a final year project for a group of
            <a href="http://www.cs.kent.ac.uk/">Computer Science</a>
            students at the <a href="http://www.kent.ac.uk/">University
            of Kent</a>, UK. The project was completed at 4pm on
            29 March 2001. It consisted of five lever-arch folders
            containing mostly source code and documentation. The
            CVS repository was tagged to signify this event, however.
          </p>
          <p>
            As can be seen in our "<a href="features.xhtml">problem
            domain</a>" document, the project was aimed at the UKC
            Computer Science department, and as such we believed that a
            demonstration to the "customer" was important. The feedback
            from our demonstation was more positive than we had
            anticipated. We believe that the system may now be of
            interest to anybody who wishes to monitor a number of
            machines on their network using a central configuration.
            The i-scream central monitoring system is now being used by
            the UKC Computer Science department, and their feedback is
            being used to further improve the product.
          </p>
          <p>
            The name <i>i-scream</i> arose from a meeting whereupon one
            member of the development team felt a strange urge to draw
            an ice cream on the discussion board. It later became
            apparent that we had no name for our project (other than
            'The Project'). It seemed only natural to name our project
            after the ice cream that had been oh-so-randomly drawn on
            the white board. Copyright issues immediately ruled out
            anything involving Mr Whippy, so we had to settle for
            <i>i-scream</i>. And thus, we were left with a cunning play
            on words - it still sounded like <i>ice cream</i>, yet also
            served as a functional description of our system - namely,
            one which screams at somebody if something has gone
            wrong...
          </p>
        </div>
<!--#include virtual="/footer.inc" -->
      </div>
<!--#include virtual="/menu.inc" -->
    </div>
  </body>
</html>
Revision:	1.6
Committed:	Thu Jul 22 12:52:11 2004 UTC (20 years, 3 months ago) by tdb
Branch:	MAIN
Changes since 1.5:	+1 -1 lines
Log Message:	Change mirror from mirror.ac.uk to mirrorservice.org.
#	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="http://www.mirrorservice.org/sites/ftp.i-scream.org/pub/i-scream/cms/">
115	Old Builds</a>
116	</li>
117	</ul>
118	<p>
119	These builds were completed at the end of the project
120	itself. They match with the documentation below, and work.
121	But we've done a fair amount of work since creating them.
122	</p>
123	<h2>
124	<a id="documentation">Documentation</a>
125	</h2>
126	<h3>
127	Product documentation
128	</h3>
129	<ul>
130	<li>
131	<a href="documentation/">Documentation</a>
132	</li>
133	</ul>
134	<p>
135	This documentation was written as the CMS project was
136	completed. It therefore applies to the downloads available
137	from the time the project finished. There will definately
138	be descrepencies between this documentation and the snapshot
139	builds.
140	</p>
141	<h3>
142	Javadoc documentation
143	</h3>
144	<ul>
145	<li>
146	<a href="javadoc/">Javadoc</a>
147	</li>
148	</ul>
149	<p>
150	Each component of the CMS written in java has fairly
151	extensive javadoc documentation that helps to explain the
152	code and API's.
153	</p>
154	<h3>
155	Process documentation
156	</h3>
157	<ul>
158	<li>
159	<a href="minutes.xhtml">Meeting Minutes</a>
160	</li>
161	<li>
162	<a href="projectpapers.xhtml">Documentation</a>
163	</li>
164	</ul>
165	<p>
166	Various pieces of documentation were generated during the
167	project that were intended for internal use. They're not
168	required reading for running the CMS, but might be
169	interesting if you're curious about the project itself.
170	</p>
171	<h2>
172	<a id="history">Project History</a>
173	</h2>
174	<p>
175	The i-scream Distributed Central Monitoring System
176	started off as a final year project for a group of
177	<a href="http://www.cs.kent.ac.uk/">Computer Science</a>
178	students at the <a href="http://www.kent.ac.uk/">University
179	of Kent</a>, UK. The project was completed at 4pm on
180	29 March 2001. It consisted of five lever-arch folders
181	containing mostly source code and documentation. The
182	CVS repository was tagged to signify this event, however.
183	</p>
184	<p>
185	As can be seen in our "<a href="features.xhtml">problem
186	domain</a>" document, the project was aimed at the UKC
187	Computer Science department, and as such we believed that a
188	demonstration to the "customer" was important. The feedback
189	from our demonstation was more positive than we had
190	anticipated. We believe that the system may now be of
191	interest to anybody who wishes to monitor a number of
192	machines on their network using a central configuration.
193	The i-scream central monitoring system is now being used by
194	the UKC Computer Science department, and their feedback is
195	being used to further improve the product.
196	</p>
197	<p>
198	The name <i>i-scream</i> arose from a meeting whereupon one
199	member of the development team felt a strange urge to draw
200	an ice cream on the discussion board. It later became
201	apparent that we had no name for our project (other than
202	'The Project'). It seemed only natural to name our project
203	after the ice cream that had been oh-so-randomly drawn on
204	the white board. Copyright issues immediately ruled out
205	anything involving Mr Whippy, so we had to settle for
206	<i>i-scream</i>. And thus, we were left with a cunning play
207	on words - it still sounded like <i>ice cream</i>, yet also
208	served as a functional description of our system - namely,
209	one which screams at somebody if something has gone
210	wrong...
211	</p>
212	</div>
213	<!--#include virtual="/footer.inc" -->
214	</div>
215	<!--#include virtual="/menu.inc" -->
216	</div>
217	</body>
218	</html>