Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "COSMOSMonthlySummit-Apr2008"
m (→Agenda) |
Jim.gyng.com (Talk | contribs) (→Agenda) |
||
| Line 34: | Line 34: | ||
Thoughts from Jimmy Mohsin for COSMOS 1.1 and beyond… | 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) requirements; we also need to think about how we can phase it into Open Source, assuming this is something we even want to do… | |
| − | + | ||
| − | + | # Security design AND reference implementation(s) | |
| − | + | # Further support for CMDBf | |
| − | + | # 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) | |
| − | + | ||
| − | + | ||
Revision as of 13:58, 7 April 2008
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
- 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) requirements; we also need to think about how we can phase it into Open Source, assuming this is something we even want to do…
- Security design AND reference implementation(s)
- Further support for CMDBf
- 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)