- Devel - oVirt List Archives

Questions for Redhat team
by Suchitra Herwadkar 13 Dec '18

13 Dec '18

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(a)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(a)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(a)veritas.com Who • pchavva(a)redhat.com - organizer • mahesh.falmari(a)veritas.com • abhay.marode(a)veritas.com • nsoffer(a)redhat.com • ketan.pachpande(a)veritas.com • tnisan(a)redhat.com • sudhakar.paulzagade(a)veritas.com • suchitra.herwadkar(a)veritas.com • navin.tah(a)veritas.com • ehowriga(a)redhat.com • james.olson(a)veritas.com • adbarbos(a)redhat.com - optional • renee.carlisle(a)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&…> To join via Room System: Video Conferencing System: <https://www.google.com/url?q=http%3A%2F%2Fredhat.bjn.vc&sa=D&ust=1545134436…> redhat.bjn.vc<https://www.google.com/url?q=http%3A%2F%2Fredhat.bjn.vc&sa=D&ust=1545134436…> -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…> https://www.redhat.com/en/conference-numbers<https://www.google.com/url?q=https%3A%2F%2Fwww.redhat.com%2Fen%2Fconference…>) 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(a)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>.

2 1

Announcing 'COVERAGE' option in OST
by Marcin Sobczyk 13 Dec '18

13 Dec '18

Hi, I've been working on adding coverage report for VDSM in OST recently, and I'm happy to announce, that the first batch of patches is merged! To run a suite with coverage, look for 'COVERAGE' drop-down on OST's build parameters page. If you run OST locally, pass a '--coverage' argument to 'run_suite.sh'. Currently, coverage works only for VDSM in basic-suite-master, but adding VDSM support for other suites is now a no-brainer. More patches are on the way! Since the option is named 'COVERAGE', and not 'VDSM_COVERAGE', other projects are welcome to implement their coverage reports on top of it. Cheers, Marcin

9 8

ovirt-system-tests_compat-4.2-suite-master is failing since November 27
by Sandro Bonazzola 12 Dec '18

12 Dec '18

hi, ovirt-system-tests_compat-4.2-suite-master is failing since November 27 with following error: Error: Fault reason is "Operation Failed". Fault detail is "[Bond name 'bond_fancy0' does not follow naming criteria. For host compatibility version 4.3 or greater, custom bond names must begin with the prefix 'bond' followed by 'a-z', 'A-Z', '0-9', or '_' characters. For host compatibility version 4.2 and lower, custom bond names must begin with the prefix 'bond' followed by a number.]". HTTP response code is 400. I think that if the scope of the test is to check that 4.2 still works with 4.3 engine, bond_fancy0 works for 4.3 but it's clearly not good for 4.2 and the test needs a fix. -- SANDRO BONAZZOLA MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://red.ht/sig>

6 11

Request for reviews
by Germano Veit Michel 12 Dec '18

12 Dec '18

Hi, I would like to have these 2 trivial changes reviewed and merged in time for 4.3 vdsm. Please have a look: https://gerrit.ovirt.org/#/q/topic:dump-volume-chains+(status:open+OR+statu… Thanks, Germano

1 0

v2v: -o rhv-upload: Upload via NBD
by Nir Soffer 11 Dec '18

11 Dec '18

I posted this patch for vdsm, adding NBD APIs: https://gerrit.ovirt.org/c/96079/ The main purpose of these APIs are enabling incremental restore, but they also enable a more efficient rhv-upload via NBD, and importing to thin disks, which is not possible with current solution. The same idea can work for KubeVirt or other targets, minimizing specific target code. Here is how rhv-upload can work using NBD: 1. rhv-upload plugin separated to pre and post scripts - pre - prepare disk and start image transfer - post - finialize image transfer, create vm, etc. 2. rhr-upload-pre plugin create a transfer with transport="nbd" POST /imagetransfers <image_transfer> <disk id="123"/> <direction>upload</direction> <format>raw</format> <transport>nbd</transport> </image_transfer> Engine does not implement <transport> yet, but this should be an easy change. This will use the new NBD APIs to export the disk using NBD over unix socket. We can support later also NBD over TLS/PSK. Engine will return NBD url in transfer_url: <transfer_url>nbd:unix:/run/vdsm/nbd/<transfer_uuid>.sock</tansfer_url> 3. v2v use the trasfer_url to start qem-img with the NBD server: nbdkit (vddk) -> qemu-img convert -> qemu-nbd Note that nbdkit is removed from the rhv side of the pipeline. This is expected to improve the throughput significantly, since imageio is not very good with lot of small requests generated by qemu-img. 4. rhv-upload-post script invoked to complete the transfer What do you think? Nir

