Class lstorage:VirtualDriveDef (CONCRETE)

Class ID:2074
Encrypted: false - Exportable: true - Persistent: true
Privileges: [admin, ls-compute, ls-config, ls-config-policy, ls-server, ls-storage, ls-storage-policy]
SNMP OID: .1.3.6.1.4.1.9.9.719.1.74.27

Virtual Drive Def


Naming Rules
RN FORMAT: virtual-drive-def

    [1] PREFIX=virtual-drive-def


DN FORMAT: 

[0] org-[name]/tier-[name]/ls-[name]/vdrive-ref-[lunItemName]/disk-group-config/virtual-drive-def

[1] org-[name]/ls-[name]/vdrive-ref-[lunItemName]/disk-group-config/virtual-drive-def

[2] org-[name]/disk-group-config-[name]/virtual-drive-def

[3] org-[name]/profile-[name]/lun-set-config-[name]/virtual-drive-def

[4] org-[name]/tier-[name]/ls-[name]/profile-def/lun-set-config-[name]/virtual-drive-def

[5] org-[name]/ls-[name]/profile-def/lun-set-config-[name]/virtual-drive-def

                



Containers Hierarchies
top:Root This class represents the root element in the object hierarchy. All managed objects in the system are descendants of the Root element.
 ├
org:Org
 
 ├
ls:Server Logical Server Definition. Holds and Regulates Specification of: identity connectivity applied to the physical compute node like compute:Blade upon association. Logical Server can serve the following purposes: associatable instance initialization template persistent ...
 
 
 ├
lstorage:ProfileDef An object contained by {@link ls:Server} that encapsulates the service profile storage requirements. This object provides the same functionality as a {@link lstorage:Profile}, but unlike a {@link lstorage:Profile}, it is contained directly under a {@ls:Server}. This can be useful in cases when the {@link ls:Server} must be self-contained. The storage specified under a Stor...
 
 
 
 ├
lstorage:LunSetConfig
 
 
 
 
 ├
lstorage:VirtualDriveDef
top:Root This class represents the root element in the object hierarchy. All managed objects in the system are descendants of the Root element.
 ├
org:Org
 
 ├
ls:Server Logical Server Definition. Holds and Regulates Specification of: identity connectivity applied to the physical compute node like compute:Blade upon association. Logical Server can serve the following purposes: associatable instance initialization template persistent ...
 
 
 ├
storage:VirtualDriveRef This is a concrete subclass to reference a local deployed LUN (storage:VirtualDrive).
 
 
 
 ├
lstorage:DiskGroupConfigDef
 
 
 
 
 ├
lstorage:VirtualDriveDef
top:Root This class represents the root element in the object hierarchy. All managed objects in the system are descendants of the Root element.
 ├
org:Org
 
 ├
ls:Tier Tier
 
 
 ├
ls:Server Logical Server Definition. Holds and Regulates Specification of: identity connectivity applied to the physical compute node like compute:Blade upon association. Logical Server can serve the following purposes: associatable instance initialization template persistent ...
 
 
 
 ├
lstorage:ProfileDef An object contained by {@link ls:Server} that encapsulates the service profile storage requirements. This object provides the same functionality as a {@link lstorage:Profile}, but unlike a {@link lstorage:Profile}, it is contained directly under a {@ls:Server}. This can be useful in cases when the {@link ls:Server} must be self-contained. The storage specified under a Stor...
 
 
 
 
 ├
lstorage:LunSetConfig
 
 
 
 
 
 ├
lstorage:VirtualDriveDef
top:Root This class represents the root element in the object hierarchy. All managed objects in the system are descendants of the Root element.
 ├
org:Org
 
 ├
ls:Tier Tier
 
 
 ├
ls:Server Logical Server Definition. Holds and Regulates Specification of: identity connectivity applied to the physical compute node like compute:Blade upon association. Logical Server can serve the following purposes: associatable instance initialization template persistent ...
 
 
 
 ├
storage:VirtualDriveRef This is a concrete subclass to reference a local deployed LUN (storage:VirtualDrive).
 
 
 
 
 ├
lstorage:DiskGroupConfigDef
 
 
 
 
 
 ├
lstorage:VirtualDriveDef
top:Root This class represents the root element in the object hierarchy. All managed objects in the system are descendants of the Root element.
 ├
org:Org
 
 ├
lstorage:DiskGroupConfigPolicy
 
 
 ├
lstorage:VirtualDriveDef
top:Root This class represents the root element in the object hierarchy. All managed objects in the system are descendants of the Root element.
 ├
org:Org
 
 ├
lstorage:Profile An object in the org hierarchy that encapsulates storage requirements for a service profile. A storage profile specifies all the storage requirements (Local and remote LUNs, NFS, CIFS...) of a service profile. When the storage profile is deployed, the system automatically selects one or more storage sub-systems and configures the storage as specified in the storage profile. ...
 
 
 ├
