|
|
| Line 1: |
Line 1: |
| − | [[COSMOS|COSMOS Main Page]] > [[COSMOSF2F-Toronto-Jan-06]]
| |
| | | | |
| − |
| |
| − | == Overview ==
| |
| − | The objective of the COSMOS demo is to present an overview of the project, our progress to date, and explain the key value adds to the Systems Management community.
| |
| − |
| |
| − | We will need to focus the presentation given the 30 minute time limit. Even though chart ware is strongly discouraged in a demo, we will need one chart for the project overview, one to explain SML/CML, and one roadmap & wrap up slide. That will leave about 20 minutes of demo-able material.
| |
| − |
| |
| − | Since SML & CML is the new new thing and is a fundamental part of the project, we will concentrate of showing how SML & CML can be used in monitoring systems as an interface between data producers and data consumers in order to facilitate interoperability among operations management tools.
| |
| − |
| |
| − |
| |
| − | == The Script ==
| |
| − | * The demo starts with a web browser open to an empty page.
| |
| − | * Enter the URL that shows a list of available topologies that can be viewed.
| |
| − | ** Harm initially questioned why the topology "viewer" could not be a BIRT report. If we did this the initial report navigator could be ther BIRT servlet and the the topologies would become a BIRT report. This would allow us to use the BIRT designer to reflect the top level view.
| |
| − | * The initial set returned contains no data.
| |
| − | * Switch to Eclipse and show the project containing the SML files. Open the topology file and show the SML that represents the topology.
| |
| − | ** Show & discuss the validation work that Valentina is doing.
| |
| − | * Make the file available to the web app (e.g. copy it to web inf). (''instead of copying, why not just have the project in that location?'')
| |
| − | * Refresh the browser.
| |
| − | *Select a topology node.
| |
| − | ** The browser opens to show the top level nodes of a topology. In this case, it should show a collection of machines. Each machine should have a name and id. Each node should display what information is available to view and what other children nodes it is related to. The topology should show the operating system. There should be two one with windows and one with linux.
| |
| − | * Select the windows OS
| |
| − | ** The initial set of information that is available for the windows machine should be limited to the applications that are deployed on it, e.g. Tomcat.
| |
| − | ** Open the SML file and add the entry that indicates log file information is available and statistical information is available.
| |
| − | ** Refresh the page
| |
| − | *** The page contains the log and stat information.
| |
| − | *** Select the report that shows the log information. [[COSMOSSampleReport|SampleReport]]
| |
| − | *** It should be possible to navigate into the event detail that is in the log.
| |
| − | ** From the Operating System view, select the Tomcat Application Server
| |
| − | *** The information for Tomcat is displayed. It shows the hosted application deployed in it. There are no logs or statistical information available for it.
| |
| − | ** Select the application.
| |
| − | *** There is no information available.
| |
| − | *** Edit the SML topology file to add the log information. Discuss how BtM was used to instrument the application with CBE.
| |
| − | *** Refresh the view.
| |
| − | ** The application now shows that log information is available for the application.
| |
| − | *** Select the report showing the log information.
| |
| − | * Wrap up and big finish
| |
| − | ** '''CALL TO ACTION '''
| |
| − | ** Deliver our message
| |
| − | *** Handout (or gizmo thing) with community information (call in info, meeting times, cosmos home page)
| |
| − |
| |
| − | == The Messages ==
| |
| − |
| |
| − | By following the script we can deliver the following messages
| |
| − |
| |
| − | (not necessarily in this order)
| |
| − |
| |
| − | * COSMOS is a project that is starting to deliver some basic value
| |
| − | * We can tie together the full life cycle of systems management from development (BtM/ME) to production (COSMOS reports)
| |
| − | ** In the scenario, we can talk about how the current BtM tooling for CBE was used to generate the CBEs that get stored in the data store. We can say how the WSDM tooling was used to create the WEF events that get stored in there as well.
| |
| − | ** We can indicate how ME was used to configure/update the SML-IF documents that described the management capabilities of the system under test, e.g. if log or statistical data was avaialable.
| |
| − | ** We talk to the standard based control layer (stretch goal is to show it)
| |
| − | *** Note: We can turn on collection manually possibly if we wated to show live data. I think this should be a stretch goal once we get everything working. The progression would be:
| |
| − | **** Show the ez-bake oven approach to the data store.
| |
| − | **** Turn on data collection manually and show real event data
| |
| − | **** Use web pages to control the collection (SML-IF would play a part here)
| |
| − | ** We show re-use/collaboration between the projects (TPTP/COSMOS)
| |
| − | ** We show web-based reports (initially derived from the TPTP reports)
| |
| − | * We can indicate the importance of using a model based approach in systems management (and our model language is SML/CML)
| |
