- Devel - oVirt List Archives

device compatibility interface for live migration with assigned devices
by Yan Zhao 15 Sep '20

15 Sep '20

hi folks, we are defining a device migration compatibility interface that helps upper layer stack like openstack/ovirt/libvirt to check if two devices are live migration compatible. The "devices" here could be MDEVs, physical devices, or hybrid of the two. e.g. we could use it to check whether - a src MDEV can migrate to a target MDEV, - a src VF in SRIOV can migrate to a target VF in SRIOV, - a src MDEV can migration to a target VF in SRIOV. (e.g. SIOV/SRIOV backward compatibility case) The upper layer stack could use this interface as the last step to check if one device is able to migrate to another device before triggering a real live migration procedure. we are not sure if this interface is of value or help to you. please don't hesitate to drop your valuable comments. (1) interface definition The interface is defined in below way: __ userspace /\ \ / \write / read \ ________/__________ ___\|/_____________ | migration_version | | migration_version |-->check migration --------------------- --------------------- compatibility device A device B a device attribute named migration_version is defined under each device's sysfs node. e.g. (/sys/bus/pci/devices/0000\:00\:02.0/$mdev_UUID/migration_version). userspace tools read the migration_version as a string from the source device, and write it to the migration_version sysfs attribute in the target device. The userspace should treat ANY of below conditions as two devices not compatible: - any one of the two devices does not have a migration_version attribute - error when reading from migration_version attribute of one device - error when writing migration_version string of one device to migration_version attribute of the other device The string read from migration_version attribute is defined by device vendor driver and is completely opaque to the userspace. for a Intel vGPU, string format can be defined like "parent device PCI ID" + "version of gvt driver" + "mdev type" + "aggregator count". for an NVMe VF connecting to a remote storage. it could be "PCI ID" + "driver version" + "configured remote storage URL" for a QAT VF, it may be "PCI ID" + "driver version" + "supported encryption set". (to avoid namespace confliction from each vendor, we may prefix a driver name to each migration_version string. e.g. i915-v1-8086-591d-i915-GVTg_V5_8-1) (2) backgrounds The reason we hope the migration_version string is opaque to the userspace is that it is hard to generalize standard comparing fields and comparing methods for different devices from different vendors. Though userspace now could still do a simple string compare to check if two devices are compatible, and result should also be right, it's still too limited as it excludes the possible candidate whose migration_version string fails to be equal. e.g. an MDEV with mdev_type_1, aggregator count 3 is probably compatible with another MDEV with mdev_type_3, aggregator count 1, even their migration_version strings are not equal. (assumed mdev_type_3 is of 3 times equal resources of mdev_type_1). besides that, driver version + configured resources are all elements demanding to take into account. So, we hope leaving the freedom to vendor driver and let it make the final decision in a simple reading from source side and writing for test in the target side way. we then think the device compatibility issues for live migration with assigned devices can be divided into two steps: a. management tools filter out possible migration target devices. Tags could be created according to info from product specification. we think openstack/ovirt may have vendor proprietary components to create those customized tags for each product from each vendor. e.g. for Intel vGPU, with a vGPU(a MDEV device) in source side, the tags to search target vGPU are like: a tag for compatible parent PCI IDs, a tag for a range of gvt driver versions, a tag for a range of mdev type + aggregator count for NVMe VF, the tags to search target VF may be like: a tag for compatible PCI IDs, a tag for a range of driver versions, a tag for URL of configured remote storage. b. with the output from step a, openstack/ovirt/libvirt could use our proposed device migration compatibility interface to make sure the two devices are indeed live migration compatible before launching the real live migration process to start stream copying, src device stopping and target device resuming. It is supposed that this step would not bring any performance penalty as -in kernel it's just a simple string decoding and comparing -in openstack/ovirt, it could be done by extending current function check_can_live_migrate_destination, along side claiming target resources.[1] [1] https://specs.openstack.org/openstack/nova-specs/specs/stein/approved/libvi… Thanks Yan

14 117

ovirt-engine has been tagged (ovirt-engine-4.4.2.6)
by Tal Nisan 14 Sep '20

14 Sep '20

1 0

Re: oVirt Terraform Provider
by Sandro Bonazzola 14 Sep '20

14 Sep '20

