Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "COSMOSF2F-Toronto-Jan-06"

(Minutes)
(Minutes)
Line 85: Line 85:
 
The other advantage to taking a standards based approach is that each part of the infrastructure could automatically discover and bind to the other parts.  This would be similar to taking a SOA based approach where SCA could be used to “wire” together a systems management infrastructure.   
 
The other advantage to taking a standards based approach is that each part of the infrastructure could automatically discover and bind to the other parts.  This would be similar to taking a SOA based approach where SCA could be used to “wire” together a systems management infrastructure.   
  
This approach would also allow an optimization to happen that would short circuit any remote connections.  Everyone agreed this should be explored in more detail.
+
This approach would also allow an optimization to happen that would short circuit any remote connections.  The use of Tuscany was brough up, and this was generally viewed positively, although the full implications of adding a dependency on this project was unclear.  Everyone agreed this should be explored in more detail.
  
  

Revision as of 13:46, 17 January 2007

COSMOS Main Page

Overview

The COSMOS team is having a face to face that bookends the TPTP face to face in Toronto, CA, Jan 8 - 12, 2006.

Daily Conference Calls

We will hold daily conference calls at 11:00am and 5:00pm EST.

Call in number 888 241 8547 pc: 999451

Attendees

Mark Weitzel (Jan 8 - Jan 12)

Harm Sluiman (Jan 8 - Jan 12)

Valentina Popescu ( Jan 8 - Jan 12; not available from 1-4PM Jan 8 )

Don Ebright (Jan 8 - Jan 9 morning and early afternoon)

Joel Hawkins (Jan 8 - Jan 9 morning and early afternoon)

Oliver Cole (??)

Hubert Leung

Marius Slavescu (Jan 8 - Jan 10, Jan 12)

Joseph P Toomey (Jan 8 - Jan 10)

Agenda

The agenda contains a section for questions/discussions/issues we want to work through with the TPTP team.

The main goal is to establsh a project plan, resource assignments, and set of deliverables necessary to realize the initial COSMOS prototype

Monday Jan 8

I (Don) wrote this agenda but feel free to make changes

  • 8:00 Review current status and plans for TPTP AC and agents
  • 8:30 Long term requirements for TPTP and COSMOS agent infrastructure
  • 9:00 Data collection query interface
  • 11:00 Conference call
  • 11:30 Lunch / Demo of portal based log viewer (tentative)
  • 12:00 OSGi based agent control framework
  • 2:00 Data normalization
    • TPTP APIs, new and existing
  • 4:00 Anything else
  • 5:00 Conference call

Attendees

Mark Weitzel, Harm Sluiman, Joel Hawkins, Don Ebright, Hubert Leung, Marius Slavescu, Valentina Popescu, Zulah Eckert (for OSGi discussion)

Minutes

We started the first part of the meeting understanding the current history of the TPTP architecture, in particular the RAC and the existing models that it uses.

There are five models in TPTP, Hierarchy, Statistical, Log, Trace and Test. Of immediate relevance to COSMOS are the Hierarchy, Statistical, and Log models.

TptpModels.gif

In TPTP, the existing models reside in memory and are created using EMF. In several areas, the use of EMF bleeds through to the API layer. It was agreed that we did not want EMF to be surfaced in the API layers in the data collection work. That applied to both the writing of data and the reading of data.

  • The working assumption is that the existing TPTP query interface (RDB -> EMF) will be reworked.
  • The queries are tightly coupled to the requirements of the UI implementation.
  • COSMOS would not rely on EMF in the views, primarily b/c these would be web based reports/UI.
  • The existing EMF models may continue to be used by TPTP for the existing views. However, this was determined to be a TPTP decision. See using existing TPTP views with new data store for an overview.
  • For Log data, there is a data store already that is used in the large log support for TPTP.

