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)
(Evolved End-toEnd Scenario)
Line 25: Line 25:
  
  
=== Evolved End-toEnd Scenario ===
+
''[[COSMOS_Evolved End-toEnd Scenario|Scenario for June]] ''
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 08:27, 4 April 2007

Back to COSMOS Home

Next Meeting

The next architecutre meeting will be April 4, 2007 2:30pm EDT.

Call in number 877 421 0033 pc: COSMOS (267667)


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


Scenario for June

Minutes from past meetings

Cosmos Architecture Meeting 28-Mar-07

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