Configuration Management

DRAFT – This is not yet an official OSLC workgroup - To be discussed with workgroup and Steering Committee

Charter

See the Configuration Management Charter page.

Terminology

Note: this terminology is provisional: the workgroup is tasked with defining the actual terminology.

• Resource: in this context, we refer to an information resource - data that resides on a computer, not an actual physical entity.
• Configuration: a resource that identifies a set of revisions, versions, and/or states of some other resources (the workgroup is to determine if configuration can contain other configurations).
• Configuration management: the practices of managing configurations, their contents, their lifecycles - in particular, identifying and controlling changes to configurations.
• Baseline: an immutable configuration, that is, a snapshot in time of the state of a set of resources, including the links from those resources.

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

Milestones

Scenarios

See ConfigMgtScenarios for scenarios.

Meetings

See ConfigMgtMeetings for details on meeting logistics, agendas, and minutes.

Specifications

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.

Participants

NickCrossley (IBM - lead)
GeoffreyClemm (IBM)
PeterHack (IBM)
SamitMehta (IBM)
JohnCamelon (IBM)
JimConallen (IBM)
NiklasLarsson (Tieto)
MikeLoeffler (GM)
SandeepKohli (IBM)

Mailing List

TBD - currently using OSLC-SCM