Jump to: navigation, search

Difference between revisions of "Cosmos Release Plan"

(Release Milestones)
Line 1: Line 1:
 
[[COSMOS|COSMOS Wiki]] >  [[COSMOS_Work_Items|COSMOS Work Items]]  
 
[[COSMOS|COSMOS Wiki]] >  [[COSMOS_Work_Items|COSMOS Work Items]]  
  
= COSMOS 1.0 Release Plan - Draft - Updated 5/14/2008 =
+
= COSMOS 1.1 Release Plan =
  
 
== Overview ==
 
== Overview ==
Line 7: Line 7:
  
  
This document lays out the feature and API set for the COSMOS Tech Preview releases.                                       
+
This document lays out the feature and API set for the COSMOS releases.                                       
 
* [[#Release Deliverables|Release Deliverables]]  
 
* [[#Release Deliverables|Release Deliverables]]  
 
* [[#Release Milestones|Release Milestones]]  
 
* [[#Release Milestones|Release Milestones]]  
Line 34: Line 34:
 
== Release Milestones ==
 
== Release Milestones ==
  
This COSMOS 1.0 is targeted for general availability on 14-November-2008.  All deliverables will be available for download as soon as the release has been tested and validated in the target configurations.  There is an allocation of resource to defect removal in all iterations. The first Iterations 1-10 will contain the bulk of the enhancement work, while Iterations 11-13 will mainly be used to stabilize and shut down the release.  
+
This COSMOS 1.1 is targeted for general availability on 26-June-2009.  All deliverables will be available for download as soon as the release has been tested and validated in the target configurations.  There is an allocation of resource to defect removal in all iterations. The first Iterations 1-2 will contain the bulk of the enhancement work, with Iteration 3 stabilizing the milestone driver, with Iteration 4 finishing the enhancement work, and Iteration 5 will mainly be used to stabilize and shut down the release.  
  
  
Line 174: Line 174:
 
|Fri 08/17/2007
 
|Fri 08/17/2007
 
|Validation Testing & Documentation
 
|Validation Testing & Documentation
|
 
|-
 
|'''Iteration 6'''
 
|'''6 weeks'''
 
|'''Mon 08/13/2007'''
 
|'''Fri 09/28/2007'''
 
|'''Mon 08/20/2007'''
 
|'''Fri 10/02/2007'''
 
|
 
|Extended test pass by 1 week
 
|-
 
|  i6 Development
 
|5 weeks
 
|Mon 08/13/2007
 
|Fri 09/14/2007
 
|Mon 08/20/2007
 
|Fri 09/14/2007
 
|Development & Bug Fixes
 
|
 
|- 
 
|  i6 Testing
 
|1 week
 
|Mon 09/17/2007
 
|Fri 09/28/2007
 
|Mon 09/17/2007
 
|Fri 10/02/2007
 
|Validation Testing & Documentation
 
|Extended test pass by 1 week
 
|-
 
|'''Iteration 7'''
 
|'''7.5 weeks'''
 
|'''Mon 10/03/2007'''
 
|'''Fri 11/23/2007'''
 
|'''Mon 10/03/2007'''
 
|'''Mon 11/26/2007'''
 
|
 
|
 
|-
 
|  i7 Development
 
|5.5 weeks
 
|Mon 10/03/2007
 
|Fri 11/09/2007
 
|Mon 10/03/2007
 
|Fri 11/09/2007
 
|Development & Bug Fixes
 
|
 
|-
 
|**High-level designs for i8 Complete**
 
|1 day
 
|Mon 11/12/2007
 
|Mon 11/12/2007
 
|Mon 11/12/2007
 
|Mon 11/12/2007
 
|High-level designs and sizings
 
|
 
|- 
 
|  i7 Testing
 
|2 weeks
 
|Mon 11/12/2007
 
|Fri 11/23/2007
 
|Mon 11/12/2007
 
|Mon 11/26/2007
 
|Validation Testing & Documentation
 
|
 
|-
 
|'''Iteration 8'''
 
|'''9 weeks'''
 
|'''Mon 11/26/2007'''
 
|'''Fri 01/25/2008'''
 
|'''Mon 11/26/2007'''
 
|'''Fri 01/25/2008'''
 
|
 
|
 
|-
 
|  i8 Development
 
|6 weeks
 
|Mon 11/26/2007
 
|Fri 01/11/2008
 
|Mon 11/26/2007
 
|Fri 01/11/2008
 
|Development & Bug Fixes
 
|
 
|-
 
|**High-level designs for i9 Complete**
 
|1 day
 
|Fri 01/18/2008
 
|Fri 01/18/2008
 
|
 
|
 
|High-level designs and sizings
 
|
 
|- 
 
|  i8 Testing
 
|2 weeks
 
|Mon 01/14/2008
 
|Fri 01/25/2008
 
|Mon 01/14/2008
 
|Fri 01/25/2008
 
|Validation Testing & Documentation
 
|
 
|-
 
|'''Iteration 9'''
 
|'''6 weeks'''
 
|'''Mon 01/28/2008'''
 
|'''Fri 03/07/2008'''
 
|'''Mon 01/28/2008'''
 
|'''Fri 03/07/2008'''
 
|
 
|
 
|-
 
|  i9 Development
 
|4 weeks
 
|Mon 01/28/2008
 
|Wed 02/20/2008
 
|Mon 01/28/2008
 
|Wed 02/20/2008
 
|Development & Bug Fixes
 
|
 
|-
 
|**High-level designs for i10 Complete**
 
|1 day
 
|Fri 02/22/2008
 
|Fri 02/22/2008
 
|
 
|
 
|High-level designs and sizings
 
|
 
|- 
 
|  i9 Testing
 
|2 weeks
 
|Mon 02/25/2008
 
|Fri 03/07/2008
 
|Mon 02/25/2008
 
|Fri 03/07/2008
 
|Validation Testing & Documentation
 
|
 
|-
 
!'''**Milestone 2**'''
 
|'''1 day'''
 
|'''Fri 03/07/2008'''
 
|'''Fri 03/07/2008'''
 
|'''Fri 03/07/2008'''
 
|'''Fri 03/07/2008'''
 
|Available for POCs
 
|
 
|-
 
|'''Iteration 10'''
 
|'''8 weeks'''
 
|'''Mon 03/10/2008'''
 
|'''Fri 05/02/2008'''
 
|'''Mon 03/10/2008'''
 
|'''Thu 05/01/2008'''
 
|
 
|
 
|-
 
|  i10 Development
 
|6 weeks
 
|Mon 03/10/2008
 
|Wed 04/16/2008
 
|Mon 03/10/2008
 
|Mon 04/21/2008
 
|Development & Bug Fixes
 
|
 
|-
 
|**High-level designs for i11 Complete**
 
|1 day
 
|Fri 04/18/2008
 
|Fri 04/18/2008
 
|
 
|
 
|High-level designs and sizings
 
|
 
|- 
 
|  i10 Testing
 
|2 weeks
 
|Mon 04/21/2008
 
|Fri 05/02/2008
 
|Mon 04/21/2008
 
|Thu 05/01/2008
 
|Validation Testing & Documentation
 
|
 
|-
 
|'''Iteration 11'''
 
|'''8 weeks'''
 
|'''Mon 05/05/2008'''
 
|'''Fri 06/27/2008'''
 
|'''Mon 05/05/2008'''
 
|
 
|
 
|
 
|-
 
|  i11 Development
 
|6 weeks
 
|Mon 05/05/2008
 
|Wed 06/09/2008
 
|Mon 05/05/2008
 
|
 
|Development & Bug Fixes
 
|
 
|- 
 
|  i11 Testing
 
|2 weeks
 
|Mon 06/16/2008
 
|Fri 06/27/2008
 
|
 
|
 
|Validation Testing & Documentation
 
|
 
|-
 
!'''**Milestone 3**'''
 
|'''1 day'''
 
|'''Fri 06/27/2008'''
 
|'''Fri 06/27/2008'''
 
|
 
|
 
|Available for PoCs
 
|
 
|-
 
|'''Iteration 12'''
 
|'''6 weeks'''
 
|'''Mon 06/30/2008'''
 
|'''Fri 08/08/2008'''
 
|
 
|
 
|
 
|
 
|-
 
|  i12 Development
 
|4 weeks
 
|Mon 06/30/2008
 
|Wed 07/23/2008
 
|
 
|
 
|Development & Bug Fixes
 
|
 
|-
 
|**High-level designs for i13 Complete**
 
|1 day
 
|Fri 07/25/2008
 
|Fri 07/25/2008
 
|
 
|
 
|High-level designs and sizings
 
|
 
|- 
 
|  i12 Testing
 
|2 weeks
 
|Mon 07/28/2008
 
|Fri 08/08/2008
 
|
 
|
 
|Validation Testing & Documentation
 
|
 
|-
 
|'''Iteration 13'''
 
|'''6 weeks'''
 
|'''Mon 08/11/2008'''
 
|'''Fri 09/19/2008'''
 
|
 
|
 
|
 
|
 
|-
 
|  i13 Development
 
|4 weeks
 
|Mon 08/11/2008
 
|Wed 09/03/2008
 
|
 
|
 
|Development & Bug Fixes
 
|
 
|- 
 
|  i13 Testing
 
|2 weeks
 
|Mon 09/08/2008
 
|Fri 09/19/2008
 
|
 
|
 
|Validation Testing & Documentation
 
|
 
|-
 
|'''Iteration 14'''
 
|'''8 weeks'''
 
|'''Mon 09/22/2008'''
 
|'''Fri 11/14/2008'''
 
|
 
|
 
|
 
 
|
 
|
 
|-
 
|-
Line 482: Line 194:
 
|
 
|
 
|-
 
|-
|'''COSMOS 1.0 Availability'''
+
|'''COSMOS 1.1 Availability'''
 
|'''1 day'''
 
|'''1 day'''
|'''Fri 11/14/2008'''
+
|'''Fri 06/26/2000'''
|'''Fri 11/14/2008'''
+
|'''Fri 06/26/2009'''
 
|
 
|
 
|
 
|
Line 520: Line 232:
 
Plan items targeted for this release represent the addition of new features or areas where existing features will be significantly reworked or enhanced.  Plan items are allocated to the projects indicated above.
 
Plan items targeted for this release represent the addition of new features or areas where existing features will be significantly reworked or enhanced.  Plan items are allocated to the projects indicated above.
  
=== Milestone 1 Objectives (i1 - i4) ===
+
=== Milestone 1 Objectives (i1 - i3) ===
 
+
* Provide tools that support systems management data conforming to the Service Modeling Language (SML) and SML-Interchange Format (SML-IF) standards, including SML and SML-IF document validation, SML-IF editing, import of SML-IF documents and export to SML-IF documents
+
* Create example data center described in SML format
+
* Provide standard APIs for accessing COSMOS data from heterogeneous clients
+
* Create data collectors that gather data from Common Base Event (CBE) logs, JMX, and WSDM Event Format (WEF) sources
+
* Provide preset reports to visualize event and statistical data
+
* Create a data store to persist statistical information based on the standard SDMX specification
+
* Create a relational data store for the persistence of event information and statistical information
+
* Create a web-based viewer composed of Web 2.0 gadgets to thoroughly examine data from SML-IF documents
+
* Provide extension points to create complementary visualizations in the form of Web 2.0 gadgets and BIRT reports
+
 
+
  
 +
[[COSMOS_1.1_Iteration1_Features| v1.1 Iteration 1 Features]]
 +
[[COSMOS_1.1_Iteration2_Features| v1.1 Iteration 2 Features]]
 +
[[COSMOS_1.1_Iteration3_Features| v1.1 Iteration 3 Features]]
 
[[COSMOS_Milestone1_Plan_Items|COSMOS Milestone 1 Plan Items]]
 
[[COSMOS_Milestone1_Plan_Items|COSMOS Milestone 1 Plan Items]]
  
=== Milestone 2 Objectives (i5 - i9) ===
+
=== GA Objectives (i4 - i5) ===
 
+
* Provide framework for implementing CMDBf query and registration services
+
* Create Eclipse-integrated toolkit for creating data managers and management data repositories (MDRs)
+
* Provide ability to register an MDR with the COSMOS framework
+
* Provide ability to register and deregister an MDR with a federating CMDB, using the COSMOS UI
+
* Provide ability to query an MDR from the COSMOS UI, using query builder driven by CMDBf metadata
+
* Create example MDRs, including a simplistic one and one based on the example data center
+
* Provide ability to visualize a CMDBf query response
+
* Provide support for deploying to J2EE environments (for example, Tomcat)
+
* Provide full test suite showing implementation examples
+
  
  
Line 566: Line 260:
 
* Finalize API
 
* Finalize API
 
* Enhance quality and documentation
 
* Enhance quality and documentation
 
 
 
 
=== Proposal for Themes - i11 - i13 ===
 
<font color="blue">
 
From Ruth Lee:
 
 
My proposal for the COSMOS iterations between now and November is (Themes in italics):
 
 
i11: ''Quality and Extensibility'': identify API, document API, drive more adoption, ideally get more activity on the mailing list and newsgroup.
 
Purpose: Increase adoption of COSMOS, stabilize COSMOS, and prove COSMOS as an extensible framework.
 
 
i12: ''Accessibility, internationalization and localization, upgrade path''
 
Purpose: Provide support for the pervasive themes in Eclipse. (Suspect this is needed to qualify releasing a 1.0.)
 
 
i13: ''Quality'': Reduce defect backlog, finish any items needed to release a 1.0
 
Purpose: Wind-down, clean up any remaining items that we think are needed to quality to release 1.0 in November.
 
 
'''Delineation between M3 and 1.0:'''
 
M3 is English-only, non-accessible. 1.0 will be enabled for translation (although nothing will be translated), it will be globalized, accessible, and the upgrade path plan will be in place.
 
</font>
 

Revision as of 08:13, 3 December 2008

COSMOS Wiki > COSMOS Work Items

COSMOS 1.1 Release Plan

Overview

Please send comments about this plan to the cosmos-mgmt@eclipse.org project management mailing list.


This document lays out the feature and API set for the COSMOS releases.

This plan describes the deliverables, milestones, and plan items for the COSMOS project. Each plan item covers a feature or API that is to be added to COSMOS, or some aspect of COSMOS that is to be improved. Each plan item has its own entry in the COSMOS bugzilla database, with a title and a concise summary (usually a single paragraph) that explains the work item at a suitably high level so that everyone can readily understand the work item.


Fixing bugs, improving test coverage, documentation, examples, performance tuning, usability, etc. are considered routine ongoing maintenance activities and are not included in this plan unless they would also involve a significant change to the API or feature set, or involve a significant amount of work. The intent of the plan is to account for all interesting feature work.

Release Deliverables

The following release deliverables are provided:

  • Runtime
  • Tooling
  • Source
  • Examples
  • Component Tests
  • Data Collection Implementation
  • Data Visualization Implementation
  • Resource Modeling Implementation
  • Management Enablement Implementation
  • CMDBf Implementation

Release Milestones

This COSMOS 1.1 is targeted for general availability on 26-June-2009. All deliverables will be available for download as soon as the release has been tested and validated in the target configurations. There is an allocation of resource to defect removal in all iterations. The first Iterations 1-2 will contain the bulk of the enhancement work, with Iteration 3 stabilizing the milestone driver, with Iteration 4 finishing the enhancement work, and Iteration 5 will mainly be used to stabilize and shut down the release.


Release Milestones

Milestone Duration Planned Start Date Planned End Date Actual Start Date Actual End Date Description Comments
Iteration 1 8 weeks Tues 01/02/2007 Fri 02/23/2007 Tues 01/02/2007 Fri 02/23/2007 Demo development
Iteration 2 6 weeks Mon 02/26/2007 Fri 04/06/2007 Mon 02/26/2007 Fri 04/06/2007
i2 Development 5 weeks Mon 02/26/2007 Fri 03/30/2007 Mon 02/26/2007 Fri 03/30/2007 Development & Bug Fixes
i2 Testing 1 week Mon 04/02/2007 Fri 04/06/2007 Mon 04/02/2007 Fri 04/06/2007 Validation Testing
Iteration 3 6 weeks Mon 04/09/2007 Fri 05/18/2007 Mon 04/09/2007 Fri 05/18/2007
i3 Development 5 weeks Mon 04/09/2007 Fri 05/11/2007 Mon 04/09/2007 Fri 05/11/2007 Development & Bug Fixes
i3 Testing 1 week Mon 05/14/2007 Fri 05/18/2007 Mon 05/14/2007 Fri 05/18/2007 Validation Testing
Iteration 4 6 weeks Mon 05/21/2007 Fri 06/29/2007 Mon 05/21/2007 Fri 06/29/2007 Shut down and Testing
i4 Development 4 weeks Mon 05/21/2007 Fri 06/15/2007 Mon 05/21/2007 Fri 06/15/2007 Bug Fixes
i4 Testing 2 weeks Mon 06/18/2007 Fri 06/29/2007 Mon 06/18/2007 Fri 06/29/2007 Validation Testing
**Milestone 1** 1 day Fri 06/29/2007 Fri 06/29/2007 Fri 06/29/2007 Fri 06/29/2007 Available for POCs
Iteration 5 6 weeks Mon 07/02/2007 Fri 08/10/2007 Mon 07/02/2007 Fri 08/17/2007
i5 Development 5 weeks Mon 07/02/2007 Fri 08/03/2007 Mon 07/02/2007 Fri 08/10/2007 Development & Bug Fixes
i5 Testing 1 week Mon 08/06/2007 Fri 08/10/2007 Mon 08/13/2007 Fri 08/17/2007 Validation Testing & Documentation
i14 Development 5 weeks Mon 09/22/2008 Wed 10/22/2008 Development & Bug Fixes
i14 Testing 3 weeks Mon 10/27/2008 Fri 11/14/2008 Final Validation Testing, Documentation & Shutdown
COSMOS 1.1 Availability 1 day Fri 06/26/2000 Fri 06/26/2009 GA Release

Release Themes

The COSMOS project adopted the following themes which represent the key focus areas for COSMOS enhancements in the year ahead.

  • Provide an open platform that is standards-based for extensibility and openness
  • Provide exemplary tools for monitoring and management of popular open distributed platforms
  • Establish base framework:
    • Data collection normalization and persistence framework
    • CMDB Federation (CMDBf) support framework
    • Validation/Editing/Viewing framework based on Service Modeling Language (SML)
    • Deployment framework for management enablement using Solution Deployment Descriptor (SDD)

Project Designs

<NEEDS TO BE UPDATED>

The COSMOS project is comprised of four projects, managed in a coordinated fashion, across which the plan items are allocated. COSMOS projects include:

  • Data Collection Project - The COSMOS Data Collection framework aims to provide value by building a standard based integration framework that can incrementally replace the existing ad hoc integrations between agent infrastructures and the management applications that utilize them. The initial focus of the data collection component is the delivery of a framework that provides a well-defined set of service interface types that facilitate the discovery and control of monitoring agents as well as related data services such as collection, transformation, filtering, persistence, and query. These services may be discovered, explored, and controlled through Web Services Distributed Management (WSDM) standard interfaces. They will describe themselves by exposing Service Modeling Language Interchange Format (SML-IF) models using WS-metadata exchange.
  • Data Visualization Project (Design Document)- The COSMOS Data Visualization framework aims to provide value by building a standards based integration infrastructure that provides access to two dimensions of the COSMOS management architecture, COSMOS Data Collection and COSMOS Resource Modeling. COSMOS Data Visualization provides a well-defined set of service interface types that facilitate the exploration of the COSMOS Resource Modeling's repository of models and the retrieval of the COSMOS Data Collection's repository of state, event, and performance information. The model repository is semantically linked to the information in the monitor data repository. This relationship, which is managed in Service Modeling Language (SML) through the Resource Modeling component, is used to connect the exploration of the model with data that has been collected.
  • Resource Modeling Project - The COSMOS Resource Modeling sub-project aims to provide support for building a common model to represent the information being shared in a system management scenario. The project is proposing to use Service Modeling Language (SML) as the XML schema language to define this common model. The SML-IF interchange format will be used to share model components between the tools involved in a system management activity.
  • Management Enablement - To be implemented in a future release

Designs for these projects will be checked in to the COSMOS bugzilla database so that developers can reference them as they create designs for specific plan items.

Features

Plan items targeted for this release represent the addition of new features or areas where existing features will be significantly reworked or enhanced. Plan items are allocated to the projects indicated above.

Milestone 1 Objectives (i1 - i3)

v1.1 Iteration 1 Features v1.1 Iteration 2 Features v1.1 Iteration 3 Features COSMOS Milestone 1 Plan Items

GA Objectives (i4 - i5)

COSMOS Milestone 2 Use Cases

Milestone 3 Objectives (i10 - i11)

  • Update SML Validator to align with latest SML specification
  • Enhance CMDB Federation Toolkit
  • Provide support for non-COSMOS MDRs and clients using vanilla web services
  • Provide overall quality and stabilization improvements and reduce defect backlog
  • Establish clear set of public APIs & complete externalization of strings


COSMOS Milestone 3 Use Cases

Milestone 4/COSMOS 1.0 GA Objectives (i12-i14)

  • Provide SDD Tooling and Runtime for management enablement
  • Finalize API
  • Enhance quality and documentation