Skip to main content

Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "COSMOS Architecture Meetings"

(Next Meeting)
('''Agenda''')
Line 8: Line 8:
  
 
=== '''Agenda''' ===
 
=== '''Agenda''' ===
On yesterday’s Data Collection call we wanted to start drilling down into the different sections of the componentRoughly speaking, there are three major sections, the control API, the input services, and the query services.
+
Joel has an example working of wrapping the GLA from TPTPHe is planning to have this code checked in by today's meeting. 
 +
* Confirm with Joel there were no problems getting code in, e.g. Java natures et.
 +
* Confirm setup instructions--would like to get team using this
 +
* Confirm build instructions to Hubert
 +
* Review broken down work items for team, e.g. RAC example
  
Today’s architecture meeting will be devoted to studying the control API that Joel is currently working on. 
 
  
* Data Collection API Control Layer Review
+
Joel will begin working on the query API this week.  On last week's call, we began discussing the difference
** We will review the WSDL document, as well as the “SCDL-like” mapping document. 
+
b/t a "strongly typed" interface, e.g. getTopologies vs. a "weakly typed" interface e.g. executeQuery(production.topology).
** We will define a plan to incorporate the TPTP RAC as well as additional agents to demonstrate the effectiveness of the API
+
* On today's call, we need to define this stack all the way through, from UI to the data layer.
** Review of current test cases exercising the API
+
** We indicated that for June, the only client to the control API would be the Managed Agent Explorer. A stretch goal should the creation of a Web 2.0 like “gadget” that understands and can interact with any WSDM resource—a Web 2.0 MAX per se.
+
** Creation and assignment of bugzilla features to support the above
+
  
* Chris was going to present his "Top 5 Query Services" that we can start defining and directing our efforts
+
Resource Modeling
** Need to reconcile with what we have today and the work in TPTP
+
* Now that GLA is incorporated, we can begin to create a description of this in SML and add it into the data center example
 +
** https://bugs.eclipse.org/bugs/show_bug.cgi?id=178590
  
  
Please note: The Data Collection documentation is checked into CVS
+
=== Evolved End-toEnd Scenario ===
**[[http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.cosmos/doc/org.eclipse.cosmos.doc.architecture/dataCollectionServices.html?root=Technology_Project&view=co| Data Collection Doc]]
+
Our end to end would look like:
 +
* Browse are resource topology using tree widget
 +
** We may realize that an GLA is available in the environment but not turned on. No references b/t resources in the SML-IF
 +
* Using the control layer we should be able to turn on data collection. This starts collecting data via the GLA
 +
** The SML-IF document is updated (with the reference between the resource producing the logs and the GLA for now, by hand, but a stretch goal is to do this automatically)
 +
** Metadata exchange should be enabled for both SML-IF and standard WSDL
 +
* Well known WSDM instance registry updated with relationships
 +
* Refresh the resource topology
 +
* The resource and its log should be represented
 +
** Run the log report
 +
 
 +
 
 +
Super Stretch Goal
 +
 
 +
* Activate a new resource
 +
** Capture the WSDM advertisement
 +
* Use the WSDM advertisement to activate the GLA for the new resource
  
 
== Minutes from past meetings ==
 
== Minutes from past meetings ==

Revision as of 12:37, 21 March 2007

Back to COSMOS Home

Next Meeting

The next architecutre meeting will be March 21, 2007 2:30pm EDT.

Call in number 888 241 8547 pc 999451


Agenda

Joel has an example working of wrapping the GLA from TPTP. He is planning to have this code checked in by today's meeting.

  • Confirm with Joel there were no problems getting code in, e.g. Java natures et.
  • Confirm setup instructions--would like to get team using this
  • Confirm build instructions to Hubert
  • Review broken down work items for team, e.g. RAC example


Joel will begin working on the query API this week. On last week's call, we began discussing the difference b/t a "strongly typed" interface, e.g. getTopologies vs. a "weakly typed" interface e.g. executeQuery(production.topology).

  • On today's call, we need to define this stack all the way through, from UI to the data layer.


Resource Modeling


Evolved End-toEnd Scenario

Our end to end would look like:

  • Browse are resource topology using tree widget
    • We may realize that an GLA is available in the environment but not turned on. No references b/t resources in the SML-IF
  • Using the control layer we should be able to turn on data collection. This starts collecting data via the GLA
    • The SML-IF document is updated (with the reference between the resource producing the logs and the GLA for now, by hand, but a stretch goal is to do this automatically)
    • Metadata exchange should be enabled for both SML-IF and standard WSDL
  • Well known WSDM instance registry updated with relationships
  • Refresh the resource topology
  • The resource and its log should be represented
    • Run the log report


Super Stretch Goal

  • Activate a new resource
    • Capture the WSDM advertisement
  • Use the WSDM advertisement to activate the GLA for the new resource

Minutes from past meetings

Cosmos Architecture Meeting 14-Mar-07

Cosmos Architecture Meeting 28-Feb-07

Cosmos Architecture Meeting 21-Feb-07

Cosmos Architecture Meeting 14-Feb-07

Cosmos Architecture Meeting 07-Feb-07

Cosmos Architecture Meeting 31-Jan-07

Cosmos Architecture Meeting 24-Jan-07

Cosmos Architecture Meeting 17-Jan-07

Back to the top