Revision: Configuration Management Wiki Home

New here? Sign up!

Sort of a ghost town here
Active specification development is now at Change and Configuration Management TC

Want to contribute?

Mailing list

Workgroup information

History View Links to this page Revision from: 2013 April 16 | 07:43 am

This is the revision from 2013 April 16 at 07:43 am View the current live version of the article.

Contents

New Members
Charter
Terminology
Milestones
Issues
Scenarios
Meetings
Specifications
Working Documents
Related Documents and Information
Mailing List

New Members

We welcome new members! Remember to sign the participation agreement forms, and please fill out your bio and optionally provide a photo - see the page Nick Crossley for a very short example.

Charter

See the Configuration Management Charter page.

Terminology

See the Configuration Management Terminology page, and the Configuration Management Resource Definitions page. This specification references the emerging work of W3C Linked Data Platform.

See also some legacy Baseline properties proposed by the Core workgroup.

Milestones

Date	Milestone	Status
2012-12-31	Terminology, use cases, and requirements defined	In progress
TBD	First draft specification written	In progress
TBD	Draft OSLC SCM migration strategy published	Not started
TBD	Specification in convergence	Not started
TBD	Finalization of Configuration Management 1.0	Not started
TBD	At least one implementation of Configuration Management 1.0 available	Not started

Issues

See Configuration Management Issues for a list of open issues.

Scenarios

See Configuration Management Scenarios for scenarios.

Meetings

See Configuration Management Meetings for details on meeting logistics, agendas, and minutes.

Specifications

Document	Version	Status
None yet

Working Documents

The first two documents are legacy proposals from the Core workgroup: one involves resource rewriting to create new resources that are specific to versions or snapshots of individual resources across multiple service providers, and the other creates snapshot states for a set of resources from a single service provider. Neither of these is necessarily the approach to be used by this workgroup, but they are referenced so we can see what ground has already been covered.