##(see the SpecSpec for an explanation)

 * '''Launchpad Entry''': UbuntuSpec:server-maverick-wbemcim-providers
 * '''Created''':
 * '''Contributors''': GuillaumeBottex
 * '''Packages affected''':

== Summary ==

## This should provide an overview of the issue/functionality/change proposed here. Focus here on what will actually be DONE, summarising that so that other people don't have to read the whole spec. See also CategorySpec for examples.
Since Karmic, OpenDRIM providers are providing basic information through CIM/WBEM infrastructure.
This specs outlines which new OpenDRIM providers should be packaged and which part of the CIM schema and CIM profiles shoul be covered.

== Rationale ==

## This should cover the _why_: why is this change being proposed, what justifies it, where we see this justified.
OpenDRIM providers have been developed for any Linux distribution.
16 new providers are ready to be included into Maverick.
However, the upstream project team would like some feedback from the Ubuntu community in order to improve their project.
A discussion beteween the OpenDRIM team and the Ubuntu staff on which providers are needed for the next Ubuntu server release, should be held.

== Design ==

## You can have subsections that better describe specific parts of the issue.


== Discussion notes ==

=== Current status ===
 * SBLIM stack on the broker side
 * OpenDRIM on the providers side

=== Maverick plans ===
 * SBLIM stack
   * Necessary updates
     * sfcb: 1.3.4 -> 1.3.7 (1.3.8 available at the end of May)
     * sfcc: 2.2.0 -> 2.2.1
     * cim-schema: 2.22 -> 2.25experimental
 * OpenDRIM providers
   * Which ones for 10.10
   * Key Development schedule dates
   * Upload/sponsoring support

=== Future plans ===
 * sfcb to universe (schema license)
 * PPU Upload rights

== Providers ==

=== Since Karmic ===

 * Provider Common Library

 * Base Server
 * System Memory
 * Ethernet Port
 * Physical Asset
 * Record Log
 * IP Interface

=== To be added ===

 * BIOS
 * Boot
 * CPU
 * DHCP
 * DNS
 * OS
 * PCI
 * Power Management
 * Power Supply
 * Sensors
 * Simple Identity Management
 * Software Inventory
 * Software Update
 * Battery

=== WIP ===

 * SSH
 * Telnet
 * Fan

 * Role Based Authorization
 * Integrated Access Control Policy Management

=== Profiles left ===

 * Diagnostics Profile
 * CLP Service Profile
 * SMASH Collections Profile
 * SM CLP Admin Domain Profile
 * Modular Systems Profile
 * Service Processor Profile
 * Device Tray Profile
 * Pass-Through Module Profile
 * Shared Device Management Profile
 * Text Console Redirection Profile
 * Alarm Device Profile
 * Platform Watchdog Profile
 * Resource Allocation Profile
 * System Virtualization Profile <--
 * Allocation Capabilities Profile
 * Processor Resource Virtualization Profile <-
 * Memory Resource Virtualization Profile <-
 * Storage Resource Virtualization Profile <-
 * Base Metrics Profile
 * Indications Profile
 * Virtual System Profile
 * Base Desktop and Mobile Profile <--
 * Generic Device Resource Virtualization Profile
 * Opaque Management Data Profile
 * Indicator LED Profile
 * KVM Redirection Profile
 * USB Redirection Profile
 * Enabled Logical Element Profile
 * Power Utilization Management Profile <--
 * Media Redirection Profile
 * Wi-Fi Port Profile <--

== Implementation ==

## This section should describe a plan of action (the "how") to implement the changes discussed. Could include subsections like:

=== Server side coverage ===

 1. Update SFCB server to the lastest stable version
 2. Update CIM Schema to the lastest Experimental version (2.25.0)
 
=== OpenDRIM providers ===

 1. Update package of the OpenDRIM common library
 2. Update packages of the providers present in Karmic
  * Base Server
  * System Memory
  * Ethernet Port
  * Physical Asset
  * Record Log
  * IP Interface
 3. Upload the 16 new providers' packages
 4. Add the Work In Progress providers if available for the FeatureFreeze

== Test/Demo Plan ==

## It's important that we are able to test new features, and demonstrate them to users.  Use this section to describe a short plan that anybody can follow that demonstrates the feature is working.  This can then be used during testing, and to show off after release. Please add an entry to http://testcases.qa.ubuntu.com/Coverage/NewFeatures for tracking test coverage.

## This need not be added or completed until the specification is nearing beta.

== Unresolved issues ==

## This should highlight any issues that should be addressed in further specifications, and not problems with the specification itself; since any specification with problems cannot be approved.

== BoF agenda and discussion ==

## Use this section to take notes during the BoF; if you keep it in the approved spec, use it for summarising what was discussed and note any options that were rejected.

----
CategorySpec