Hi, We have two actions in Virtual media schema as InsertMedia, EjectMedia which can be used to change values of Inserted, Writeprotected Attributes As per VirtualMedia schema, Inserted, Writeprotected Attributes readonly property is false which means it can be changed by user using patch method. If user patches Inserted, Writeprotected as false means, how it needs to be handled, like do we need to invoke action of EjectMedia. If implementation calls EjectMedia action for Patching false value, why we need to have separate action. Through InsertMedia, EjectMedia action, implementation can change Inserted, Writeprotected Attributes values so schema is mentioning Readonly as false as per my understanding, But when we interpret readonly as False in schema means it can allow patch operation to change value Please explain the usage of changing values of Inserted, Writeprotected through patch operation(without calling Actions)
The Actions were added because the addition/removal of virtual media can have side effects, and we didn't like having single patch properties to have those types of effects. Also, the Action provides a means to specify all of the properties (parameters) that are needed to fully specify the correct desired outcome.
We'd recommend using the Actions for both Insert/Eject...
We're going to take a look at this area as there have been other folks concerned about interoperability with this aspect of the model. If anything there should be some more documentation for how this is supposed to function.
Hi Jeff, Thanks for details and you are correct about Patching Inserted attribute value. For example If user patches Inserted as true only, then other parameters required for Inserted Action is not available, so calling Action is also not possible. So it's better not to allow patching Inserted, Writeprotected Attributes directly from implementation. I hope this can be explained in document or schema to make it clear for User in future