--- web/www/cms/index.xhtml 2004/03/23 20:22:31 1.3 +++ web/www/cms/index.xhtml 2004/08/01 15:29:04 1.9 @@ -1,182 +1,219 @@ <!--#include virtual="/doctype.inc" --> - -<head> -<title>i-scream CMS homepage</title> + <head> + <title> + i-scream CMS homepage + </title> <!--#include virtual="/style.inc" --> -</head> - -<body> - -<div id="container"> - -<div id="main"> - + </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 name="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 name="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 name="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 name="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.mirror.ac.uk/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 name="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 descrepences - 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 name="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> - + <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="/mirrors.xhtml">Download Mirrors</a> + </li> + </ul> + <p> + These builds can be found in the <code>cms</code> directory + on our download mirrors. They were completed at the end + of the project itself, and 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> - + </div> <!--#include virtual="/menu.inc" --> - -</div> - -</body> + </div> + </body> </html>