lstorage:LunSetConfig
 
 
 
 ├
lstorage:VirtualDriveDef


Contained Hierarchy
lstorage:VirtualDriveDef

Inheritance
lstorage:VirtualDriveDef

Events
                



Faults
                



Fsms
                



Properties Summary
Defined in: lstorage:VirtualDriveDef
storage:VdDefAccessType
          scalar:Enum8
accessPolicy  (lstorage:VirtualDriveDef:accessPolicy)
           The type of data access allowed for the virtual drive
storage:CacheType
          scalar:Enum8
driveCache  (lstorage:VirtualDriveDef:driveCache)
           Virtual drive cache type
storage:IOType
          scalar:Enum8
ioPolicy  (lstorage:VirtualDriveDef:ioPolicy)
           Virtual drive IO policy
storage:ReadType
          scalar:Enum8
readPolicy  (lstorage:VirtualDriveDef:readPolicy)
           Virtual drive read policy
scalar:Bool security  (lstorage:VirtualDriveDef:security)
           Enabling/Disabling security on VD
storage:StripSizeConfig
          scalar:Enum8
stripSize  (lstorage:VirtualDriveDef:stripSize)
           The strip size is the portion of a stripe that resides on a single drive in the drive group. This is measured in KB
storage:ConfiguredWriteType
          scalar:Enum8
writeCachePolicy  (lstorage:VirtualDriveDef:writeCachePolicy)
           Write cache policy
Defined in: mo:TopProps
mo:ModificationChildAction
          scalar:Bitmask32
childAction  (mo:TopProps:childAction)
          
reference:Object dn  (mo:TopProps:dn)
           The Distinguished Name (dn) unambiguously identifies an object in the system.
The dn provides a fully qualified path from the top of the object tree, all the way to the object. It is built as a sequence of relative names separated by the "/" character.
For example:
< ... dn = "sys/chassis-5/blade-2/adaptor-1" />
reference:RN rn  (mo:TopProps:rn)
           The Relative Name (rn) uniquely identifies an object within a given context.
Note that a dn is comprised of a sequence of relative names. For example, the context "sys/chassis-1/blade-1/adaptor-1/host-eth-2" can be thought of as the following expression:
dn = <root object>/{rn}/{rn}/{rn}/{rn}/{rn}.
The rn can then be used to identify the object (for instance, "adaptor-1") within the context:
<... rn ="../" />
mo:InstSaclType
          scalar:Bitmask8
sacl  (mo:TopProps:sacl)
           The system acl property for each Managed Object. br/> This property is a 8 bit mask and supports the following values :-
a: del
b: mod
c: addchild
d: cascade

By default all Managed Objects have the following permissions
a: del
b: mod
c: addchild
This property is persisted in the db. If this property has a value none
it means, the user has read only permissions on this object.
mo:ModificationStatus
          scalar:Bitmask32
status  (mo:TopProps:status)
           This property controls the life cycle of a managed object

Properties Detail

accessPolicy

Type: storage:VdDefAccessType
Primitive Type: scalar:Enum8
Units: null
Encrypted: false
Access: admin
Category: TopLevelRegular
Property Validators:
Comments:
The type of data access allowed for the virtual drive
Constants
platform-default 0 NO COMMENTS
unknown 0 NO COMMENTS
read-write 1 NO COMMENTS
read-only 2 NO COMMENTS
blocked 3 NO COMMENTS
transport-ready 4 NO COMMENTS
hidden 5 NO COMMENTS
DEFAULT unknown(0) NO COMMENTS

childAction

Type: mo:ModificationChildAction
Primitive Type: scalar:Bitmask32
Units: null
Encrypted: false
Access: implicit
Category: TopLevelChildAction
Property Validators:
Comments:
Constants
deleteAll 16384u NO COMMENTS
ignore 4096u NO COMMENTS
deleteNonPresent 8192u NO COMMENTS
DEFAULT 0 This type is used to

dn

Type: reference:Object
Units: null
Encrypted: false
Access: implicit
Category: TopLevelDn
Property Validators:
Comments:
The Distinguished Name (dn) unambiguously identifies an object in the system.
The dn provides a fully qualified path from the top of the object tree, all the way to the object. It is built as a sequence of relative names separated by the "/" character.
For example:
< ... dn = "sys/chassis-5/blade-2/adaptor-1" />

driveCache

Type: storage:CacheType
Primitive Type: scalar:Enum8
Units: null
Encrypted: false
Access: admin
Category: TopLevelRegular
Property Validators:
Comments:
Virtual drive cache type
Constants
platform-default 0 NO COMMENTS
unknown 0 NO COMMENTS
no-change 1 NO COMMENTS
enable 2 NO COMMENTS
disable 3 NO COMMENTS
DEFAULT unknown(0) NO COMMENTS

ioPolicy

