In our blueprint, we supply a specific imageRef to use for cloning, which contains a valid template. However, during the Compute Allocation phase, we would like to be able to re-assign the imageRef property to a different template - a copy that we know is in the cluster we're deploying to (for faster cloning). We do have all of that working and are sending the updated imageRef value back to vRA in a customProperties attribute.
But when the clone actually takes place in vSphere, it uses the original template. We can verify that the imageRef value is updated as it should be in customProperties, but it seems to be ignored when the cloning. Does anyone know if this something we should be able to do in 8.1? Or if there is another way to change the template used for cloning after the request is submitted?
In 7.5, we update the __clonefrom field, which works as expected.
Any insight is appreciated, thanks!
I am thinking on another way to do it. What if you add some Capability Tags to your clusters and depending which Cluster you select for the provisioning you can specify a particular imageRef_
Thanks for the reply, but I think I may end up in the same spot. Ultimately, we won't know which cluster the build will wind up in before the request is submitted by the user - it's not something we want them to select, and multiple clusters could match based on the capability tags. So there's no way for us to have the image we want to use in the blueprint simply because we can't know until placement happens.
So this may be another way to determine the image we want to use during the compute allocation, but we'd still need to find a way to tell vRA to use the updated image we select. That's the part that doesn't seem to be working. It's as if the imageRef at request time is set in stone and can't be altered again before provisioning.
Unless there is a different way to update the imageRef other than through modifying the custom properties?
Working with support on this. It does seem like the imageRef value can be updated successfully during Compute Reservation, but unfortunately I don't think that helps us since we still won't know which cluster we'll be landing in at that phase. That event does have a placementIds array in its schema, so we may be able to use that to choose a cluster ourselves.....but doesn't look promising as of now. I've asked support to see if they can identify exactly what those placementIds represent, since it is not documented - no word yet.