SMI Tutorial > SMI-S 1.1.0 Functionality > SNIA Packages
 |
SNIA Packages |
 |
Profiles |
Subprofiles |
Packages
Health |
Physical Package |
Software |
Block Services
A SNIA Package can be referenced by SNIA Profile. Like a Profile, a Package defines a set of CIM classes. It also defines the associations that will be used to traverse between classes. In addition to defining the classes used, a Package also defines the properties and extrinsic methods to be used. In certain cases, the Package even specifies the values a property or method argument can have.
However, there exists a significant difference between a Subprofile and a Package. A Subprofile represents additional functionality that a vendor can optionally choose to implement as part of their Profile implementation. In contrast, when a Package is referenced by a Profile, all of the CIM elements in the Package are considered to be part of the Profile and hence, must be implemented.
A Package contains the same components as a Profile which are:
- The standards used
- The events that a Client can monitor
- The Subprofiles that can optionally be implemented
- Recipes for performing a particular management task using the Package
- The WBEM operations that the SMI Agent must support
- The CIM elements used by the Package
- Other Packages
SMI-S 1.1.0 defines the following four Packages:
- Health - allows a Client to retrieve information about the status of the device managed by the referencing Profile
- Physical Package - allows a Client to retrieve information about the physical characteristics of the device managed by the referencing Profile
- Software - allows a Client to retrieve information about the software or firmware installed on the device or element managed by the referencing Profile
- Block Services - allows a Client to manage storage pools and logical disks by the referencing storage Profile
|
