I am starting to design our 8.1 environment and need help figuring out how deployments can be migrated to a new blueprint? The scenario being, we would like to build a blueprint for single instance VM provisioning that can provision Win/Linux servers OS's. It initial implementation would be pretty straight forward but as the blueprint matures I could see the need to split the blueprint either for technical or customer experience reasons.
In 7.6 migrating VM's to a new blueprint required unregistering them, then importing them using the new blueprint. This was easier said than done, and ultimately did not work for us due to issues with IPAM.
Question: In 8.x is there a process for moving deployments (in our case single VM's) to a different blueprint which will allow for clean deprovisioning?
I understand the blueprints would likely have to be similar, which they would be. Over time I imagine our blueprint will evolve and I want to ensure we can still allow users to deprovision their VM's within the service broker, while at the same time not keeping old blueprints around. Hopefully that makes sense.
Thanks for reading.
Do you mean, there is no way to do it? I can't tell if that was a typo.
Is there a process for decommissioning a blueprint then? There has to be some method to migrate VM's.. I hope?
I think there is no way to do it within this version, as we don't have a supported method to unregister VMs.
Regarding this: "Is there a process for decommissioning a blueprint then? There has to be some method to migrate VM's.. I hope?"
I'll ask this and let you know