Il giorno gio 3 set 2020 alle ore 12:29 Jake Reynolds < jake.reynolds(a)bidfx.com> ha scritto: > Hi, > > A number of PRs (bug fixes & feature additions) are outstanding on the > oVirt Terraform Provider https://github.com/oVirt/terraform-provider-ovirt. > There seems to have been no activity on the master branch of the repo for > months. > > 1. How can I promote/request that PRs are reviewed in a timely manner? > > Hi, +Roy Golan <rgolan(a)redhat.com> , +Roberto Ciatti <rciatti(a)redhat.com> , +Gal Zaidman <gzaidman(a)redhat.com> , +Evgeny Slutsky <eslutsky(a)redhat.com> can you please review pull requests in https://github.com/oVirt/terraform-provider-ovirt/pulls ? Thanks, > > 1. > 2. I am using this to deploy a global infrastructure over the next > year and expect to be doing further extensions/improvements over that time > (done 5 PRs in the past few weeks alone). How do I go about becoming part > of the community and getting write access to this repo if there is no > active maintainer? > > Welcome aboard :-) you're now part of the community! For getting merge rights into the repo, current maintainer should accept you as co-maintainer there. You can discuss here further extensions/improvements you'd like to work on or open bugs/rfe on https://bugzilla.redhat.com/enter_bug.cgi?product=ovirt-distribution&compon… for starting the discussion. If you prefer to work on github only I would recommend to ping here as well, to be sure people will be aware of the issue / pull request has been opened. > > 1. > > Thanks, > > > Jake > > > _______________________________________________ > Devel mailing list -- devel(a)ovirt.org > To unsubscribe send an email to devel-leave(a)ovirt.org > Privacy Statement: https://www.ovirt.org/privacy-policy.html > oVirt Code of Conduct: > https://www.ovirt.org/community/about/community-guidelines/ > List Archives: > https://lists.ovirt.org/archives/list/devel@ovirt.org/message/QCECG5CP4XO7M… > -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://www.redhat.com/> *Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours. <https://mojo.redhat.com/docs/DOC-1199578>*

2 1

[ARM64] Possiblity to support oVirt on ARM64
by Zhenyu Zheng 11 Sep '20

11 Sep '20

Hi oVirt, We are currently trying to make oVirt work on ARM64 platform, since I'm quite new to oVirt community, I'm wondering what is the current status about ARM64 support in the oVirt upstream, as I saw the oVirt Wikipedia page mentioned there is an ongoing efforts to support ARM platform. We have a small team here and we are willing to also help to make this work. Thanks alot, Zhenyu Zheng

6 8

ovirt-engine has been tagged (ovirt-engine-4.4.2.5)
by Tal Nisan 11 Sep '20

11 Sep '20

1 0

CI cannot find ioprocess package
by Vojtech Juranek 09 Sep '20

09 Sep '20

Hi, CI fails quite often with Error: Unable to find a match: python3-ioprocess-1.4.1 see e.g. [1, 2]. Can someone please take a look? Thanks Vojta [1] https://jenkins.ovirt.org/job/vdsm_standard-check-patch/23502 [2] https://jenkins.ovirt.org/job/vdsm_standard-check-patch/23503

2 1

isort errors while make install
by Prajith Kesava Prasad 09 Sep '20

09 Sep '20

Hi, everytime i clone and run make install i get this error, as a workaround i remove them and re-run which works fine, but i wanted to know the root cause, i thought it was because i pulled a wrong head ref?, or is it a common issue? ``` packaging/setup/plugins/ovirt-engine-setup/ovirt-engine/config/aaajdbc.py:249:21 '...'.format(...) has unused named argument(s): profile packaging/setup/plugins/ovirt-engine-setup/ovirt-engine/upgrade/auth_url_validation.py:75:13 '...'.format(...) has unused named argument(s): ownConnection + echo ERROR: The following check failed: ERROR: The following check failed: ``` Regards, Prajith

3 2

ovirt-engine has been tagged (ovirt-engine-4.4.3.2)
by Tal Nisan 09 Sep '20

09 Sep '20

1 0

[CI] Builds broken by "Status code: 403 for http://resources.ovirt.org/pub/yum-repo/ovirt-release-master.rpm"
by Nir Soffer 08 Sep '20

08 Sep '20

This is the second time, last time there was an issue during a nightly job that left the master snapshot repo broken. I have 3 failure builds: https://jenkins.ovirt.org/job/ovirt-engine_standard-check-patch/7744/ https://jenkins.ovirt.org/job/ovirt-engine_standard-check-patch/7751/ https://jenkins.ovirt.org/job/ovirt-engine_standard-check-patch/7755/ All seems to fail in: [2020-09-07T10:00:56.163Z] + dnf install -y http://resources.ovirt.org/pub/yum-repo/ovirt-release-master.rpm [2020-09-07T10:01:08.524Z] Status code: 403 for http://resources.ovirt.org/pub/yum-repo/ovirt-release-master.rpm (IP: 66.187.230.40) Checking manually show: $ curl https://resources.ovirt.org/pub/yum-repo/ovirt-release-master.rpm <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>403 Forbidden</title> </head><body> <h1>Forbidden</h1> <p>You don't have permission to access /pub/yum-repo/ovirt-release-master.rpm on this server.</p> </body></html> Looking at: https://resources.ovirt.org/pub/yum-repo/ ovirt-elease-master.rpm does not exist. So we have 2 issues: - The file does not exist - We return "403 Forbidden" instead of "404 Not Found"

3 6

gerrit pull/clone timeout
by Prajith Kesava Prasad 07 Sep '20

07 Sep '20

Is anyone else facing an issue of timeout (forever) while cloning/pulling ovirt-engine at times in gerrit, i followed the required procedures like adding ssh keys etc, did anything change or am I missing something? I have pasted the vv output for the same ``` $ git clone git://gerrit.ovirt.org/ovirt-engine -vvv Cloning into 'ovirt-engine'... Looking up gerrit.ovirt.org ... done. Connecting to gerrit.ovirt.org (port 9418) ... 107.22.212.69 done. and then hangs ``` ``` git clone ssh://pkesavap@gerrit.ovirt.org:29418/ovirt-engine.git Cloning into 'ovirt-engine'... ``` Regards, Prajith

2 1