Type: storage:IOType
Primitive Type: scalar:Enum8
Units: null
Encrypted: false
Access: admin
Category: TopLevelRegular
Property Validators:
Comments:
Virtual drive IO policy
Constants
platform-default 0 NO COMMENTS
unknown 0 NO COMMENTS
direct 1 NO COMMENTS
cached 2 NO COMMENTS
DEFAULT unknown(0) NO COMMENTS

readPolicy

Type: storage:ReadType
Primitive Type: scalar:Enum8
Units: null
Encrypted: false
Access: admin
Category: TopLevelRegular
Property Validators:
Comments:
Virtual drive read policy
Constants
platform-default 0 NO COMMENTS
unknown 0 NO COMMENTS
read-ahead 1 NO COMMENTS
normal 2 NO COMMENTS
DEFAULT unknown(0) NO COMMENTS

rn

Type: reference:RN
Units: null
Encrypted: false
Access: implicit
Category: TopLevelRn
Property Validators:
Comments:
The Relative Name (rn) uniquely identifies an object within a given context.
Note that a dn is comprised of a sequence of relative names. For example, the context "sys/chassis-1/blade-1/adaptor-1/host-eth-2" can be thought of as the following expression:
dn = <root object>/{rn}/{rn}/{rn}/{rn}/{rn}.
The rn can then be used to identify the object (for instance, "adaptor-1") within the context:
<... rn ="../" />

sacl

Type: mo:InstSaclType
Primitive Type: scalar:Bitmask8
Units: null
Encrypted: false
Access: implicit
Category: TopLevelSacl
Property Validators:
Comments:
The system acl property for each Managed Object. br/> This property is a 8 bit mask and supports the following values :-
a: del
b: mod
c: addchild
d: cascade

By default all Managed Objects have the following permissions
a: del
b: mod
c: addchild
This property is persisted in the db. If this property has a value none
it means, the user has read only permissions on this object.
Constants
none 0 NO COMMENTS
del 1 NO COMMENTS
mod 2 NO COMMENTS
addchild 4 NO COMMENTS
cascade 8 NO COMMENTS
DEFAULT 0 NO COMMENTS

security

Type: scalar:Bool
Units: null
Encrypted: false
Access: admin
Category: TopLevelRegular
Property Validators:
Comments:
Enabling/Disabling security on VD
Constants
yes true NO COMMENTS
defaultValue false NO COMMENTS

status

Type: mo:ModificationStatus
Primitive Type: scalar:Bitmask32
Units: null
Encrypted: false
Access: implicit
Category: TopLevelStatus
Property Validators:
Comments:
This property controls the life cycle of a managed object
Constants
removed 16u In a setter method: specifies that an object should be removed.
In the return value of a setter method: indicates that an object has been removed.
created 2u In a setter method: specifies that an object should be created. An error is returned if the object already exists.
In the return value of a setter method: indicates that an object has been created.
modified 4u In a setter method: specifies that an object should be modified
In the return value of a setter method: indicates that an object has been modified.
deleted 8u In a setter method: specifies that an object should be deleted.
In the return value of a setter method: indicates that an object has been deleted.
DEFAULT 0 This type controls the life cycle of objects passed in the XML API.

When used in a setter method (such as configConfMo), the ModificationStatus specifies whether an object should be created, modified, deleted or removed.
In the return value of a setter method, the ModificationStatus indicates the actual operation that was performed. For example, the ModificationStatus is set to "created" if the object was created. The ModificationStatus is not set if the object was neither created, modified, deleted or removed.

When invoking a setter method, the ModificationStatus is optional:
If a setter method such as configConfMo is invoked and the ModificationStatus is not set, the system automatically determines if the object should be created or modified.


stripSize

Type: storage:StripSizeConfig
Primitive Type: scalar:Enum8
Units: KB
Encrypted: false
Access: admin
Category: TopLevelRegular
Property Validators:
Comments:
The strip size is the portion of a stripe that resides on a single drive in the drive group. This is measured in KB
Constants
platform-default 0 NO COMMENTS
unspecified 0 NO COMMENTS
8KB 1 NO COMMENTS
16KB 2 NO COMMENTS
32KB 3 NO COMMENTS
64KB 4 NO COMMENTS
128KB 5 NO COMMENTS
256KB 6 NO COMMENTS
512KB 7 NO COMMENTS
1024KB 8 NO COMMENTS
DEFAULT unspecified(0) NO COMMENTS

writeCachePolicy

Type: storage:ConfiguredWriteType
Primitive Type: scalar:Enum8
Units: null
Encrypted: false
Access: admin
Category: TopLevelRegular
Property Validators:
Comments:
Write cache policy
Constants
platform-default 0 NO COMMENTS
unknown 0 NO COMMENTS
write-through 1 NO COMMENTS
write-back-good-bbu 2 NO COMMENTS
always-write-back 3 NO COMMENTS
DEFAULT unknown(0) NO COMMENTS