13.07.2015 Views

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

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

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

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

the initiator adapter object that corresponds to the initiator adapter that contains the initiator portal.The server MUST add these objects to the list of storage management objects.After initialization is complete, the server MUST set the service object's service-ready state to"ready". If initialization fails, the server MUST set the service object's service-ready state to "failed".3.4.3.2 Notification Callback ObjectsThe server initializes an empty list of callback objects.3.4.4 Higher-Layer Triggered EventsNone.3.4.5 Message Processing Events and Sequencing Rules3.4.5.1 Sequencing Rules3.4.5.1.1 Adding Pack Objects for Dynamic ProvidersThe server MUST maintain a list of detected dynamic disk packs. When the server discovers a newpack (either during initialization or when a new pack arrives after initialization), it MUST create acorresponding pack object and MUST assign it a unique <strong>VDS</strong>_OBJECT_ID.The server MUST set the pack object's provider pointer to the provider object that corresponds tothe dynamic provider. The server MUST add the pack object to the list of storage managementobjects. For each callback object that is registered in the list of callback objects, the server MUSTcall the callback object's IVdsAdviseSink::OnNotify (Opnum 3) method with a<strong>VDS</strong>_NOTIFICATION structure that has the following attributes:•objectType member is <strong>VDS</strong>_NTT_PACK.•Pack member is a <strong>VDS</strong>_PACK_NOTIFICATION that has the following attributes:•ulEvent is <strong>VDS</strong>_NF_PACK_ARRIVE.•packId is the <strong>VDS</strong>_OBJECT_ID of the pack object that was added.3.4.5.1.2 Removing Pack Objects for Dynamic ProvidersThe server MUST maintain a list of detected dynamic disk packs. When the server discovers that apack was removed, it MUST remove the corresponding pack object from the list of storagemanagement objects. For each callback object that is registered in the list of callback objects, theserver MUST call the IVdsAdviseSink::OnNotify (Opnum 3) method for the callback object with a<strong>VDS</strong>_NOTIFICATION structure that has the following attributes:•objectType member set to <strong>VDS</strong>_NTT_PACK.•Pack member set to a <strong>VDS</strong>_PACK_NOTIFICATION that has the following attributes:•ulEvent set to <strong>VDS</strong>_NF_PACK_DEPART.•packId set to the <strong>VDS</strong>_OBJECT_ID of the pack object that was removed.[<strong>MS</strong>-<strong>VDS</strong>] — v20110610<strong>Virtual</strong> <strong>Disk</strong> <strong>Service</strong> (<strong>VDS</strong>) <strong>Protocol</strong> <strong>Specification</strong>Copyright © 2011 Microsoft Corporation.Release: Friday, June 10, 2011161 / 360

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!