COSMOSMonthlySummit-Apr2008

Logistics

Meeting Title:	COSMOS Community Monthly Summit
Date & Time:	Friday, April 11, 2008 8:30 am EST - 12:30 pm EST
Toll-free Dial-in number:	+1 (877) 421.0528
Primary International Dial-in:	770-615-1258
T/L Dial-in:	421-0528
Passcode:	881103#
e-Meeting:
Minutes	Meeting minutes are on the Talk Page

Agenda

• DC discussion (Don Ebright)
  • This was deferred from April 3 arch call due to the desire to have Mark's perspective in this discussion
  • Don would like to explore the role of Muse in COSMOS 1.0 and beyond

• SDD update (Jason Losh)
  • This was deferred from April 3 arch call because Jason was unable to attend due to a last minute conflict
  • Jason to talk about synergy between CMDBf, SDD, and SML

• i10 ready for early adopters (Jimmy Mohsin)
  • When will i10 be ready for early adopter?

• COSMOS 1.0
  • Will COSMOS be declared as 1.0 in June? What does that mean?
  • If we do:
    • Need to identify candidate APIs
    • Need a release review
    • Do unfinished components, such as annotation work, need to be moved to a holding area?
    • Lots of other details need to happen to get it done by then

• Post-"1.0" Plans

1. Semantic or Information model AND/OR Reconciliation taxonomies
   1. What is the scope of an Open Source Information Model? How does it jive with the Reconciliation Taxonomies we have talked about earlier?
   2. What role will SML play in this regard? Can it be THE building block for this effort?
   3. What will the role of CMDBf be in this space? Can we say that CMDBf is THE information model for configuration data?
   4. This is obviously a VERY difficult (yet high value) requirement; we also need to think about how we can phase it into Open Source, assuming this is something we even want to do…
2. Coverage for types of data in COSMOS
   1. Currently, we cover Configuration Items via support for CMDBf
   2. What do we do in regards to other types of data?
   3. How do we evolve / enhance our support for CMDBf
3. Security design AND reference implementation(s)
4. i18n
   1. Confirm that this is an item for COSMOS 1.1 and beyond
5. Well defined COSMOS install & upgrade approach / paradigm / tooling
   1. I state this since I doubt if we will be able complete this by June end for COSMOS 1.0
6. Management capabilities for core COSMOS components (i.e. for the Domain and the Broker)
7. Logging - we need to address this soon after 1.0 (ER 224079)
   1. Need project wide approach and strategy, esp. with SDD becoming more integrated
   2. Is log4j the way to go?