My environment is a pack of esxi 5.5, vcenter, and 2 DC on that pack, and vmware vrealize automation appliance with iaas installed and configured.
I'm practically stuck with realize next scenario - I want to provide two machines in two datacenter in one time, but when I create a multimachine blueprint in vRa, all vm's is placed only in one datacenter in default vrm folder.
My multimachine at first was made from two single machine cloning from template with custom property "VirtualMachine.Admin.ClusterName" pointing on dc1 and dc2, but automation is ignore this property while clone new vm.
Then I experiment with clone from template resides on dc2, and as result I get a vm in dc1. So when I disable the resorce reservation with dc1 and allow only dc2 resources I get provisioning error "no resources".
I know that I can create wery big complex orchestrator workflow and assign trought a "advanced service", but what if exist more straight path?
Please help me.
Sorry for bad English, it's not my native language.
I find my mistake with reservation configuration - in dc2-reservation I doesnt set any memory, so any vm clone (and creation) get failed.
But to achive my goals I have to make 2 templates in 2 datacentres with different storage and network mapping, and than my multimachine blueprint with 2 single clone blueprint can do his job. I still think it is not most effective way.
I will be very appreciate for any advice with this.
The easiest way to do this would be to use different reservation policies for different datacenters.. That way, the VM's end up in their correct place. However, that means you'll need blueprints defined for each datacenter, each using the blueprints associated with specific datacenter.
As far as multiple templates go, it honestly depends on a number of factors. What I do is configure templates in a central location, then use storage-based replication to mirror them out to all of our remote sites.. That way we have a single, consistent set of templates, but they are available at all remote locations for use.