OVF_STORE volumes are not updated
Hi, I noticed that OVF_STORE volumes are not generated periodically as expected [1]. It seems like the OVF_STORE volumes are only generated when the Storage Domain is detached from Engine, which is not feasible if we want to keep the VMs running. 1) Is there any way to force the OVF_STORE volume creation without detaching the Storage Domain? This would be very usefull for disaster recovery, since Storage Domains can be backed up and VM can be reimported. But if the OVF_STORE volumes are not updated, critical information like the ID of the VM active snapshot will get lost. If the VM is restored with a previous snapshot (not the last one), all information written after the last snapshot known by the OVF_STORE will get lost. 2) On the other hand, the only way I know to re-read the OVF_STORE content with the VM information contained in a Storage Domain, is by detaching and re-attaching it. I wonder if there is also any way to re-read the OVF_STORE? [1] : This is can be verified very easily by changing a running VM properties (change its name or create a snapshot), copying the whole storage domain and importing it into another Engine (POOL_UID and CHECKSUM must be removed from metadata in order to be able to attach to another Datacenter). PS: I'm on 3.6 RC. 1.
This is what we discussed on BZ#1268842, right? On Mon, Oct 5, 2015 at 11:35 AM, Christopher Pereira <kripper@imatronix.cl> wrote:
Hi,
I noticed that OVF_STORE volumes are not generated periodically as expected [1]. It seems like the OVF_STORE volumes are only generated when the Storage Domain is detached from Engine, which is not feasible if we want to keep the VMs running.
1) Is there any way to force the OVF_STORE volume creation without detaching the Storage Domain?
This would be very usefull for disaster recovery, since Storage Domains can be backed up and VM can be reimported. But if the OVF_STORE volumes are not updated, critical information like the ID of the VM active snapshot will get lost. If the VM is restored with a previous snapshot (not the last one), all information written after the last snapshot known by the OVF_STORE will get lost.
2) On the other hand, the only way I know to re-read the OVF_STORE content with the VM information contained in a Storage Domain, is by detaching and re-attaching it. I wonder if there is also any way to re-read the OVF_STORE?
[1] : This is can be verified very easily by changing a running VM properties (change its name or create a snapshot), copying the whole storage domain and importing it into another Engine (POOL_UID and CHECKSUM must be removed from metadata in order to be able to attach to another Datacenter).
PS: I'm on 3.6 RC. 1. _______________________________________________ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
This is a multi-part message in MIME format. --------------020106050903080905010807 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Yes. On 14-10-2015 8:48, Allon Mureinik wrote:
This is what we discussed on BZ#1268842, right?
On Mon, Oct 5, 2015 at 11:35 AM, Christopher Pereira <kripper@imatronix.cl <mailto:kripper@imatronix.cl>> wrote:
Hi,
I noticed that OVF_STORE volumes are not generated periodically as expected [1]. It seems like the OVF_STORE volumes are only generated when the Storage Domain is detached from Engine, which is not feasible if we want to keep the VMs running.
1) Is there any way to force the OVF_STORE volume creation without detaching the Storage Domain?
This would be very usefull for disaster recovery, since Storage Domains can be backed up and VM can be reimported. But if the OVF_STORE volumes are not updated, critical information like the ID of the VM active snapshot will get lost. If the VM is restored with a previous snapshot (not the last one), all information written after the last snapshot known by the OVF_STORE will get lost.
2) On the other hand, the only way I know to re-read the OVF_STORE content with the VM information contained in a Storage Domain, is by detaching and re-attaching it. I wonder if there is also any way to re-read the OVF_STORE?
[1] : This can be verified very easily by changing a running VM properties (change its name or create a snapshot), copying the whole storage domain and importing it into another Engine (POOL_UID and CHECKSUM must be removed from metadata in order to be able to attach to another Datacenter).
PS: I'm on 3.6 RC. 1. _______________________________________________ Devel mailing list Devel@ovirt.org <mailto:Devel@ovirt.org> http://lists.ovirt.org/mailman/listinfo/devel
--------------020106050903080905010807 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 7bit <html> <head> <meta content="text/html; charset=utf-8" http-equiv="Content-Type"> </head> <body bgcolor="#FFFFFF" text="#000000"> Yes.<br> <div class="moz-signature"> <style> .signature, .small-signature { font-family:"Calibri","sans-serif";mso-fareast-font-family:"Times New Roman"; color:#7F7F7F; } .signature { font-size:10pt; } .small-signature { font-size:8pt; }</style><br> </div> <div class="moz-cite-prefix">On 14-10-2015 8:48, Allon Mureinik wrote:<br> </div> <blockquote cite="mid:CADgXf3xsnrydQDK+QM4uaJ2gKKjHmFdctKYCSPdP5jLJ0=Y4uQ@mail.gmail.com" type="cite"> <div dir="ltr"> <div class="gmail_default" style="font-family:monospace,monospace">This is what we discussed on BZ#1268842, right?</div> </div> <div class="gmail_extra"><br> <div class="gmail_quote">On Mon, Oct 5, 2015 at 11:35 AM, Christopher Pereira <span dir="ltr"><<a moz-do-not-send="true" href="mailto:kripper@imatronix.cl" target="_blank"><a class="moz-txt-link-abbreviated" href="mailto:kripper@imatronix.cl">kripper@imatronix.cl</a></a>></span> wrote:<br> <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br> <br> I noticed that OVF_STORE volumes are not generated periodically as expected [1].<br> It seems like the OVF_STORE volumes are only generated when the Storage Domain is detached from Engine, which is not feasible if we want to keep the VMs running.<br> <br> 1) Is there any way to force the OVF_STORE volume creation without detaching the Storage Domain?<br> <br> This would be very usefull for disaster recovery, since Storage Domains can be backed up and VM can be reimported.<br> But if the OVF_STORE volumes are not updated, critical information like the ID of the VM active snapshot will get lost.<br> If the VM is restored with a previous snapshot (not the last one), all information written after the last snapshot known by the OVF_STORE will get lost.<br> <br> 2) On the other hand, the only way I know to re-read the OVF_STORE content with the VM information contained in a Storage Domain, is by detaching and re-attaching it.<br> I wonder if there is also any way to re-read the OVF_STORE?<br> <br> [1] : This can be verified very easily by changing a running VM properties (change its name or create a snapshot), copying the whole storage domain and importing it into another Engine (POOL_UID and CHECKSUM must be removed from metadata in order to be able to attach to another Datacenter).<br> <br> PS: I'm on 3.6 RC. 1.<br> _______________________________________________<br> Devel mailing list<br> <a moz-do-not-send="true" href="mailto:Devel@ovirt.org" target="_blank">Devel@ovirt.org</a><br> <a moz-do-not-send="true" href="http://lists.ovirt.org/mailman/listinfo/devel" rel="noreferrer" target="_blank">http://lists.ovirt.org/mailman/listinfo/devel</a><br> <br> <br> </blockquote> </div> <br> </div> </blockquote> <br> </body> </html> --------------020106050903080905010807--
You don't have to detach the Storage Domain to refresh the OVF_STORE, but instead move it to only to maintenance. You can also change the interval value OvfUpdateIntervalInMinutes in the vdc_options table which is by default executes every 60 minutes and sync the OVF_STORE disk with the VMs' and Templates' data. Regards, Maor ----- Original Message -----
From: "Christopher Pereira" <kripper@imatronix.cl> To: "Allon Mureinik" <amureini@redhat.com> Cc: devel@ovirt.org Sent: Wednesday, October 14, 2015 2:53:49 PM Subject: Re: [ovirt-devel] OVF_STORE volumes are not updated
Yes.
On 14-10-2015 8:48, Allon Mureinik wrote:
This is what we discussed on BZ#1268842, right?
On Mon, Oct 5, 2015 at 11:35 AM, Christopher Pereira < kripper@imatronix.cl > wrote:
Hi,
I noticed that OVF_STORE volumes are not generated periodically as expected [1]. It seems like the OVF_STORE volumes are only generated when the Storage Domain is detached from Engine, which is not feasible if we want to keep the VMs running.
1) Is there any way to force the OVF_STORE volume creation without detaching the Storage Domain?
This would be very usefull for disaster recovery, since Storage Domains can be backed up and VM can be reimported. But if the OVF_STORE volumes are not updated, critical information like the ID of the VM active snapshot will get lost. If the VM is restored with a previous snapshot (not the last one), all information written after the last snapshot known by the OVF_STORE will get lost.
2) On the other hand, the only way I know to re-read the OVF_STORE content with the VM information contained in a Storage Domain, is by detaching and re-attaching it. I wonder if there is also any way to re-read the OVF_STORE?
[1] : This can be verified very easily by changing a running VM properties (change its name or create a snapshot), copying the whole storage domain and importing it into another Engine (POOL_UID and CHECKSUM must be removed from metadata in order to be able to attach to another Datacenter).
PS: I'm on 3.6 RC. 1. _______________________________________________ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
_______________________________________________ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
This is a multi-part message in MIME format. --------------050708030208070405020402 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Ok. I will do some tests reducing OvfUpdateIntervalInMinutes and check if OVF_STORE is updated when a new snapshot is created. Thanks. On 14-10-2015 9:21, Maor Lipchuk wrote:
You don't have to detach the Storage Domain to refresh the OVF_STORE, but instead move it to only to maintenance. You can also change the interval value OvfUpdateIntervalInMinutes in the vdc_options table which is by default executes every 60 minutes and sync the OVF_STORE disk with the VMs' and Templates' data.
Regards, Maor
----- Original Message -----
From: "Christopher Pereira" <kripper@imatronix.cl> To: "Allon Mureinik" <amureini@redhat.com> Cc: devel@ovirt.org Sent: Wednesday, October 14, 2015 2:53:49 PM Subject: Re: [ovirt-devel] OVF_STORE volumes are not updated
Yes.
On 14-10-2015 8:48, Allon Mureinik wrote:
This is what we discussed on BZ#1268842, right?
On Mon, Oct 5, 2015 at 11:35 AM, Christopher Pereira < kripper@imatronix.cl > wrote:
Hi,
I noticed that OVF_STORE volumes are not generated periodically as expected [1]. It seems like the OVF_STORE volumes are only generated when the Storage Domain is detached from Engine, which is not feasible if we want to keep the VMs running.
1) Is there any way to force the OVF_STORE volume creation without detaching the Storage Domain?
This would be very usefull for disaster recovery, since Storage Domains can be backed up and VM can be reimported. But if the OVF_STORE volumes are not updated, critical information like the ID of the VM active snapshot will get lost. If the VM is restored with a previous snapshot (not the last one), all information written after the last snapshot known by the OVF_STORE will get lost.
2) On the other hand, the only way I know to re-read the OVF_STORE content with the VM information contained in a Storage Domain, is by detaching and re-attaching it. I wonder if there is also any way to re-read the OVF_STORE?
[1] : This can be verified very easily by changing a running VM properties (change its name or create a snapshot), copying the whole storage domain and importing it into another Engine (POOL_UID and CHECKSUM must be removed from metadata in order to be able to attach to another Datacenter).
PS: I'm on 3.6 RC. 1. _______________________________________________ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
_______________________________________________ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
--------------050708030208070405020402 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 7bit <html> <head> <meta content="text/html; charset=utf-8" http-equiv="Content-Type"> </head> <body bgcolor="#FFFFFF" text="#000000"> Ok. I will do some tests reducing OvfUpdateIntervalInMinutes and check if OVF_STORE is updated when a new snapshot is created.<br> Thanks.<br> <div class="moz-signature"> <style> .signature, .small-signature { font-family:"Calibri","sans-serif";mso-fareast-font-family:"Times New Roman"; color:#7F7F7F; } .signature { font-size:10pt; } .small-signature { font-size:8pt; }</style><br> </div> <div class="moz-cite-prefix">On 14-10-2015 9:21, Maor Lipchuk wrote:<br> </div> <blockquote cite="mid:18823340.54251509.1444825305017.JavaMail.zimbra@redhat.com" type="cite"> <pre wrap="">You don't have to detach the Storage Domain to refresh the OVF_STORE, but instead move it to only to maintenance. You can also change the interval value OvfUpdateIntervalInMinutes in the vdc_options table which is by default executes every 60 minutes and sync the OVF_STORE disk with the VMs' and Templates' data. Regards, Maor ----- Original Message ----- </pre> <blockquote type="cite"> <pre wrap="">From: "Christopher Pereira" <a class="moz-txt-link-rfc2396E" href="mailto:kripper@imatronix.cl"><kripper@imatronix.cl></a> To: "Allon Mureinik" <a class="moz-txt-link-rfc2396E" href="mailto:amureini@redhat.com"><amureini@redhat.com></a> Cc: <a class="moz-txt-link-abbreviated" href="mailto:devel@ovirt.org">devel@ovirt.org</a> Sent: Wednesday, October 14, 2015 2:53:49 PM Subject: Re: [ovirt-devel] OVF_STORE volumes are not updated Yes. On 14-10-2015 8:48, Allon Mureinik wrote: This is what we discussed on BZ#1268842, right? On Mon, Oct 5, 2015 at 11:35 AM, Christopher Pereira < <a class="moz-txt-link-abbreviated" href="mailto:kripper@imatronix.cl">kripper@imatronix.cl</a> > wrote: Hi, I noticed that OVF_STORE volumes are not generated periodically as expected [1]. It seems like the OVF_STORE volumes are only generated when the Storage Domain is detached from Engine, which is not feasible if we want to keep the VMs running. 1) Is there any way to force the OVF_STORE volume creation without detaching the Storage Domain? This would be very usefull for disaster recovery, since Storage Domains can be backed up and VM can be reimported. But if the OVF_STORE volumes are not updated, critical information like the ID of the VM active snapshot will get lost. If the VM is restored with a previous snapshot (not the last one), all information written after the last snapshot known by the OVF_STORE will get lost. 2) On the other hand, the only way I know to re-read the OVF_STORE content with the VM information contained in a Storage Domain, is by detaching and re-attaching it. I wonder if there is also any way to re-read the OVF_STORE? [1] : This can be verified very easily by changing a running VM properties (change its name or create a snapshot), copying the whole storage domain and importing it into another Engine (POOL_UID and CHECKSUM must be removed from metadata in order to be able to attach to another Datacenter). PS: I'm on 3.6 RC. 1. _______________________________________________ Devel mailing list <a class="moz-txt-link-abbreviated" href="mailto:Devel@ovirt.org">Devel@ovirt.org</a> <a class="moz-txt-link-freetext" href="http://lists.ovirt.org/mailman/listinfo/devel">http://lists.ovirt.org/mailman/listinfo/devel</a> _______________________________________________ Devel mailing list <a class="moz-txt-link-abbreviated" href="mailto:Devel@ovirt.org">Devel@ovirt.org</a> <a class="moz-txt-link-freetext" href="http://lists.ovirt.org/mailman/listinfo/devel">http://lists.ovirt.org/mailman/listinfo/devel</a> </pre> </blockquote> <pre wrap=""> </pre> </blockquote> <br> </body> </html> --------------050708030208070405020402--
participants (3)
-
Allon Mureinik -
Christopher Pereira -
Maor Lipchuk