I've got a scenario where a customer may want a single blueprint to be deployed on either replicated storage or non-replicated storage. Since this is a single blueprint that could be deployed on two different datastores, I can't use a Reservatoin Policy to make the decision because it's tied to an entire blueprint.
My plan was to:
- Execute an update property worfklow during the VMPSMasterWorkflow32.Requested Lifecycle State. That changed a reservation policy based on a user input.
- When the machine lifecycle state hits the VMPSMasterWorkflow32.BuildingMachine it would use the updated reservation policy to place the VM in the right datastore.
It turns out that this doesn't work.
The property updates successfully and you can see the property has been changed once the machine has been provi@sioned, but it doesn't use the changed value during provisioning.
Does anyone have any insight on a way to do this other than the usual suspects:
- Post Provisioning Action to Storage vMotion the machine,
- Publish two blueprints and make the user decide which one to use.