SMI Tutorial > SMI-S 1.1.0 Functionality > SNIA Subprofiles
 |
SNIA Subprofiles |
 |
Profiles |
Subprofiles |
Packages
Common |
Common Target Ports |
Common Initiator Ports
Server |
Fabric |
Switch |
Storage
A SNIA Subprofile can be referenced by a SNIA Profile to allow optional inclusion of additional capability. Like a Profile, a Subprofile defines the classes that a client will use to perform the additional management tasks provided by the Subprofile. The Subprofile also defines the associations that will be used to traverse between classes. In addition to identifying the classes used, a Subprofile also defines the properties and extrinsic methods of each class that must be supported. In certain cases, the Subprofile even specifies the values a property or method argument must have.
However, a significant difference exists between a Profile and a Subprofile. A Profile represents a base set of classes and capabilities that all supporting implementations must make available. In contrast, a Subprofile represents an optional set of classes and capabilities that a vendor may or may not choose to implement. As an example, for a disk array product, a vendor would implement all of the CIM elements defined in the Array Profile. If their array product can create snapshots and replicas, then the vendor may also choose to implement the CIM elements defined in the Copy Services Subprofile.
A Subprofile can contain the same components as a Profile. They are:
- The standards used
- The events that a Client can monitor
- The Packages that are incorporated into the Subprofile
- Recipes for performing a particular management task using the Subprofile
- The WBEM operations that the SMI Agent must support
- The CIM elements used by the Subprofile
- Other Subprofiles
As for a Profile, the Subprofile elements described above are explicitly defined in Extensible Markup Language (XML) files, one XML file for each Subprofile. For example, the encapsulation of the model requirements of the FDMI Subprofile is defined in FDMISubprofile.xml.
In SMI-S 1.1.0, the following four groups of Subprofiles have been defined:
- Common
- Common Initiator Port
- Common Target Port
- Profile-specific
A Common Subprofile is one that can apply to many different Profiles. For example, the Location Subprofile allows a client to determine the physical location of the element managed by the Profile. Such capability has wide applicability.
A Common Initiator Ports Subprofile is one that can apply to Profiles that manage the generic SCSI capabilities and transport-specific aspects of target storage systems such as disk arrays and tape libraries. In contrast, a Common Target Ports Subprofile is one that can apply to Profiles that manage the generic SCSI capabilities and transport-specific aspects for hosts and storage systems to discover and make connections to connected storage such as physical disks and external devices .
A Profile-specific Subprofile applies to only one particular Profile. For example, the Fabric Profile identifies the following four Fabric specific Subprofiles:
- Zone Control
- Enhanced Zoning and Enhanced Zoning Control
- FDMI
- Fabric Path Performance
The other Profiles with specific Subprofiles are
A Subprofile can also be referenced by a Package and even another Subprofile.
|
