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.
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
- Documentation ERs
- Review the status of the COSMOS User and Development guides
- Are there any other i10 ERs that will impact the content for these guides?
- Post-1.0 Plans
Thoughts from Jimmy Mohsin for COSMOS 1.1 and beyond…
- Semantic or Information model AND/OR Reconciliation taxonomies
- What is the scope of an Open Source Information Model? How does it jive with the Reconciliation Taxonomies we have talked about earlier?
- What role will SML play in this regard? Can it be THE building block for this effort?
- What will the role of CMDBf be in this space? Can we say that CMDBf is THE information model for configuration data?
- 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…
- Coverage for types of data in COSMOS
- Currently, we cover Configuration Items via support for CMDBf
- What do we do in regards to other types of data?
- How do we evolve / enhance our support for CMDBf
- Security design AND reference implementation(s)
- i18n
- Well defined COSMOS install & upgrade approach / paradigm / tooling
- I state this since I doubt if we will be able complete this by June end for COSMOS 1.0
- Management capabilities for core COSMOS components (i.e. for the Domain and the Broker)