EMF & Metadata: One of the advantages of using EMF is that it provided a mechanism to derive meta information about the models that are being worked with. There will be multiple levels of metadata in the system that we will need to work. Ideally, a mechanism should be in place to provide a consistent strategy.

  • EMF may be appropriate for a RCP/Eclipse UI, but this must not bleed through to any other level.
  • Will SML (or CML) be a mechanism that we can leverage?


High Level Architecture: The second part of the day was focused on diagramming the high level architecture of COSMOS and where we would share (be dependent on) parts of TPTP. In later sessions, these diagrams were refined to focus on what could be delivered by the March milestone.

During this discussion, it was observed that there is an opportunity to formalize the control interface of the RAC. The formalization would be done using WSDM interfaces. This would provide a standards based mechanism of controlling the data collection mechanism. This approach had several advantages

  • COSMOS could be data collection agnostic and still control the collection of data
    • Just as the RAC would be enabled, other agents could as well, e.g. Nagios, or commercial vendors
    • The existing commands that flow across the command channel of the RAC would be explicitly expressed
  • A standard API would allow data collection to participate in higher order processes, e.g. BPEL based workflows
  • It may be possible to combine SML-IF or CML documents in the API as a way to specify information to collect (or the kind of information to collect). A rough initial pass at this is represented in the demo scenario where an SML-IF document is updated to indicate that log and statistical information is now available.

An interesting observation that emerged from this conversation is that using WSDM in this capacity would provide an opportunity to develop a new standard for the industry. This led to the discussion if COSMOS should be actively trying to lead the industry in defining new standards for systems management or simply use management standards where they exist.

  • It was agreed that the role of COSMOS should be to facilitate the development of new standards, and to provide reference implementations of existing standards where appropriate.

The other advantage to taking a standards based approach is that each part of the infrastructure could automatically discover and bind to the other parts. This would be similar to taking a SOA based approach where SCA could be used to “wire” together a systems management infrastructure.

This approach would also allow an optimization to happen that would short circuit any remote connections. The use of Tuscany was brough up, and this was generally viewed positively, although the full implications of adding a dependency on this project was unclear. Everyone agreed this should be explored in more detail.


Longer term, this would lead to decoupling the runtime monitoring from the development time instrumentation by allowing the application to discover the available monitoring infrastructure.

We also discussed rehosting the TPTP AC in process. This discussion, combined with the standardization discussion about apply/wrapping standards around the RAC, lead to the realization that this could transform what COSMOS delivers into a basic Java based (OSGi) agent framework. A question was raised if this was outside the initial intent of the scope proposed in the project creation and if so, did the companies participating want to pursue this.

This is an open item.

Tuesday Jan 9

  • More Data Modeling re: data collection, loaders, persistence, etc...
  • Look at the Hierarchy and Statistical models
    • Joe T. to look at the Test model
  • Attempt to identify small API
    • Query interface

Wednesday Jan 10

  • 8:00am - 10:00am Review/present work so far to TPTP team


Thursday Jan 11

  • 9:00am - 11:00am EST: Work on query APIs
  • 11:00am - 3:00pm EST
    • Using SML in Management Enablement
    • Interaction interfaces with validator
    • Discuss and agree first deliverables
      • Initial assumptions:
 March: SML Validator & samples (not just basic ones, but more complex ones that can form a 'bootstrap' for editor validation).
 Second release: SML GUI editor.

COSMOSEcliseCon2007Demo

Friday Jan 12

11:00 - 12pm EST Wrap up.

Initial Development Plan Jan 12 - March 1

  • Jan 12

Draft of Demo Script (Mark W.) Submit demo to Eclipse Con (Mark W.)

  • Jan 18

Each team must review the demo script and determine their work items.

    • Don E: Data Collection
    • Craig T: Reporting
    • Oliver C: Management Enablement
    • Steve J: Resource Modeling

February 14: Demo Script Final

March 1: Code Complete

TPTP Topics

  • RAC roadmap and plans for a managability interface

Back to the top