Description of problem: As part of the disaster recovery scenario a recovered site have pre-configured clusters which might be different than the original site. The registration process of unregistered VMs/Templates obligates the user to provide a cluster id. We would like cluster name to the VM/Template OVF. The idea is that on the recovery process we will take the cluster name from the entity OVF and map it using a predefined mapper of DR tool to the cluster on the secondary site. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Maor - everything here seems to be merged. Are we waiting for any other patches, or should this be MODIFIED?
(In reply to Allon Mureinik from comment #1) > Maor - everything here seems to be merged. > Are we waiting for any other patches, or should this be MODIFIED? yes, I got some last touch ups but the functionality should be valid
Setting requires-doc- - we'll document all of the DR improvements together.
Created attachment 1369113 [details] ovf VM OVF now contains the cluster name. <ClusterName>secondary_cluster_1</ClusterName> OVF attached. Used: rhvm-4.2.0.2-0.1.el7.noarch
This bugzilla is included in oVirt 4.2.0 release, published on Dec 20th 2017. Since the problem described in this bug report should be resolved in oVirt 4.2.0 release, published on Dec 20th 2017, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report.