<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Feb 8, 2018 at 10:34 AM, Luca 'remix_tj' Lorenzetto <span dir="ltr"><<a href="mailto:lorenzetto.luca@gmail.com" target="_blank">lorenzetto.luca@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On Tue, Feb 6, 2018 at 9:33 PM, Maor Lipchuk <<a href="mailto:mlipchuk@redhat.com">mlipchuk@redhat.com</a>> wrote:<br>
[cut]<br>
<span class="gmail-">>> What i need is that informations about vms is replicated to the remote<br>
>> site with disk.<br>
>> In an older test i had the issue that disks were replicated to remote<br>
>> site, but vm configuration not!<br>
>> I've found disks in the "Disk" tab of storage domain, but nothing on VM<br>
>> Import.<br>
><br>
><br>
><br>
> Can you reproduce it and attach the logs of the setup before the disaster<br>
> and after the recovery?<br>
> That could happen in case of new created VMs and Templates which were not<br>
> yet updated in the OVF_STORE disk, since the OVF_STORE update process was<br>
> not running yet before the disaster.<br>
> Since the time of a disaster can't be anticipated, gaps like this might<br>
> happen.<br>
><br>
<br>
</span>I haven't tried the recovery yet using ansible. It was an experiment<br>
of possible procedure to be performed manually and was on 4.0.<br>
I asked about this unexpected behavior and Yaniv returned me that was<br>
due to OVF_STORE not updated and that in 4.1 there is an api call that<br>
updates OVF_STORE on demand.<br>
<br>
I'm creating a new setup today and i'll test again and check if i<br>
still hit the issue. Anyway if the problem persist i think that<br>
engine, for DR purposes, should upgrade the OVF_STORE as soon as<br>
possible when a new vm is created or has disks added.<br></blockquote><div><br></div><div><br></div><div>If engine will update the OVF_STORE on any VM change that could reflect the oVirt performance since it is a heavy operation,</div><div>although we do have some ideas to change that design so every VM change will only change the VM OVF instead of the whole OVF_STORE disk.</div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
[cut]<br>
<span class="gmail-">>><br>
>> Ok, but if i keep master storage domain on a non replicate volume, do<br>
>> i require this function?<br>
><br>
><br>
> Basically it should also fail on VM/Template registration in oVirt 4.1 since<br>
> there are also other functionalities like mapping of OVF attributes which<br>
> was added on VM/Templates registeration.<br>
><br>
<br>
</span>What do you mean? That i could fail to import any VM/Template? In what case?<br></blockquote><div><br></div><div><br></div><div>If using the fail-over in ovirt-ansible-disaster-recovery, the VM/Template registration process is being done automatically through the ovirt-ansible tasks and it is based on the oVirt 4.2 API.</div><div>The task which registers the VMs and the Templates is being done there without indicating the target cluster id, since in oVirt 4.2 we already added the cluster name in the VM's/Template's OVF.</div><div>If your engine is oVirt 4.1 the registration will fail since in oVirt 4.1 the cluster id is mandatory.</div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
<br>
Another question:<br>
<br>
we have 2 DCs in main site, do we require to have also 2 DCs in<br>
recovery site o we can import all the storage domains in a single DC<br>
on recovery site? There could be uuid collisions or similar?<br></blockquote><div><br></div><div><br></div><div>I think it could work, although I suggest that the clusters should be compatible with those configurd in the primary setup</div><div>otherwise you might encounter problems when you will try to fail back (and also to avoid any collisions of affinity groups/labels or networks).</div><div>For example if in your primary site you had DC1 with cluster1 and DC2 with cluster2 then your secondary setup should be DC_Secondary with cluster_A and cluster_B.</div><div>cluster1 will be mapped to cluster_A and cluster2 will be mapped to cluster_B.</div><div><br></div><div>Another thing that might be troubling is with the master domain attribute in the mapping var file.</div><div>That attribute indicates which storage domain is master or not.</div><div>Here is an example how it is being configured in the mapping file:</div><div><div>- dr_domain_type: nfs</div><div> dr_primary_dc_name: Prod</div><div> dr_primary_name: data_number</div><div> dr_master_domain: True</div><div> dr_secondary_dc_name: Recovery<br></div><div> dr_secondary_address: <br></div><div>...</div></div><div><br></div><div><br></div><div>In your primary site you have two master storage domains, and in your secondary site what will probably happen is that on import of storage domains only one of those two storage domains will be master.</div><div>Now that I think of it, it might be better to configure the master attribute for each of the setups, like so:</div><div><div> dr_primary_master_domain: True<br></div><div> dr_secondary_master_domain: False</div></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
Thank you so much for your replies,<br>
<div class="gmail-HOEnZb"><div class="gmail-h5"><br>
Luca<br>
--<br>
"E' assurdo impiegare gli uomini di intelligenza eccellente per fare<br>
calcoli che potrebbero essere affidati a chiunque se si usassero delle<br>
macchine"<br>
Gottfried Wilhelm von Leibnitz, Filosofo e Matematico (1646-1716)<br>
<br>
"Internet è la più grande biblioteca del mondo.<br>
Ma il problema è che i libri sono tutti sparsi sul pavimento"<br>
John Allen Paulos, Matematico (1945-vivente)<br>
<br>
Luca 'remix_tj' Lorenzetto, <a href="http://www.remixtj.net" rel="noreferrer" target="_blank">http://www.remixtj.net</a> , <<a href="mailto:lorenzetto.luca@gmail.com">lorenzetto.luca@gmail.com</a>><br>
</div></div></blockquote></div><br></div></div>