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.
COSMOSF2F-08-Nov-07
Logistics
- Anyone who wants to have a scheduled conference call for a particular time slot, please add a note in that portion of the agenda. We will use the same number as the weekly Data Collection call.
- Toll-free Dial-in number: +1 (866) 213.1962
- Primary International Dial-in: +1.609.454.9912
- Passcode: 2025533#
- If you need to contact the group at a time when the confrence call is not active, call the main Compuware number (313) 227-7300 and ask for conference room 14W-4216.
- Location
- Compuware Corp
- One Campus Martius
- Detroit, MI, USA 48226: Nov 7-9
- Main phone 313 227-7300
- Our meeting room 14W-4216 313.227.7300 x79742
- Visitor passes are issued at the Concierge desk near the main entrance.
- Security will direct you to the Visitor Center on the eighth floor of the Woodward wing.
- Parking is available in the Compuware ramp. Take a ticket at the public entrance on Farmer street. Tickets can be validated at the Visitor Center for free exit from the parking ramp.
-
- Nearest hotel - easy walking distance - two blocks from Compuware
- Hilton Garden Inn Detroit Downtown
- 351 Gratiot Avenue, Detroit, Michigan, USA 48226
- Tel: +1-313-967-0900 Fax: +1-313-967-0908
- [map]
- Nearest hotel - easy walking distance - two blocks from Compuware
-
- Nearest airport - DTW (see map for driving directions to Compuware) and locations of HQ and parking ramp.[link]
- Proposed schedule 10AM-6PM daily.
- Non-critical items will be scheduled after 3PM Friday for the convenience of those who must leave early.
- Anyone who wants to have a scheduled conference call for a particular time slot, please add a note in that portion of the agenda. We will use the same number as the weekly Data Collection call.
- If you need to contact the group, call the main Compuware number (313) 227-7300 and ask for conference room 14W-4216.
Agenda
1. Collection of data--northbound interfaces - Wednesday 8:00 AM
- What resources should we target?
- How to monitor COSMOS itself?
2. Ensure that all the designs for i7 / i8 / i9 are in order - Wednesday 10:00 AM
- Ensure that we agree on the delineation between the MDRs and the Broker; and the exact role of the Management Domain.
Note: indicates the item has been discussed
- COSMOS_Design_205658 Extend the initial design and implementation of COSMOS DC Management Domain
- COSMOS_Design_204921 Extend the initial design and implementation of COSMOS DC Broker
- https://bugs.eclipse.org/bugs/show_bug.cgi?id=188390 Support for Nagios agents in data collection
- https://bugs.eclipse.org/bugs/show_bug.cgi?id=208100 Create a transformation engine that is able to process CMDBf queries based on a reconciliation taxonomy scheme
- COSMOS_Design_208274 Create an MDR toolkit that will allow adopters to easily register and use a data provider inside COSMOS framework
- https://bugs.eclipse.org/bugs/show_bug.cgi?id=205826 Update DataCenter model based on latest SML changes
- https://bugs.eclipse.org/bugs/show_bug.cgi?id=205956 SML validator should provide API for accessing the model
- https://bugs.eclipse.org/bugs/show_bug.cgi?id=205960 SML Data Center repository should be dynamically populated
- https://bugs.eclipse.org/bugs/show_bug.cgi?id=205825 Update SML validator implementation based on changes to the SML latest draft
- https://bugs.eclipse.org/bugs/show_bug.cgi?id=208584 Update CMDBf query and registration service implementations to 1.0 spec level
- https://bugs.eclipse.org/bugs/show_bug.cgi?id=208976 Data Manager and MDR framework
- https://bugs.eclipse.org/bugs/show_bug.cgi?id=208592 Error Handling - improve programming model
- https://bugs.eclipse.org/bugs/show_bug.cgi?id=208593 Internationalization Support - programming model
- https://bugs.eclipse.org/bugs/show_bug.cgi?id=208595 Register Queries with Visualization - programming model
- https://bugs.eclipse.org/bugs/show_bug.cgi?id=208603 Register Visualzations with a Query Response - programming model
- https://bugs.eclipse.org/bugs/show_bug.cgi?id=208604 Data Visualization Test Harness
3. M2 / Leveraging CMDBf Use Case - Wednesday 1:00 PM
- Reiterate / refine our goals.
- How will we push it forward to enable adoption of the CMDBf Use Case?
- Talk about a potential target domain.
- What is the UI approach for M2? Where / how will the COSMOS GUI framework be used?
- Where do we go after this use case?
- Define COSMOS "MDR Toolkit", what tooling we need, etc... see the programming model
- Coordination of efforts with CMDBf.org group
- Schedule call in with Mark J. and Marv W. 3:30pm Eastern 11/8/2007
4. COSMOS Programming Model Thursday 8:00 AM
- discussion page
- What are the use cases for extending/adopting the COSMOS code
- Adoption patterns
- What do we need in terms of "SDKs". This will impact how we structure our deliverables
- Provisional API Guidelines (we are currently not following these guidelines)
- Joel's annotation roadmap page here
5. Divvy up the work for i8 / i9 (M2) Thursday 12:15 PM
- Try to assign areas of focus for each company across the COSMOS community for the i8 / i9 ERs
- Management Domain design & implementation: CA
- Broker design & implementation: CA
- Logging design & implementation: CA
- SQA methodology / manual / automated testing: CA + ?
- MDR design & implementation: IBM + Compuware + ?
- GUI design & implementation: IBM + Compuware + ?
- Cross-company demo enablement: IBM + Compuware + CA ?
- Review the M2 release plan and establish that it is realistic
- Define plan / timeframe for synchronizing all COSMOS DC codebases
3-2. CMDBf - part 2 Thursday 3:30 PM
- Schedule call in with Mark J. and Marv W.
6. Facilitation of Adoption Thursday 4:00 PM
- How do we publish our packaging for the CMDBf Use Case?
- Identify and publish the tech stack for the CMDBf Use Case.
- Identify the range of adopters for the Leveraging CMDBf use case.
- Documentation
- Useability
- Support
- What can we do to ensure that adopters of ALL types derive immediate value?
7. Security considerations for the COSMOS DC M2 Friday 8:00 AM
- Define the scope of Security
- What is our Security model?
- How will we publish this capability & area of concern to the outside world?
8. Fire drill Friday 10:00 AM
4-2. Programming model part 2 Friday 10:30 AM
- Close on what to do with the sandbox
- Provisional APIs
9. Breakout sessions Friday 11:00 AM
10. SQA considerations for the COSMOS DC M2 Friday 12:00 Noon
- Define the SQA strategy for M2
- Talk about SQA resourcing
- Talk about the exact function of the SQA resources for the COSMOS DC
- Define QA metrics & release closure criteria for i8 / i9 (i.e. M2)
11. Review Plan and Action items 1:00 PM
12. EOM 2:30 PM