[MS-VDS]: Virtual Disk Service (VDS) Protocol Specification

3.4.1.1 Service ObjectThe service object exposes DCOM interfaces for retrieving and interacting with all storagemanagement objects. The service object:•Implements IVdsService and IVdsServiceInitialization interfaces.•Implements IVdsServiceUninstallDisk, IVdsServiceHba, IVdsServiceSAN, andIVdsServiceIscsi interfaces.•Maintains a value that indicates the ready state of the service. The service-ready state values are"not ready", "ready", or "failed". When an object is created, this value will be "not ready". Whenthe service is finished initializing, this value will be changed to "ready". After the value is "ready",it will not change.3.4.1.2 Storage Management ObjectsThe server maintains a list of the following VDS objects:•HBA Port•The server maintains an object for each HBA port on the system.•Each HBA port object exposes DCOM interfaces for querying information from an HBA port onthe system.•Each HBA port object implements the IVdsHbaPort interface.•Initiator Adapter•The server maintains an object for each initiator adapter on the system.•Each initiator adapter object exposes DCOM interfaces for querying information from an iSCSIinitiator adapter on the system.•Each initiator adapter object implements the IVdsIscsiInitiatorAdapter interface.•Initiator Portal•The server maintains an object for each initiator portal on the system.•Each initiator portal object exposes DCOM interfaces for querying information from an iSCSIinitiator portal on the system.•Each initiator portal object implements the IVdsIscsiInitiatorPortal interface.•Each initiator portal object maintains a pointer to the initiator adapter object to which itbelongs.•Software Provider•The server maintains an object for each provider on the system.•The basic provider is for managing basic disks.•The dynamic provider is for managing dynamic disks.[MS-VDS] — v20110610Virtual Disk Service (VDS) Protocol SpecificationCopyright © 2011 Microsoft Corporation.Release: Friday, June 10, 2011154 / 360