2 2

[VDSM] Incremental backup - vdsm NBD APIs
by Nir Soffer 11 Dec '18

11 Dec '18

I posted patches for vdsm new NBD APIs: https://gerrit.ovirt.org/q/topic:nbd+project:vdsm For the big picture, see the feature page: https://ovirt.org/develop/release-management/features/storage/incremental-b… Changes: - Adding option to run a service as user:group https://gerrit.ovirt.org/c/96077 - Adding back support for systemd-run and systemctl_stop to supervdsm. https://gerrit.ovirt.org/c/96078 - Introducing the NBD APIs https://gerrit.ovirt.org/c/96079 - Starting nbd module tests https://gerrit.ovirt.org/c/96080 - Allow running tests that need supervdsm on your laptop https://gerrit.ovirt.org/c/96081 The infrastructure changes may be useful for other maintainers. Please review, Nir

1 1

ovirt-engine has been tagged (ovirt-engine-4.2.8.1)
by Tal Nisan 10 Dec '18

10 Dec '18

1 0

vdsm has been tagged (v4.20.45)
by Milan Zamazal 10 Dec '18

10 Dec '18

1 0

Lago v0.45 Release Announcement
by Gal Ben Haim 10 Dec '18

10 Dec '18

Hi All, On behalf of the Lago team, I'm pleased to announce Lago v0.45 is available! For a detailed release announcement please refer to our Github page at: https://github.com/lago-project/lago/releases/tag/0.45 Resources ========== Lago Docs: http://lago.readthedocs.io/en/latest/ GitHub: https://github.com/lago-project/lago/ YUM Repository: http://resources.ovirt.org/repos/lago/stable/0.0/rpm/ Pypi: https://pypi.python.org/pypi/lago Docker Hub: https://hub.docker.com/r/lagoproject/lago/ Changelog: https://lago.readthedocs.io/en/latest/_static/ChangeLog.txt As always, if you find any problems, or willing to contribute, visit our GitHub page. Enjoy! -- *GAL BEN HAIM* RHV DEVOPS -- *GAL bEN HAIM* RHV DEVOPS

1 0

[Ovirt] [CQ weekly status] [07-12-2018]
by Dafna Ron 07 Dec '18

07 Dec '18

Hi, This mail is to provide the current status of CQ and allow people to review status before and after the weekend. Please refer to below colour map for further information on the meaning of the colours. *CQ-4.2*: YELLOW (#1) The main issues were packaging issues 1. we needed to replace the 7.6 image due to segmentation faults during add_host. 2. missing dependencies for qemu-kvm-ev - fixed with patch: https://gerrit.ovirt.org/#/c/96055/ *CQ-Master:* YELLOW (#1) 1. we needed to replace the 7.6 image due to segmentation faults during add_host (same as 4.2) 2. vdsm project moved to STDCI v2 which caused failures due to check-patch job which has been failing for a while. although it created failures, vdsm still continued running the V1 jobs which meant tested repo still had updated vdsm packages. Happy week! Dafna ------------------------------------------------------------------------------------------------------------------- COLOUR MAP Green = job has been passing successfully ** green for more than 3 days may suggest we need a review of our test coverage 1. 1-3 days GREEN (#1) 2. 4-7 days GREEN (#2) 3. Over 7 days GREEN (#3) Yellow = intermittent failures for different projects but no lasting or current regressions ** intermittent would be a healthy project as we expect a number of failures during the week ** I will not report any of the solved failures or regressions. 1. Solved job failures YELLOW (#1) 2. Solved regressions YELLOW (#2) Red = job has been failing ** Active Failures. The colour will change based on the amount of time the project/s has been broken. Only active regressions would be reported. 1. 1-3 days RED (#1) 2. 4-7 days RED (#2) 3. Over 7 days RED (#3)

1 0