[ovirt-devel] Re: Issue with engine-setup on master

On Tue, Jul 31, 2018 at 5:04 PM, Greg Sheremeta wrote: > Scott noticed while using my ansible dev env setup role that some packages > changed names. Looks like there are py2 and py3 versions. I had assumed > that was from this work -- is that correct? Since this work brings much > instability for

[ovirt-devel] Re: Issue with engine-setup on master

Thanks that helped On Tue, Jul 31, 2018 at 3:43 AM, Yedidyah Bar David wrote: > On Mon, Jul 30, 2018 at 9:50 PM, Ravi Shankar Nori > wrote: > > Should mention that I am on Fedora 28 > > > > On Mon, Jul 30, 2018 at 2:08 PM, Ravi Shankar Nori > wrote: > >> > >> Hi, > >> > >> I pulled the latest

[ovirt-devel] Extended DPDK support in oVirt[0]

Hi, oVirt support for DPDK was introduced in 2017[1], and is now enhanced in terms of deployment via Ansible[2] and usage via OVN. Compatible hosts and NICs can now be easily configured to use userspace drivers, while usage is enhanced via OVN, allowing for both increased performance and SDN usab

[ovirt-devel] Lago oVirt plugin v0.45 Release Announcement

Hi All, On behalf of the Lago team, I'm pleased to announce Lago oVirt plugin v0.45 is available! For a detailed release announcement, please refer to our Github page at: https://github.com/lago-project/lago-ost-plugin/releases/tag/0.45 Resources == Docs: http://lago-ost-plugin.readthedo

[ovirt-devel] Re: oVirt Dashboard issues

YANIV LAVI SENIOR TECHNICAL PRODUCT MANAGER Red Hat Israel Ltd. 34 Jerusalem Road, Building A, 1st floor Ra'anana, Israel 4350109 yl...@redhat.comT: +972-9-7692306 /8272306 F: +972-9-7692223 IM: ylavi TRIED. TESTED. TRUSTED.

[ovirt-devel] Re: oVirt Dashboard issues

On Tue, Jul 31, 2018 at 4:43 PM, Greg Sheremeta wrote: > On Tue, Jul 31, 2018 at 5:47 AM Liz Blanchard wrote: > >> >> >> On Sun, Jul 29, 2018 at 11:36 AM, Nir Soffer wrote: >> >>> On Fri, Jul 27, 2018 at 6:13 PM Vojtech Szocs wrote: >>> > * Cluster cube shows "1 cluster" but also "N/A" ev

[ovirt-devel] Re: Issue with engine-setup on master

Scott noticed while using my ansible dev env setup role that some packages changed names. Looks like there are py2 and py3 versions. I had assumed that was from this work -- is that correct? Since this work brings much instability for developers, it's important to communicate this stuff before it b

[ovirt-devel] Re: oVirt Dashboard issues

On Tue, Jul 31, 2018 at 5:47 AM Liz Blanchard wrote: > > > On Sun, Jul 29, 2018 at 11:36 AM, Nir Soffer wrote: > >> On Fri, Jul 27, 2018 at 6:13 PM Vojtech Szocs wrote: >> >>> > * Cluster cube shows "1 cluster" but also "N/A" even when my cluster >>> is up with 2 machines (with DNS names). >>>

[ovirt-devel] Re: [EXTERNAL] Re: Re: Image Transfer mechanism queries/API support

Hi Navin, I will tentatively schedule a weekly call for every Thursday from 10:00 to 10:30 AM (or up to 11:00 if required). Would this slot work for Veritas? I will confirm the time with the rest of the Red Hat team as well and make changes accordingly. Best, Pavan. On Mon, Jul 30, 2018, 8:56 P

[ovirt-devel] Re: [EXTERNAL] Re: Re: Image Transfer mechanism queries/API support

Hi Pavan and all: We have committed the RHV support for next release of NetBackup. It would help if we can have a weekly/bi weekly call for next 2 months. If there are no topics then we can cancel the call. Please let us know if this is fine and we can send a calendar invite. + Renee Thanks

[ovirt-devel] Re: oVirt Dashboard issues

On Sun, Jul 29, 2018 at 11:36 AM, Nir Soffer wrote: > On Fri, Jul 27, 2018 at 6:13 PM Vojtech Szocs wrote: > >> > * Cluster cube shows "1 cluster" but also "N/A" even when my cluster is >> up with 2 machines (with DNS names). >> >> The "N/A" text shown in Cluster status card simply means that we

[ovirt-devel] Re: Issue with engine-setup on master

On Mon, Jul 30, 2018 at 9:50 PM, Ravi Shankar Nori wrote: > Should mention that I am on Fedora 28 > > On Mon, Jul 30, 2018 at 2:08 PM, Ravi Shankar Nori wrote: >> >> Hi, >> >> I pulled the latest mater rpms from nightly builds [1] and there seems to >> be a issue running engine-setup. >> >> engin