Difference between revisions of "COSMOS SDD Minutes 08APR08"

Latest revision as of 19:17, 15 April 2008

Logistics

• Date: 08APR08
• Time: 9AM EST
• Attendees: Chris Mildebrandt, Charlie Halloran, Mark McCraw, Merri Jensen, Josh Hester, Jason Losh, Julia McCarthy, Eric Rose, Jeff Hamm

Agenda

1. Review minutes from last week
2. Cover using SDD to install COSMOS possibilities
   • Create an SDD for installing COSMOS -- community members to be on the call to articulate COSMOS install requirements. How formal do we want requirements gathering to be?
   • Marry change analyzer code to SAS extraction code and UI
   • Create an SML profile of the COSMOS install
   • Status update on the above items
3. Deployment runtime use case review -- need these moved to COSMOS use case section
4. Follow-up on action items
   • Charlie/Chris/Eric, continue working w/ IBM legal on committing BTG code & Change Analyzer code, Charlie to send status.
   • Jason to commit SAS SDD Tooling code simultaneous with IBM SDD Tooling.
   • Mark W to contact Eclipse about adding SDD Tooling code (since contributions are over 200 lines of code).
   • Mark W to review Decision Matrix wiki page for implementation technology and for CL1 vs CL2 non-functional requirements.
   • Continue looking into additional projects that Michael mentioned, links are provided in the Minutes section from 19FEB08.
   • Mark W to determine package names for Change Analyzer code.
   • Jason to start moving use cases and "details" into COSMOS Use Cases and begin entering i11 enhancement requests.
   • Merri & Jason to get up with COSMOS SML experts to create SML for COSMOS.
   • Julia to work with Jeff and Mark M. to create CL1 SDD for COSMOS and work with Chris to run it through the Change Analyzer.
   • Mark M. and Jeff to continue working on code for COSMOS install.
   • Jason to schedule meeting for futher discussion of SDD for COSMOS.
   • Jason to determine alternate meeting time so as not to conflict with the RE meeting.

Minutes

1. Package names do need to be changed in the Change Analyzer code. Mark W. finally confirmed what those are, and Chris will find someone to update them.
2. Jason to contact Ruth about rescheduling the RE and/or the SDD call so that they no longer conflict.
3. Jeff to get SAS zip extractor code ready to push for next week, including appropriate package names.
4. P2 update:
   • There was a new push before Jeff went on vacation.
   • WindRiver and other companies are starting to poke around with it.
5. How to query for resources and register resources - remaining major code contribution needed to hook SDD Runtime together.
   • Use "query" instead of "discover".
   • We can't assume that a resource has been registered by the SDD, so we have to create a plugin of some sort that can do "code passthru"
   • We need to register resources that we are installing.
   • May be able to use CMDBf's APIs to register with federating CMDB, and with local MDR.
   • Julia has created UML diagrams that need a few tweaks and may be posted next week.
6. Review of meeting on April 4th, with COSMOS team regarding installer requirements for COSMOS. Jason has documented the minutes at COSMOS_Install_Requirements.
   • Question from Mark M.: Will the installer prompt for a third party requirement and then wait for user to say okay I've got it (if the runtime doesn't find that it was already available)? Specifically, what about the Tomcat requirement? Webapp won't work without it. Answer: It will probably just give them a log and they will have to start installation over after they get the requirements updated (at least that is what I think I heard - I was having phone problems, and very loud barking dogs in my ear ;-) )
   • Question from Mark M.: Will we be providing a GUI? Answer: Probably a very simplistic one, we don't want to go to far into this area so that we don't infringe on other companies value add.
   • Question from ???: There was another question and something that Jason was supposed to follow up on with Jimmy, and I didn't write it down... Sorry... If anyone knows what it was, please let me know, or better yet, just add it here!
   • COSMOS team has decided that they will use the Eclipse Update Manager to install their plugins, so we won't worry about those for now. This is an area where we may be able to blend P2 in nicely in the future since it is supposed to replace the Update Manager.

Action Items

1. Charlie/Chris/Eric, continue working w/ IBM legal on committing BTG code & Change Analyzer code, Charlie to send status.
2. Jason to commit SAS SDD Tooling code simultaneous with IBM SDD Tooling.
3. Mark W to contact Eclipse about adding SDD Tooling code (since contributions are over 200 lines of code).
4. Mark W to review Decision Matrix wiki page for implementation technology and for CL1 vs CL2 non-functional requirements.
5. Continue looking into additional projects that Michael mentioned, links are provided in the Minutes section from 19FEB08.
6. Jason to start moving use cases and "details" into COSMOS Use Cases and begin entering i11 enhancement requests.
7. Merri & Jason to get up with COSMOS SML experts to create SML for COSMOS.
8. Julia to work with Jeff and Mark M. to create CL1 SDD for COSMOS and work with Chris to run it through the Change Analyzer.
9. Mark M. and Jeff to continue working on code for zip extraction.
10. Jason to contact Ruth for alternate meeting time so as not to conflict with the RE meeting.
11. Chris to find someone to update package names for Change Analyzer before code is committed.