openwbem-smash-providers README

CONTENTS

   1.0 - What is openwbem-smash-providers

   2.0 - SMASH Overview
      2.1 - Who's Who
         2.1.1 - SMASH
         2.1.2 - SMWG
         2.1.3 - DMTF
      2.2  What is SMASH
      2.3  Purpose of openwbem-smash-providers
      2.4  Dependencies and Requirements
      2.5  Namespace requirements

   3.0 - Smash Profile Versions in this release
   4.0 - Known Issues

-------------------------------------------------------------------------------
1.0 What is openwbem-smash-providers

   openwbem-smash-providers is a set of providers that can be used by the Common
   Information Model Object Manager (CIMOM) for OpenWBEM (Web-Based Enterprise
   Management). These providers instrument the Systems Management Architecture
   for Server Hardware (SMASH) profiles as laid out by the Distributed Management 
   Task Force (DTMF). The providers contain a suite of specifications that deliver
   architectural semantics, along with industry standard protocols and profiles, to
   unify management of the data center.

   For more information on OpenWBEM and providers (generally), read the 
   OpenWBEM README or visit 
   http://www.openwbem.org.

   For more information on DMTF, SMWG, SMASH, visit:
   http://www.dmtf.org


-------------------------------------------------------------------------------
2.0 SMASH Overview

   2.1 Who's Who
      2.1.1 SMASH is the Server Management Architecture for System Hardware. 
            It is the working architecture of the SMWG.
      2.1.2 SMWG is the Server Management Working Group of the DMTF.
      2.1.3 DMTF is the Distributed Management Task Force. The DMTF is driving 
            the Comon Information Model (CIM) approach to server management.

   2.2  What is SMASH
      SMASH consists of multiple profiles of closely related parts of the system
      and how they relate to each other and to other profiles.
      SMASH profiles, as a set, are not yet at a 1.0 version. Therefore, the profiles
      implemented in openwbem-smash-providers will change as the profiles they
      implement change.

   2.3  Purpose of openwbem-smash-providers
      The purpose of this project (openwbem-smash-providers) is to implement 
      the SMASH profiles.

  
   2.4  Dependencies and Requirements
      openwbem-smash-providers depend on the following
      *  mofs, from the nim/model project
           omc-core
 	   omc-base-providers
   	   omc-smash-providers
      *  providers, from the nim/novell-provider-base (openwbem-base-providers.rpm)
	   openwbem-base-providers must be installed.

	  
   2.5  Namespace requirements
      SMASH requires a smash namespace (by default, 'smash') in which all
      smash-provided data is found. It also relies on the interop namespace
      (by default, 'Interop') in which Profile Versioning information is found.


-------------------------------------------------------------------------------
3.0 SMASH Profile Versions in this release
   Base Server Profile                  0.7.3
   Boot Control Profile                 0.8.2
   CLP Admin Domain Profile             0.9.1     (partial)
   CPU Profile                          0.8.0
   DHCP Client Profile                  0.8.0
   DNS Client Profile                   0.8.1
   Ethernet Port Profile                0.9.3
   Fan Profile                          0.8.1
   Firmware Inventory Profile           0.7.2
   IP Interface Profile                 0.8.4
   Physical Asset Profile               0.8.1
   Power Supply                         0.8.0
   Profile Registration Profile         0.9.3
   Record Log Profile                   0.9.2
   Sensor Profile                       0.9.1
   SSH Service Profile                  0.8.0
   System Memory Profile                0.7.2
   System Collectionns Profile          0.7.1     (partial)


-------------------------------------------------------------------------------
4.0 Known Issues
   4.1  General
      These profile are not yet 1.0 ratified, so the providers that implement
      these profiles are inherently imcomplete and non-compliant.
   4.2  Specific Known Issues
      4.2.1 DHCP Client Profile
            This will work with traditional network configuration.  It will not
            work with the new Network Manager included in SLES 10/SLED 10.

 
