Questions for Redhat team
Hi Nir & RedHat team 1. Cloned VM support in RHV. There are two types of clones as per my understanding 1. Full Cloned VM: Independent copy of a virtual machine that shares nothing with the parent template after the cloning operation. 2. Dependent Cloned VM: It is a copy of a virtual machine that shares virtual disks with the parent template. This type of clone is made from a snapshot of the parent which is qcow2 image. All files available on the parent at the moment of the snapshot continue to remain available to the linked clone. Ongoing changes to the virtual disk of the parent do not affect the linked clone, and changes to the disk of the linked clone do not affect the parent. We want to know what the customer preference ( 1 or 2) as both have pros & cons. What is the guidance given by RHV around this? How do we recommend customers to patch the template disks when multiple VMs are cloned from it? Kindly provide more details. 1. Is there a way to we can mount a QCOW2 image using QCOW2 mounter and have a block level view of the data ? We read about libguestfs but this is filesystem view. 1. We would like to know when we can expect “Allocation Regions API” . I’m referring to https://bugzilla.redhat.com/show_bug.cgi?id=1622946 This is marked for 4.3 at this point in time. I presume we will get it as part of 4.2.X release as well. Kindly confirm ? Thanks Suchitra From: pchavva@redhat.com When: 8:30 PM - 9:00 PM December 13, 2018 Subject: [EXTERNAL] Canceled event: RHV- Veritas Netbackup Weekly Sync @ Thu Dec 13, 2018 10am - 10:30am (EST) (suchitra.herwadkar@veritas.com) This event has been canceled. RHV- Veritas Netbackup Weekly Sync When Thu Dec 13, 2018 10am – 10:30am Eastern Time - New York Calendar suchitra.herwadkar@veritas.com Who • pchavva@redhat.com - organizer • mahesh.falmari@veritas.com • abhay.marode@veritas.com • nsoffer@redhat.com • ketan.pachpande@veritas.com • tnisan@redhat.com • sudhakar.paulzagade@veritas.com • suchitra.herwadkar@veritas.com • navin.tah@veritas.com • ehowriga@redhat.com • james.olson@veritas.com • adbarbos@redhat.com - optional • renee.carlisle@veritas.com - optional Agenda: This Engineering weekly sync will cover the engagement activity for Netbackup and RHV integration. To join the Meeting: https://bluejeans.com/5723877297<https://www.google.com/url?q=https%3A%2F%2Fbluejeans.com%2F5723877297&sa=D&ust=1545134436601000&usg=AFQjCNEU3vxF2EbxmxU4ygldTNyv5p2NrQ> To join via Room System: Video Conferencing System: <https://www.google.com/url?q=http%3A%2F%2Fredhat.bjn.vc&sa=D&ust=1545134436601000&usg=AFQjCNEO3YYgeVkhEE8deWM-3AfO_nfvlg> redhat.bjn.vc<https://www.google.com/url?q=http%3A%2F%2Fredhat.bjn.vc&sa=D&ust=1545134436601000&usg=AFQjCNEO3YYgeVkhEE8deWM-3AfO_nfvlg> -or-199.48.152.18 Meeting ID : 5723877297 To join via phone : 1) Dial: 408-915-6466 (United States) (see all numbers - <https://www.google.com/url?q=https%3A%2F%2Fwww.redhat.com%2Fen%2Fconference-numbers&sa=D&ust=1545134436602000&usg=AFQjCNHWnVI60XQbOYkf1paPITO1l9ifsQ> https://www.redhat.com/en/conference-numbers<https://www.google.com/url?q=https%3A%2F%2Fwww.redhat.com%2Fen%2Fconference-numbers&sa=D&ust=1545134436602000&usg=AFQjCNHWnVI60XQbOYkf1paPITO1l9ifsQ>) 2) Enter Conference ID : 5723877297 Invitation from Google Calendar<https://www.google.com/calendar/> You are receiving this courtesy email at the account suchitra.herwadkar@veritas.com because you are an attendee of this event. To stop receiving future updates for this event, decline this event. Alternatively you can sign up for a Google account at https://www.google.com/calendar/ and control your notification settings for your entire calendar. Forwarding this invitation could allow any recipient to modify your RSVP response. Learn More<https://support.google.com/calendar/answer/37135#forwarding>.
On Thu, Dec 13, 2018 at 3:24 PM Suchitra Herwadkar < Suchitra.Herwadkar@veritas.com> wrote:
Hi Nir & RedHat team
1. Cloned VM support in RHV.
There are two types of clones as per my understanding
1. Full Cloned VM: Independent copy of a virtual machine that shares nothing with the parent template after the cloning operation. 2. Dependent Cloned VM: It is a copy of a virtual machine that shares virtual disks with the parent template. This type of clone is made from a snapshot of the parent which is qcow2 image. All files available on the parent at the moment of the snapshot continue to remain available to the linked clone. Ongoing changes to the virtual disk of the parent do not affect the linked clone, and changes to the disk of the linked clone do not affect the parent.
We want to know what the customer preference ( 1 or 2) as both have pros & cons. What is the guidance given by RHV around this? How do we recommend customers to patch the template disks when multiple VMs are cloned from it? Kindly provide more details.
Customer can use both types of clones, based on their needs. If having the dependency on the a shared template is fine, and the user is ok with having qcow2 format and at least one snapshot, and prefer faster cloning, they can go with this option. If the user wants to use raw format which can give better performance, and ok with waiting for a slower clone, copying all the data to new image, they can go with full clone. So I think on your side you should support both options, so users can make the best choice for their needs.
1. Is there a way to we can mount a QCOW2 image using QCOW2 mounter and have a block level view of the data ? We read about libguestfs but this is filesystem view.
In 4.3 we will use NBD protocol to allow block level view of an image, including all snapshots. You will be able to do full or incremental backup, or restore raw data to qcow2 image. See: https://ovirt.org/develop/release-management/features/storage/incremental-ba...
1. We would like to know when we can expect “Allocation Regions API” . I’m referring to
This is part of incremental backup effort: https://ovirt.org/develop/release-management/features/storage/incremental-ba...
This is marked for 4.3 at this point in time. I presume we will get it as part of 4.2.X release as well.
No, this requires major changes in engine, vdsm and imageio, which will be available only in 4.3. The new API is documented here: https://ovirt.org/develop/release-management/features/storage/incremental-ba... We would like to get early feedback, before we implement it. Nir
participants (2)
-
Nir Soffer -
Suchitra Herwadkar