[ovirt-devel] [ACTION REQUIRED] OpenVSwitch configuration changes

[Sandro Bonazzola]

Hi, we received a patch to ovirt-host-deploy
https://gerrit.ovirt.org/63707 related
to a change in OpenVSwitch configuration between
Red Hat OpenStack Platform 7 or older and Red Hat OpenStack Platform 8 or
newer.

- We need to ensure to catch these changes in our testing
- We need to ensure oVirt host deploy still works with Red Hat OpenStack
Platform 8 or newer.

Dan, can you or someone in network team please review the patch?
Thanks again Tony for the patch.


-- 
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com

___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

Re: [ovirt-devel] [ACTION REQUIRED] OpenVSwitch configuration changes

[Yaniv Dary]

We will not be support installation for OSP. This is not part of the
supported feature we added in 4.0.
We will not be testing this or making fixes. We can accept patches and help
with review, but it will be a upstream driven effort and needs to be
backwords compatible.

Yaniv Dary
Technical Product Manager
Red Hat Israel Ltd.
34 Jerusalem Road
Building A, 4th floor
Ra'anana, Israel 4350109

Tel : +972 (9) 7692306
8272306
Email: yd...@redhat.com
IRC : ydary


On Wed, Sep 14, 2016 at 11:11 AM, Nelly Credi  wrote:

> 
>
> On Wed, Sep 14, 2016 at 11:09 AM, Sandro Bonazzola 
> wrote:
>
>> Hi, we received a patch to ovirt-host-deploy
>> https://gerrit.ovirt.org/63707 related to a change in OpenVSwitch
>> configuration between
>> Red Hat OpenStack Platform 7 or older and Red Hat OpenStack Platform 8 or
>> newer.
>>
>> - We need to ensure to catch these changes in our testing
>> - We need to ensure oVirt host deploy still works with Red Hat OpenStack
>> Platform 8 or newer.
>>
>> Dan, can you or someone in network team please review the patch?
>> Thanks again Tony for the patch.
>>
>>
>> --
>> Sandro Bonazzola
>> Better technology. Faster innovation. Powered by community collaboration.
>> See how it works at redhat.com
>> 
>>
>
>
>
> --
> Thanks,
> Nelly
>
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

Re: [ovirt-devel] [ACTION REQUIRED] OpenVSwitch configuration changes

[Sandro Bonazzola]

On Wed, Sep 14, 2016 at 10:13 AM, Yaniv Dary  wrote:

> We will not be support installation for OSP. This is not part of the
> supported feature we added in 4.0.
> We will not be testing this or making fixes. We can accept patches and
> help with review, but it will be a upstream driven effort and needs to be
> backwords compatible.
>

Not sure to understand here. Aren't we supporting openvswitch?




>
> Yaniv Dary
> Technical Product Manager
> Red Hat Israel Ltd.
> 34 Jerusalem Road
> Building A, 4th floor
> Ra'anana, Israel 4350109
>
> Tel : +972 (9) 7692306
> 8272306
> Email: yd...@redhat.com
> IRC : ydary
>
>
> On Wed, Sep 14, 2016 at 11:11 AM, Nelly Credi  wrote:
>
>> 
>>
>> On Wed, Sep 14, 2016 at 11:09 AM, Sandro Bonazzola 
>> wrote:
>>
>>> Hi, we received a patch to ovirt-host-deploy
>>> https://gerrit.ovirt.org/63707 related to a change in OpenVSwitch
>>> configuration between
>>> Red Hat OpenStack Platform 7 or older and Red Hat OpenStack Platform 8
>>> or newer.
>>>
>>> - We need to ensure to catch these changes in our testing
>>> - We need to ensure oVirt host deploy still works with Red Hat OpenStack
>>> Platform 8 or newer.
>>>
>>> Dan, can you or someone in network team please review the patch?
>>> Thanks again Tony for the patch.
>>>
>>>
>>> --
>>> Sandro Bonazzola
>>> Better technology. Faster innovation. Powered by community collaboration.
>>> See how it works at redhat.com
>>> 
>>>
>>
>>
>>
>> --
>> Thanks,
>> Nelly
>>
>
>


-- 
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com

___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

Re: [ovirt-devel] CentOS Virt SIG - aarch 64 and ppc64le support

[Sandro Bonazzola]

On Mon, Aug 29, 2016 at 11:01 AM, Sandro Bonazzola 
wrote:

> Hi,
> within CentOS Virt SIG interest in having ppc64le and aarch64 as supported
> architecture in oVirt has raised.
> Packages from oVirt 4.0.2 has been built for both architectures for
> hypervisor host side.
> You can find the rpms in the cbs repositories waiting to be signed and
> published to mirrors here:
>
> - QEMU and deps: https://cbs.centos.org/repos/virt7-kvm-common-release/
> - oVirt Common deps: https://cbs.centos.org/repos/virt7-ovirt-common-
> release/
> - oVirt 4.0 specific packages: https://cbs.centos.
> org/repos/virt7-ovirt-40-release/
>
> While I'm pretty sure ppc64le will work out of the box I think we're
> missing something on engine side in order to fully support aarch64.
> Michal, Francesco, can you open relevant BZs in order to get aarch64 fully
> supported?
>

Michal, Francesco, any feedback? News?



>
>
> --
> Sandro Bonazzola
> Better technology. Faster innovation. Powered by community collaboration.
> See how it works at redhat.com
>



-- 
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com

___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

Re: [ovirt-devel] CentOS Virt SIG - aarch 64 and ppc64le support

[Martin Polednik]

On 14/09/16 10:42 +0200, Sandro Bonazzola wrote:

On Mon, Aug 29, 2016 at 11:01 AM, Sandro Bonazzola 
wrote:


Hi,
within CentOS Virt SIG interest in having ppc64le and aarch64 as supported
architecture in oVirt has raised.
Packages from oVirt 4.0.2 has been built for both architectures for
hypervisor host side.
You can find the rpms in the cbs repositories waiting to be signed and
published to mirrors here:

- QEMU and deps: https://cbs.centos.org/repos/virt7-kvm-common-release/
- oVirt Common deps: https://cbs.centos.org/repos/virt7-ovirt-common-
release/
- oVirt 4.0 specific packages: https://cbs.centos.
org/repos/virt7-ovirt-40-release/

While I'm pretty sure ppc64le will work out of the box I think we're
missing something on engine side in order to fully support aarch64.
Michal, Francesco, can you open relevant BZs in order to get aarch64 fully
supported?



Michal, Francesco, any feedback? News?


The virt stack is still working on aarch64, I believe it doesn't make
sense to try and start the work from oVirt's POV before CentOS 7.3 is
out.

That being said, I believe aarch64 support is a huge feature that'll
take a while to get to a point where we can start submitting bugs. No
news in that regard.






--
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com





--
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com




___
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

Re: [ovirt-devel] CentOS Virt SIG - aarch 64 and ppc64le support

[Michal Skrivanek]

> On 14 Sep 2016, at 11:06, Martin Polednik  wrote:
> 
> On 14/09/16 10:42 +0200, Sandro Bonazzola wrote:
>> On Mon, Aug 29, 2016 at 11:01 AM, Sandro Bonazzola 
>> wrote:
>> 
>>> Hi,
>>> within CentOS Virt SIG interest in having ppc64le and aarch64 as supported
>>> architecture in oVirt has raised.
>>> Packages from oVirt 4.0.2 has been built for both architectures for
>>> hypervisor host side.
>>> You can find the rpms in the cbs repositories waiting to be signed and
>>> published to mirrors here:
>>> 
>>> - QEMU and deps: https://cbs.centos.org/repos/virt7-kvm-common-release/
>>> - oVirt Common deps: https://cbs.centos.org/repos/virt7-ovirt-common-
>>> release/
>>> - oVirt 4.0 specific packages: https://cbs.centos.
>>> org/repos/virt7-ovirt-40-release/
>>> 
>>> While I'm pretty sure ppc64le will work out of the box I think we're
>>> missing something on engine side in order to fully support aarch64.
>>> Michal, Francesco, can you open relevant BZs in order to get aarch64 fully
>>> supported?

aarch64 is not supported and there’s a long way to get there
it doesn’t hurt building it but people should not expect that it works at all. 
Because it doesn’t.
Having the packages ready is a benefit of course, when we get to that we will 
have all the bricks ready and we can start on making it work. But I can’t say 
when that will happen.

>>> 
>> 
>> Michal, Francesco, any feedback? News?
> 
> The virt stack is still working on aarch64, I believe it doesn't make
> sense to try and start the work from oVirt's POV before CentOS 7.3 is
> out.
> 
> That being said, I believe aarch64 support is a huge feature that'll
> take a while to get to a point where we can start submitting bugs. No
> news in that regard.
> 
>> 
>>> 
>>> 
>>> --
>>> Sandro Bonazzola
>>> Better technology. Faster innovation. Powered by community collaboration.
>>> See how it works at redhat.com
>>> 
>> 
>> 
>> 
>> -- 
>> Sandro Bonazzola
>> Better technology. Faster innovation. Powered by community collaboration.
>> See how it works at redhat.com
>> 
> 
>> ___
>> 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

Re: [ovirt-devel] [ACTION REQUIRED] OpenVSwitch configuration changes

[Nelly Credi]

On Wed, Sep 14, 2016 at 11:09 AM, Sandro Bonazzola 
wrote:

> Hi, we received a patch to ovirt-host-deploy
> https://gerrit.ovirt.org/63707 related to a change in OpenVSwitch
> configuration between
> Red Hat OpenStack Platform 7 or older and Red Hat OpenStack Platform 8 or
> newer.
>
> - We need to ensure to catch these changes in our testing
> - We need to ensure oVirt host deploy still works with Red Hat OpenStack
> Platform 8 or newer.
>
> Dan, can you or someone in network team please review the patch?
> Thanks again Tony for the patch.
>
>
> --
> Sandro Bonazzola
> Better technology. Faster innovation. Powered by community collaboration.
> See how it works at redhat.com
> 
>



-- 
Thanks,
Nelly
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

Re: [ovirt-devel] [ACTION REQUIRED] OpenVSwitch configuration changes

[Dan Kenigsberg]

On Wed, Sep 14, 2016 at 10:23:29AM +0200, Sandro Bonazzola wrote:
> On Wed, Sep 14, 2016 at 10:13 AM, Yaniv Dary  wrote:
> 
> > We will not be support installation for OSP. This is not part of the
> > supported feature we added in 4.0.
> > We will not be testing this or making fixes. We can accept patches and
> > help with review, but it will be a upstream driven effort and needs to be
> > backwords compatible.
> >
> 
> Not sure to understand here. Aren't we supporting openvswitch?

1. We would support openvswitch natively (currently not even in tech
preview).

2. We already support Neutron with openvswitch pluging.

We have code for automatically installing and configuring hosts for
usage by [2], but we do not support it nor test it, simply because
chasing after neutron configurables exceeds our capacity.

Nonetheless, we love upstream patches like the
https://gerrit.ovirt.org/#/c/63707/1/src/ovirt_host_deploy/constants.py
coming out of the core development and QE teams.
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

Re: [ovirt-devel] CentOS Virt SIG - aarch 64 and ppc64le support

[Sandro Bonazzola]

On Wed, Sep 14, 2016 at 11:38 AM, Michal Skrivanek 
wrote:

>
> > On 14 Sep 2016, at 11:06, Martin Polednik  wrote:
> >
> > On 14/09/16 10:42 +0200, Sandro Bonazzola wrote:
> >> On Mon, Aug 29, 2016 at 11:01 AM, Sandro Bonazzola  >
> >> wrote:
> >>
> >>> Hi,
> >>> within CentOS Virt SIG interest in having ppc64le and aarch64 as
> supported
> >>> architecture in oVirt has raised.
> >>> Packages from oVirt 4.0.2 has been built for both architectures for
> >>> hypervisor host side.
> >>> You can find the rpms in the cbs repositories waiting to be signed and
> >>> published to mirrors here:
> >>>
> >>> - QEMU and deps: https://cbs.centos.org/repos/
> virt7-kvm-common-release/
> >>> - oVirt Common deps: https://cbs.centos.org/repos/virt7-ovirt-common-
> >>> release/
> >>> - oVirt 4.0 specific packages: https://cbs.centos.
> >>> org/repos/virt7-ovirt-40-release/
> >>>
> >>> While I'm pretty sure ppc64le will work out of the box I think we're
> >>> missing something on engine side in order to fully support aarch64.
> >>> Michal, Francesco, can you open relevant BZs in order to get aarch64
> fully
> >>> supported?
>
> aarch64 is not supported and there’s a long way to get there
> it doesn’t hurt building it but people should not expect that it works at
> all. Because it doesn’t.
> Having the packages ready is a benefit of course, when we get to that we
> will have all the bricks ready and we can start on making it work. But I
> can’t say when that will happen.
>

Ok, I opened a RFE to track it for whenever it will be possible to work on
it.



>
> >>>
> >>
> >> Michal, Francesco, any feedback? News?
> >
> > The virt stack is still working on aarch64, I believe it doesn't make
> > sense to try and start the work from oVirt's POV before CentOS 7.3 is
> > out.
> >
> > That being said, I believe aarch64 support is a huge feature that'll
> > take a while to get to a point where we can start submitting bugs. No
> > news in that regard.
> >
> >>
> >>>
> >>>
> >>> --
> >>> Sandro Bonazzola
> >>> Better technology. Faster innovation. Powered by community
> collaboration.
> >>> See how it works at redhat.com
> >>>
> >>
> >>
> >>
> >> --
> >> Sandro Bonazzola
> >> Better technology. Faster innovation. Powered by community
> collaboration.
> >> See how it works at redhat.com
> >> 
> >
> >> ___
> >> Devel mailing list
> >> Devel@ovirt.org
> >> http://lists.ovirt.org/mailman/listinfo/devel
> >
>
>


-- 
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com

___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

Re: [ovirt-devel] Alternatives to automatically move bugs to MODIFIED

[Sandro Bonazzola]

On Thu, Aug 18, 2016 at 9:45 AM, Eyal Edri  wrote:

>
>
> On Thu, Aug 18, 2016 at 10:38 AM, Michal Skrivanek <
> michal.skriva...@redhat.com> wrote:
>
>>
>> On 18 Aug 2016, at 09:32, Sandro Bonazzola  wrote:
>>
>>
>>
>> On Thu, Aug 18, 2016 at 9:19 AM, Michal Skrivanek <
>> michal.skriva...@redhat.com> wrote:
>>
>>>
>>> On 18 Aug 2016, at 09:09, Sandro Bonazzola  wrote:
>>>
>>>
>>>
>>> On Wed, Aug 17, 2016 at 5:12 PM, Nir Soffer  wrote:
>>>
 On Wed, Aug 17, 2016 at 2:47 PM, Eyal Edri  wrote:
 >
 >
 > On Wed, Aug 17, 2016 at 2:25 PM, Nir Soffer 
 wrote:
 >>
 >> On Wed, Aug 17, 2016 at 1:45 PM, Eyal Edri  wrote:
 >> > I still thinks its a very valuable hook and we are aware of the
 fact it
 >> > has
 >> > bugs,  especially with patches on master branch and 4.0.
 >> >
 >> > Shlomi from the infra team is working on a solution for it as we
 speak
 >> > and
 >> > we hope to have a solution in the next few days,  however it's not
 >> > trival to
 >> > test and requires setting up a staging env and improve loga for the
 >> > hooks
 >> > system.
 >>
 >> How do you plan to solve this?
 >>
 >> Only the owner of the bug knows if the all the required patches are
 merged
 >
 >
 > The authors should use Bug-Url on the main bug and related-to: on
 other
 > patches that are related.

 This is not possible. Many times you need series of patches to fix a
 bug, and
 you the number of patches may change during development. You start with
 one
 patch, and later you find that you need another one, so all of them
 will have
 a bug url.

 Practically, you should expect that all patches in the series will
 have a bug-url.
 If the hook will change the bug incorrectly someone will have to fix
 this, and
 it is very unlikely that a developer will go to clean after the hook.

 >> and backported to the correct repositories.
 >
 >
 > This is done with logic according to the bug target milestone.
 >
 > for e.g - a patch on branch 'ovirt-engine-4.0' was merged to bug
 targeted to
 > ovirt-4.0.2.
 > The hook should check if branch 4.0.2 exists or not, if it exists
 then the
 > bug should NOT move to MODIFIED,
 > since it needs still backporting to ovirt-engine-4.0.2 branch.

 This is too fragile. For example, maybe a 4.0.2 branch is created after
 the patch was merged to 4.0 branch, and the patch will be missing,
 although
 the bug is already set to modified.

 Setting to modified should be done by the owner of the bug, after
 verifying
 that the patches exists in correct branch.

 I'm not suggesting to remove the hook, just disable the feature of
 making
 a bug modified.

>>>
>>> +1. On build day checking that bugs in modified not listed in Bug-Url on
>>> the build branch due to missing backport is a painful experience.
>>>
>>>
>>> it is a tradeoff. It was mentioned before that the other way around we
>>> would be left with too many POSTed bugs which are actually already merged.
>>> The maintainer is typically not the assignee so if you e.g. merge the last
>>> patch on Thursday afternoon it takes some time to gets attention, in the
>>> meantime there is a build which won’t consider that bug.
>>>
>>>
>> The other way around is having a modified bugs which should have been in
>> post being considered in the build, moved to QE, failing QE, move back to
>> assigned.
>> Not sure it's much better.
>>
>>
>> it is when the amount of false positive ON_QA bugs is far less than
>> amount of forgotten bugs
>> I’m not advocating for it, I’m just saying it was pointed out that this
>> was the situation before we introduced the hook.
>> Perhaps with the doc police emails it is no longer a relevant point
>>
>>
> Do we have a list of number of bugs that actually failed ON_QA due to
> this?
>

No I haven't



>
>
>> Thanks,
>> michal
>>
>>
>>
>>
>>
>>>
>>>
>>>
>>>

 Nir

>>>
>>>
>>>
>>> --
>>> Sandro Bonazzola
>>> Better technology. Faster innovation. Powered by community collaboration.
>>> See how it works at redhat.com
>>> ___
>>> Devel mailing list
>>> Devel@ovirt.org
>>> http://lists.ovirt.org/mailman/listinfo/devel
>>>
>>>
>>>
>>
>>
>> --
>> Sandro Bonazzola
>> Better technology. Faster innovation. Powered by community collaboration.
>> See how it works at redhat.com
>>
>>
>>
>> ___
>> Devel mailing list
>> Devel@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/devel
>>
>
>
>
> --
> Eyal Edri
> Associate Manager
> RHV DevOps
> EMEA ENG Virtualization R&D
> Red Hat Israel
>
> phone: +972-9-7692018
> irc: eedri (on #tlv #rhev-dev #rhev-integ)
>



-- 
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com

[ovirt-devel] Integrating oVirt and Gluster geo-replication to provide a DR solution

[Sahina Bose]

Hi all,

Though there are many solutions that integrate with oVirt to provide
disaster recovery for the guest images, these solutions either rely on
backup agents running on guests or third party software and are complicated
to setup

Since oVirt already integrates with glusterfs, we can leverage gluster's
geo-replication feature to mirror contents to a remote/secondary site
periodically for disaster recovery, without the need for additional software

Please review the PR[1] for the feature page outlining the solution and
integration in oVirt.
Comments and feedback welcome.

[1] https://github.com/oVirt/ovirt-site/pull/453

thanks,
sahina
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

Re: [ovirt-devel] [ACTION REQUIRED] OpenVSwitch configuration changes

[Tony James]

On September 14, 2016 at 3:13:41 AM, Yaniv Dary (yd...@redhat.com) wrote:
> We will not be support installation for OSP. This is not part of the
> supported feature we added in 4.0.

In the process of deploying a node/hypervisor ovirt_host_deploy tries
to run the openstack-config command to write the bridge_mappings entry
to the Open vSwitch agent INI file.  This fails without the patch due
to the path change.  Are you saying that this is not supported?  If
that is the case what is the supported process for leveraging an OSP 8
Neutron provider with RHV 4/oVirt 4?  OSP 8 support is explicitly
called out in the RHV 4 release announcement.

> We will not be testing this or making fixes. We can accept patches and help
> with review, but it will be a upstream driven effort and needs to be
> backwords compatible.
>
> Yaniv Dary
> Technical Product Manager
> Red Hat Israel Ltd.
> 34 Jerusalem Road
> Building A, 4th floor
> Ra'anana, Israel 4350109
>
> Tel : +972 (9) 7692306
> 8272306
> Email: yd...@redhat.com
> IRC : ydary
>
>
> On Wed, Sep 14, 2016 at 11:11 AM, Nelly Credi wrote:
>
> >
> >
> > On Wed, Sep 14, 2016 at 11:09 AM, Sandro Bonazzola
> > wrote:
> >
> >> Hi, we received a patch to ovirt-host-deploy
> >> https://gerrit.ovirt.org/63707 related to a change in OpenVSwitch
> >> configuration between
> >> Red Hat OpenStack Platform 7 or older and Red Hat OpenStack Platform 8 or
> >> newer.
> >>
> >> - We need to ensure to catch these changes in our testing
> >> - We need to ensure oVirt host deploy still works with Red Hat OpenStack
> >> Platform 8 or newer.
> >>
> >> Dan, can you or someone in network team please review the patch?
> >> Thanks again Tony for the patch.
> >>
> >>
> >> --
> >> Sandro Bonazzola
> >> Better technology. Faster innovation. Powered by community collaboration.
> >> See how it works at redhat.com
> >>
> >>
> >
> >
> >
> > --
> > Thanks,
> > Nelly
> >
>
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

Re: [ovirt-devel] [ACTION REQUIRED] OpenVSwitch configuration changes

[Yaniv Dary]

Yaniv Dary
Technical Product Manager
Red Hat Israel Ltd.
34 Jerusalem Road
Building A, 4th floor
Ra'anana, Israel 4350109

Tel : +972 (9) 7692306
8272306
Email: yd...@redhat.com
IRC : ydary


On Wed, Sep 14, 2016 at 4:36 PM, Tony James  wrote:

> On September 14, 2016 at 3:13:41 AM, Yaniv Dary (yd...@redhat.com) wrote:
> > We will not be support installation for OSP. This is not part of the
> > supported feature we added in 4.0.
>
> In the process of deploying a node/hypervisor ovirt_host_deploy tries
> to run the openstack-config command to write the bridge_mappings entry
> to the Open vSwitch agent INI file.  This fails without the patch due
> to the path change.  Are you saying that this is not supported?  If
> that is the case what is the supported process for leveraging an OSP 8
> Neutron provider with RHV 4/oVirt 4?  OSP 8 support is explicitly
> called out in the RHV 4 release announcement.
>

We expect the Neutron agent to be configured either in provision time prior
to add host or manual configuration.
We can't supply a installer for OSP. Please fill free to open a RFE to
support this via director.


>
> > We will not be testing this or making fixes. We can accept patches and
> help
> > with review, but it will be a upstream driven effort and needs to be
> > backwords compatible.
> >
> > Yaniv Dary
> > Technical Product Manager
> > Red Hat Israel Ltd.
> > 34 Jerusalem Road
> > Building A, 4th floor
> > Ra'anana, Israel 4350109
> >
> > Tel : +972 (9) 7692306
> > 8272306
> > Email: yd...@redhat.com
> > IRC : ydary
> >
> >
> > On Wed, Sep 14, 2016 at 11:11 AM, Nelly Credi wrote:
> >
> > >
> > >
> > > On Wed, Sep 14, 2016 at 11:09 AM, Sandro Bonazzola
> > > wrote:
> > >
> > >> Hi, we received a patch to ovirt-host-deploy
> > >> https://gerrit.ovirt.org/63707 related to a change in OpenVSwitch
> > >> configuration between
> > >> Red Hat OpenStack Platform 7 or older and Red Hat OpenStack Platform
> 8 or
> > >> newer.
> > >>
> > >> - We need to ensure to catch these changes in our testing
> > >> - We need to ensure oVirt host deploy still works with Red Hat
> OpenStack
> > >> Platform 8 or newer.
> > >>
> > >> Dan, can you or someone in network team please review the patch?
> > >> Thanks again Tony for the patch.
> > >>
> > >>
> > >> --
> > >> Sandro Bonazzola
> > >> Better technology. Faster innovation. Powered by community
> collaboration.
> > >> See how it works at redhat.com
> > >>
> > >>
> > >
> > >
> > >
> > > --
> > > Thanks,
> > > Nelly
> > >
> >
>
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

Re: [ovirt-devel] [ACTION REQUIRED] OpenVSwitch configuration changes

[Tony James]

On September 14, 2016 at 8:40:09 AM, Yaniv Dary (yd...@redhat.com) wrote:
> Yaniv Dary
> Technical Product Manager
> Red Hat Israel Ltd.
> 34 Jerusalem Road
> Building A, 4th floor
> Ra'anana, Israel 4350109
>
> Tel : +972 (9) 7692306
> 8272306
> Email: yd...@redhat.com
> IRC : ydary
>
>
> On Wed, Sep 14, 2016 at 4:36 PM, Tony James wrote:
>
> > On September 14, 2016 at 3:13:41 AM, Yaniv Dary (yd...@redhat.com) wrote:
> > > We will not be support installation for OSP. This is not part of the
> > > supported feature we added in 4.0.
> >
> > In the process of deploying a node/hypervisor ovirt_host_deploy tries
> > to run the openstack-config command to write the bridge_mappings entry
> > to the Open vSwitch agent INI file. This fails without the patch due
> > to the path change. Are you saying that this is not supported? If
> > that is the case what is the supported process for leveraging an OSP 8
> > Neutron provider with RHV 4/oVirt 4? OSP 8 support is explicitly
> > called out in the RHV 4 release announcement.
> >
>
> We expect the Neutron agent to be configured either in provision time prior
> to add host or manual configuration.
> We can't supply a installer for OSP. Please fill free to open a RFE to
> support this via director.

I understand installing OSP is outside the scope of support and that
the Neutron Open vSwitch agent configuration needs to be performed
manually but adding a node/host via RHV-M/ovirt-engine fails because
part of the ovirt_host_deploy process is to touch the agent INI file.
Are you saying the Neutron external provider should not be selected on
the add host screen?

>
>
> >
> > > We will not be testing this or making fixes. We can accept patches and
> > help
> > > with review, but it will be a upstream driven effort and needs to be
> > > backwords compatible.
> > >
> > > Yaniv Dary
> > > Technical Product Manager
> > > Red Hat Israel Ltd.
> > > 34 Jerusalem Road
> > > Building A, 4th floor
> > > Ra'anana, Israel 4350109
> > >
> > > Tel : +972 (9) 7692306
> > > 8272306
> > > Email: yd...@redhat.com
> > > IRC : ydary
> > >
> > >
> > > On Wed, Sep 14, 2016 at 11:11 AM, Nelly Credi wrote:
> > >
> > > >
> > > >
> > > > On Wed, Sep 14, 2016 at 11:09 AM, Sandro Bonazzola
> > > > wrote:
> > > >
> > > >> Hi, we received a patch to ovirt-host-deploy
> > > >> https://gerrit.ovirt.org/63707 related to a change in OpenVSwitch
> > > >> configuration between
> > > >> Red Hat OpenStack Platform 7 or older and Red Hat OpenStack Platform
> > 8 or
> > > >> newer.
> > > >>
> > > >> - We need to ensure to catch these changes in our testing
> > > >> - We need to ensure oVirt host deploy still works with Red Hat
> > OpenStack
> > > >> Platform 8 or newer.
> > > >>
> > > >> Dan, can you or someone in network team please review the patch?
> > > >> Thanks again Tony for the patch.
> > > >>
> > > >>
> > > >> --
> > > >> Sandro Bonazzola
> > > >> Better technology. Faster innovation. Powered by community
> > collaboration.
> > > >> See how it works at redhat.com
> > > >>
> > > >>
> > > >
> > > >
> > > >
> > > > --
> > > > Thanks,
> > > > Nelly
> > > >
> > >
> >
>
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

Re: [ovirt-devel] [ACTION REQUIRED] OpenVSwitch configuration changes

[Yaniv Dary]

It is not run if you don't choose to deploy external provider on the host
add dialog.
It won't do that if you don't choose it.

Yaniv Dary
Technical Product Manager
Red Hat Israel Ltd.
34 Jerusalem Road
Building A, 4th floor
Ra'anana, Israel 4350109

Tel : +972 (9) 7692306
8272306
Email: yd...@redhat.com
IRC : ydary


On Wed, Sep 14, 2016 at 4:44 PM, Tony James  wrote:

> On September 14, 2016 at 8:40:09 AM, Yaniv Dary (yd...@redhat.com) wrote:
> > Yaniv Dary
> > Technical Product Manager
> > Red Hat Israel Ltd.
> > 34 Jerusalem Road
> > Building A, 4th floor
> > Ra'anana, Israel 4350109
> >
> > Tel : +972 (9) 7692306
> > 8272306
> > Email: yd...@redhat.com
> > IRC : ydary
> >
> >
> > On Wed, Sep 14, 2016 at 4:36 PM, Tony James wrote:
> >
> > > On September 14, 2016 at 3:13:41 AM, Yaniv Dary (yd...@redhat.com)
> wrote:
> > > > We will not be support installation for OSP. This is not part of the
> > > > supported feature we added in 4.0.
> > >
> > > In the process of deploying a node/hypervisor ovirt_host_deploy tries
> > > to run the openstack-config command to write the bridge_mappings entry
> > > to the Open vSwitch agent INI file. This fails without the patch due
> > > to the path change. Are you saying that this is not supported? If
> > > that is the case what is the supported process for leveraging an OSP 8
> > > Neutron provider with RHV 4/oVirt 4? OSP 8 support is explicitly
> > > called out in the RHV 4 release announcement.
> > >
> >
> > We expect the Neutron agent to be configured either in provision time
> prior
> > to add host or manual configuration.
> > We can't supply a installer for OSP. Please fill free to open a RFE to
> > support this via director.
>
> I understand installing OSP is outside the scope of support and that
> the Neutron Open vSwitch agent configuration needs to be performed
> manually but adding a node/host via RHV-M/ovirt-engine fails because
> part of the ovirt_host_deploy process is to touch the agent INI file.
> Are you saying the Neutron external provider should not be selected on
> the add host screen?
>
> >
> >
> > >
> > > > We will not be testing this or making fixes. We can accept patches
> and
> > > help
> > > > with review, but it will be a upstream driven effort and needs to be
> > > > backwords compatible.
> > > >
> > > > Yaniv Dary
> > > > Technical Product Manager
> > > > Red Hat Israel Ltd.
> > > > 34 Jerusalem Road
> > > > Building A, 4th floor
> > > > Ra'anana, Israel 4350109
> > > >
> > > > Tel : +972 (9) 7692306
> > > > 8272306
> > > > Email: yd...@redhat.com
> > > > IRC : ydary
> > > >
> > > >
> > > > On Wed, Sep 14, 2016 at 11:11 AM, Nelly Credi wrote:
> > > >
> > > > >
> > > > >
> > > > > On Wed, Sep 14, 2016 at 11:09 AM, Sandro Bonazzola
> > > > > wrote:
> > > > >
> > > > >> Hi, we received a patch to ovirt-host-deploy
> > > > >> https://gerrit.ovirt.org/63707 related to a change in OpenVSwitch
> > > > >> configuration between
> > > > >> Red Hat OpenStack Platform 7 or older and Red Hat OpenStack
> Platform
> > > 8 or
> > > > >> newer.
> > > > >>
> > > > >> - We need to ensure to catch these changes in our testing
> > > > >> - We need to ensure oVirt host deploy still works with Red Hat
> > > OpenStack
> > > > >> Platform 8 or newer.
> > > > >>
> > > > >> Dan, can you or someone in network team please review the patch?
> > > > >> Thanks again Tony for the patch.
> > > > >>
> > > > >>
> > > > >> --
> > > > >> Sandro Bonazzola
> > > > >> Better technology. Faster innovation. Powered by community
> > > collaboration.
> > > > >> See how it works at redhat.com
> > > > >>
> > > > >>
> > > > >
> > > > >
> > > > >
> > > > > --
> > > > > Thanks,
> > > > > Nelly
> > > > >
> > > >
> > >
> >
>
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

Re: [ovirt-devel] [ACTION REQUIRED] OpenVSwitch configuration changes

[Tony James]

On September 14, 2016 at 8:57:14 AM, Yaniv Dary (yd...@redhat.com) wrote:
> It is not run if you don't choose to deploy external provider on the host
> add dialog.
> It won't do that if you don't choose it.

True, thanks for clarifying. Why do we provide the option if using it
is not supported?  Will this be removed in a future release?

Basically the process of configuring the Neutron provider is:

1. Add the provider to RHV-M/ovirt-engine
2. Add a host without selecting the Neutron provider
3. Manually install and configure the Neutron Open vSwitch agent on the host

Am I correct that this is the supported approach?

>
> Yaniv Dary
> Technical Product Manager
> Red Hat Israel Ltd.
> 34 Jerusalem Road
> Building A, 4th floor
> Ra'anana, Israel 4350109
>
> Tel : +972 (9) 7692306
> 8272306
> Email: yd...@redhat.com
> IRC : ydary
>
>
> On Wed, Sep 14, 2016 at 4:44 PM, Tony James wrote:
>
> > On September 14, 2016 at 8:40:09 AM, Yaniv Dary (yd...@redhat.com) wrote:
> > > Yaniv Dary
> > > Technical Product Manager
> > > Red Hat Israel Ltd.
> > > 34 Jerusalem Road
> > > Building A, 4th floor
> > > Ra'anana, Israel 4350109
> > >
> > > Tel : +972 (9) 7692306
> > > 8272306
> > > Email: yd...@redhat.com
> > > IRC : ydary
> > >
> > >
> > > On Wed, Sep 14, 2016 at 4:36 PM, Tony James wrote:
> > >
> > > > On September 14, 2016 at 3:13:41 AM, Yaniv Dary (yd...@redhat.com)
> > wrote:
> > > > > We will not be support installation for OSP. This is not part of the
> > > > > supported feature we added in 4.0.
> > > >
> > > > In the process of deploying a node/hypervisor ovirt_host_deploy tries
> > > > to run the openstack-config command to write the bridge_mappings entry
> > > > to the Open vSwitch agent INI file. This fails without the patch due
> > > > to the path change. Are you saying that this is not supported? If
> > > > that is the case what is the supported process for leveraging an OSP 8
> > > > Neutron provider with RHV 4/oVirt 4? OSP 8 support is explicitly
> > > > called out in the RHV 4 release announcement.
> > > >
> > >
> > > We expect the Neutron agent to be configured either in provision time
> > prior
> > > to add host or manual configuration.
> > > We can't supply a installer for OSP. Please fill free to open a RFE to
> > > support this via director.
> >
> > I understand installing OSP is outside the scope of support and that
> > the Neutron Open vSwitch agent configuration needs to be performed
> > manually but adding a node/host via RHV-M/ovirt-engine fails because
> > part of the ovirt_host_deploy process is to touch the agent INI file.
> > Are you saying the Neutron external provider should not be selected on
> > the add host screen?
> >
> > >
> > >
> > > >
> > > > > We will not be testing this or making fixes. We can accept patches
> > and
> > > > help
> > > > > with review, but it will be a upstream driven effort and needs to be
> > > > > backwords compatible.
> > > > >
> > > > > Yaniv Dary
> > > > > Technical Product Manager
> > > > > Red Hat Israel Ltd.
> > > > > 34 Jerusalem Road
> > > > > Building A, 4th floor
> > > > > Ra'anana, Israel 4350109
> > > > >
> > > > > Tel : +972 (9) 7692306
> > > > > 8272306
> > > > > Email: yd...@redhat.com
> > > > > IRC : ydary
> > > > >
> > > > >
> > > > > On Wed, Sep 14, 2016 at 11:11 AM, Nelly Credi wrote:
> > > > >
> > > > > >
> > > > > >
> > > > > > On Wed, Sep 14, 2016 at 11:09 AM, Sandro Bonazzola
> > > > > > wrote:
> > > > > >
> > > > > >> Hi, we received a patch to ovirt-host-deploy
> > > > > >> https://gerrit.ovirt.org/63707 related to a change in OpenVSwitch
> > > > > >> configuration between
> > > > > >> Red Hat OpenStack Platform 7 or older and Red Hat OpenStack
> > Platform
> > > > 8 or
> > > > > >> newer.
> > > > > >>
> > > > > >> - We need to ensure to catch these changes in our testing
> > > > > >> - We need to ensure oVirt host deploy still works with Red Hat
> > > > OpenStack
> > > > > >> Platform 8 or newer.
> > > > > >>
> > > > > >> Dan, can you or someone in network team please review the patch?
> > > > > >> Thanks again Tony for the patch.
> > > > > >>
> > > > > >>
> > > > > >> --
> > > > > >> Sandro Bonazzola
> > > > > >> Better technology. Faster innovation. Powered by community
> > > > collaboration.
> > > > > >> See how it works at redhat.com
> > > > > >>
> > > > > >>
> > > > > >
> > > > > >
> > > > > >
> > > > > > --
> > > > > > Thanks,
> > > > > > Nelly
> > > > > >
> > > > >
> > > >
> > >
> >
>
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

Re: [ovirt-devel] [ACTION REQUIRED] OpenVSwitch configuration changes

[Yaniv Dary]

Yaniv Dary
Technical Product Manager
Red Hat Israel Ltd.
34 Jerusalem Road
Building A, 4th floor
Ra'anana, Israel 4350109

Tel : +972 (9) 7692306
8272306
Email: yd...@redhat.com
IRC : ydary


On Wed, Sep 14, 2016 at 5:03 PM, Tony James  wrote:

> On September 14, 2016 at 8:57:14 AM, Yaniv Dary (yd...@redhat.com) wrote:
> > It is not run if you don't choose to deploy external provider on the host
> > add dialog.
> > It won't do that if you don't choose it.
>
> True, thanks for clarifying. Why do we provide the option if using it
> is not supported?  Will this be removed in a future release?
>
> Basically the process of configuring the Neutron provider is:
>
> 1. Add the provider to RHV-M/ovirt-engine
> 2. Add a host without selecting the Neutron provider
>

We should hide it and I think there is a bug on this.
Meni?


> 3. Manually install and configure the Neutron Open vSwitch agent on the
> host
>

Yes


>
> Am I correct that this is the supported approach?
>
> >
> > Yaniv Dary
> > Technical Product Manager
> > Red Hat Israel Ltd.
> > 34 Jerusalem Road
> > Building A, 4th floor
> > Ra'anana, Israel 4350109
> >
> > Tel : +972 (9) 7692306
> > 8272306
> > Email: yd...@redhat.com
> > IRC : ydary
> >
> >
> > On Wed, Sep 14, 2016 at 4:44 PM, Tony James wrote:
> >
> > > On September 14, 2016 at 8:40:09 AM, Yaniv Dary (yd...@redhat.com)
> wrote:
> > > > Yaniv Dary
> > > > Technical Product Manager
> > > > Red Hat Israel Ltd.
> > > > 34 Jerusalem Road
> > > > Building A, 4th floor
> > > > Ra'anana, Israel 4350109
> > > >
> > > > Tel : +972 (9) 7692306
> > > > 8272306
> > > > Email: yd...@redhat.com
> > > > IRC : ydary
> > > >
> > > >
> > > > On Wed, Sep 14, 2016 at 4:36 PM, Tony James wrote:
> > > >
> > > > > On September 14, 2016 at 3:13:41 AM, Yaniv Dary (yd...@redhat.com)
> > > wrote:
> > > > > > We will not be support installation for OSP. This is not part of
> the
> > > > > > supported feature we added in 4.0.
> > > > >
> > > > > In the process of deploying a node/hypervisor ovirt_host_deploy
> tries
> > > > > to run the openstack-config command to write the bridge_mappings
> entry
> > > > > to the Open vSwitch agent INI file. This fails without the patch
> due
> > > > > to the path change. Are you saying that this is not supported? If
> > > > > that is the case what is the supported process for leveraging an
> OSP 8
> > > > > Neutron provider with RHV 4/oVirt 4? OSP 8 support is explicitly
> > > > > called out in the RHV 4 release announcement.
> > > > >
> > > >
> > > > We expect the Neutron agent to be configured either in provision time
> > > prior
> > > > to add host or manual configuration.
> > > > We can't supply a installer for OSP. Please fill free to open a RFE
> to
> > > > support this via director.
> > >
> > > I understand installing OSP is outside the scope of support and that
> > > the Neutron Open vSwitch agent configuration needs to be performed
> > > manually but adding a node/host via RHV-M/ovirt-engine fails because
> > > part of the ovirt_host_deploy process is to touch the agent INI file.
> > > Are you saying the Neutron external provider should not be selected on
> > > the add host screen?
> > >
> > > >
> > > >
> > > > >
> > > > > > We will not be testing this or making fixes. We can accept
> patches
> > > and
> > > > > help
> > > > > > with review, but it will be a upstream driven effort and needs
> to be
> > > > > > backwords compatible.
> > > > > >
> > > > > > Yaniv Dary
> > > > > > Technical Product Manager
> > > > > > Red Hat Israel Ltd.
> > > > > > 34 Jerusalem Road
> > > > > > Building A, 4th floor
> > > > > > Ra'anana, Israel 4350109
> > > > > >
> > > > > > Tel : +972 (9) 7692306
> > > > > > 8272306
> > > > > > Email: yd...@redhat.com
> > > > > > IRC : ydary
> > > > > >
> > > > > >
> > > > > > On Wed, Sep 14, 2016 at 11:11 AM, Nelly Credi wrote:
> > > > > >
> > > > > > >
> > > > > > >
> > > > > > > On Wed, Sep 14, 2016 at 11:09 AM, Sandro Bonazzola
> > > > > > > wrote:
> > > > > > >
> > > > > > >> Hi, we received a patch to ovirt-host-deploy
> > > > > > >> https://gerrit.ovirt.org/63707 related to a change in
> OpenVSwitch
> > > > > > >> configuration between
> > > > > > >> Red Hat OpenStack Platform 7 or older and Red Hat OpenStack
> > > Platform
> > > > > 8 or
> > > > > > >> newer.
> > > > > > >>
> > > > > > >> - We need to ensure to catch these changes in our testing
> > > > > > >> - We need to ensure oVirt host deploy still works with Red Hat
> > > > > OpenStack
> > > > > > >> Platform 8 or newer.
> > > > > > >>
> > > > > > >> Dan, can you or someone in network team please review the
> patch?
> > > > > > >> Thanks again Tony for the patch.
> > > > > > >>
> > > > > > >>
> > > > > > >> --
> > > > > > >> Sandro Bonazzola
> > > > > > >> Better technology. Faster innovation. Powered by community
> > > > > collaboration.
> > > > > > >> See how it works at redhat.com
> > > > > > >>
> > > > > > >>
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > --
> > > > > > > Thanks,

[ovirt-devel] [VDSM] build-artifacts failing on master

[Nir Soffer]

The build-artifacts job is failing on master now with this error:

19:09:23 Error: NOSE is too old, please install NOSE 1.3.7 or later
19:09:23 make[1]: *** [tests] Error 1
19:09:23 make[1]: Leaving directory
`/home/jenkins/workspace/vdsm_master_build-artifacts-el7-x86_64/vdsm/rpmbuild/BUILD/vdsm-4.18.999'
19:09:23 error: Bad exit status from /var/tmp/rpm-tmp.LQXOfm (%check)
19:09:23
19:09:23
19:09:23 RPM build errors:
19:09:23 Bad exit status from /var/tmp/rpm-tmp.LQXOfm (%check)

Looks like this patch is the cause:

commit 4e729ddd2b243d0953e2de5d31c42fc59859bf23
Author: Edward Haas 
Date:   Sun Sep 11 14:10:01 2016 +0300

build tests: Require NOSE 1.3.7 and up for running tests

On RHEL7/Centos7 the provided NOSE version is 1.3.0.
CI runs the tests with 1.3.7.

To be consistent and avoid different behaviours, assure that the tests
are running with a minimum nose version of 1.3.7.

Specifically, between 1.3.0 and 1.3.7 a bug has been resolved regarding
test labeling and its support with test class inheritance.

Change-Id: If79d8624cee1c14a21840e4a08000fc33abb58e5
Signed-off-by: Edward Haas 
Reviewed-on: https://gerrit.ovirt.org/63638
Continuous-Integration: Jenkins CI
Reviewed-by: Petr Horáček 
Reviewed-by: Irit Goihman 
Reviewed-by: Yaniv Bronhaim 
Reviewed-by: Piotr Kliczewski 

I did not check the details, but it seems we need to revert this patch.

Please check and fix.

Cheers,
Nir
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

Re: [ovirt-devel] [VDSM] build-artifacts failing on master

[Eyal Edri]

Its actually a good question to know if standard CI supports versions of
RPMs.
Barak - do you know if we can specify in build-artifacts.packages file a
version requirement?

for e.g python-nose >= 1.3.7

On Wed, Sep 14, 2016 at 10:21 PM, Nir Soffer  wrote:

> The build-artifacts job is failing on master now with this error:
>
> 19:09:23 Error: NOSE is too old, please install NOSE 1.3.7 or later
> 19:09:23 make[1]: *** [tests] Error 1
> 19:09:23 make[1]: Leaving directory
> `/home/jenkins/workspace/vdsm_master_build-artifacts-el7-
> x86_64/vdsm/rpmbuild/BUILD/vdsm-4.18.999'
> 19:09:23 error: Bad exit status from /var/tmp/rpm-tmp.LQXOfm (%check)
> 19:09:23
> 19:09:23
> 19:09:23 RPM build errors:
> 19:09:23 Bad exit status from /var/tmp/rpm-tmp.LQXOfm (%check)
>
> Looks like this patch is the cause:
>
> commit 4e729ddd2b243d0953e2de5d31c42fc59859bf23
> Author: Edward Haas 
> Date:   Sun Sep 11 14:10:01 2016 +0300
>
> build tests: Require NOSE 1.3.7 and up for running tests
>
> On RHEL7/Centos7 the provided NOSE version is 1.3.0.
> CI runs the tests with 1.3.7.
>
> To be consistent and avoid different behaviours, assure that the tests
> are running with a minimum nose version of 1.3.7.
>
> Specifically, between 1.3.0 and 1.3.7 a bug has been resolved regarding
> test labeling and its support with test class inheritance.
>
> Change-Id: If79d8624cee1c14a21840e4a08000fc33abb58e5
> Signed-off-by: Edward Haas 
> Reviewed-on: https://gerrit.ovirt.org/63638
> Continuous-Integration: Jenkins CI
> Reviewed-by: Petr Horáček 
> Reviewed-by: Irit Goihman 
> Reviewed-by: Yaniv Bronhaim 
> Reviewed-by: Piotr Kliczewski 
>
> I did not check the details, but it seems we need to revert this patch.
>
> Please check and fix.
>
> Cheers,
> Nir
> ___
> Infra mailing list
> in...@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/infra
>
>
>


-- 
Eyal Edri
Associate Manager
RHV DevOps
EMEA ENG Virtualization R&D
Red Hat Israel

phone: +972-9-7692018
irc: eedri (on #tlv #rhev-dev #rhev-integ)
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

Re: [ovirt-devel] [VDSM] build-artifacts failing on master

[Irit Goihman]

I think that what's missing in build-artifacts.sh is the following commands
that exist in check-patch.sh:

easy_install pip

pip install -U nose==1.3.7

This should install the right version for nose (that doesn't exist in rhel
yum repos)

On Wed, Sep 14, 2016 at 10:31 PM, Eyal Edri  wrote:

> Its actually a good question to know if standard CI supports versions of
> RPMs.
> Barak - do you know if we can specify in build-artifacts.packages file a
> version requirement?
>
> for e.g python-nose >= 1.3.7
>
> On Wed, Sep 14, 2016 at 10:21 PM, Nir Soffer  wrote:
>
>> The build-artifacts job is failing on master now with this error:
>>
>> 19:09:23 Error: NOSE is too old, please install NOSE 1.3.7 or later
>> 19:09:23 make[1]: *** [tests] Error 1
>> 19:09:23 make[1]: Leaving directory
>> `/home/jenkins/workspace/vdsm_master_build-artifacts-el7-x86
>> _64/vdsm/rpmbuild/BUILD/vdsm-4.18.999'
>> 19:09:23 error: Bad exit status from /var/tmp/rpm-tmp.LQXOfm (%check)
>> 19:09:23
>> 19:09:23
>> 19:09:23 RPM build errors:
>> 19:09:23 Bad exit status from /var/tmp/rpm-tmp.LQXOfm (%check)
>>
>> Looks like this patch is the cause:
>>
>> commit 4e729ddd2b243d0953e2de5d31c42fc59859bf23
>> Author: Edward Haas 
>> Date:   Sun Sep 11 14:10:01 2016 +0300
>>
>> build tests: Require NOSE 1.3.7 and up for running tests
>>
>> On RHEL7/Centos7 the provided NOSE version is 1.3.0.
>> CI runs the tests with 1.3.7.
>>
>> To be consistent and avoid different behaviours, assure that the tests
>> are running with a minimum nose version of 1.3.7.
>>
>> Specifically, between 1.3.0 and 1.3.7 a bug has been resolved
>> regarding
>> test labeling and its support with test class inheritance.
>>
>> Change-Id: If79d8624cee1c14a21840e4a08000fc33abb58e5
>> Signed-off-by: Edward Haas 
>> Reviewed-on: https://gerrit.ovirt.org/63638
>> Continuous-Integration: Jenkins CI
>> Reviewed-by: Petr Horáček 
>> Reviewed-by: Irit Goihman 
>> Reviewed-by: Yaniv Bronhaim 
>> Reviewed-by: Piotr Kliczewski 
>>
>> I did not check the details, but it seems we need to revert this patch.
>>
>> Please check and fix.
>>
>> Cheers,
>> Nir
>> ___
>> Infra mailing list
>> in...@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/infra
>>
>>
>>
>
>
> --
> Eyal Edri
> Associate Manager
> RHV DevOps
> EMEA ENG Virtualization R&D
> Red Hat Israel
>
> phone: +972-9-7692018
> irc: eedri (on #tlv #rhev-dev #rhev-integ)
>
> ___
> Devel mailing list
> Devel@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/devel
>



-- 
Irit Goihman
Software Engineer
Red Hat Israel Ltd.
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

Re: [ovirt-devel] [VDSM] build-artifacts failing on master

[Nir Soffer]

On Wed, Sep 14, 2016 at 10:31 PM, Eyal Edri  wrote:
> Its actually a good question to know if standard CI supports versions of
> RPMs.
> Barak - do you know if we can specify in build-artifacts.packages file a
> version requirement?
>
> for e.g python-nose >= 1.3.7

This can be worse, we build on centos, which may have this version,
but the package may not be available on rhel, failing the build in brew.

Can we do a scratch build in brew?

>
> On Wed, Sep 14, 2016 at 10:21 PM, Nir Soffer  wrote:
>>
>> The build-artifacts job is failing on master now with this error:
>>
>> 19:09:23 Error: NOSE is too old, please install NOSE 1.3.7 or later
>> 19:09:23 make[1]: *** [tests] Error 1
>> 19:09:23 make[1]: Leaving directory
>>
>> `/home/jenkins/workspace/vdsm_master_build-artifacts-el7-x86_64/vdsm/rpmbuild/BUILD/vdsm-4.18.999'
>> 19:09:23 error: Bad exit status from /var/tmp/rpm-tmp.LQXOfm (%check)
>> 19:09:23
>> 19:09:23
>> 19:09:23 RPM build errors:
>> 19:09:23 Bad exit status from /var/tmp/rpm-tmp.LQXOfm (%check)
>>
>> Looks like this patch is the cause:
>>
>> commit 4e729ddd2b243d0953e2de5d31c42fc59859bf23
>> Author: Edward Haas 
>> Date:   Sun Sep 11 14:10:01 2016 +0300
>>
>> build tests: Require NOSE 1.3.7 and up for running tests
>>
>> On RHEL7/Centos7 the provided NOSE version is 1.3.0.
>> CI runs the tests with 1.3.7.
>>
>> To be consistent and avoid different behaviours, assure that the tests
>> are running with a minimum nose version of 1.3.7.
>>
>> Specifically, between 1.3.0 and 1.3.7 a bug has been resolved
>> regarding
>> test labeling and its support with test class inheritance.
>>
>> Change-Id: If79d8624cee1c14a21840e4a08000fc33abb58e5
>> Signed-off-by: Edward Haas 
>> Reviewed-on: https://gerrit.ovirt.org/63638
>> Continuous-Integration: Jenkins CI
>> Reviewed-by: Petr Horáček 
>> Reviewed-by: Irit Goihman 
>> Reviewed-by: Yaniv Bronhaim 
>> Reviewed-by: Piotr Kliczewski 
>>
>> I did not check the details, but it seems we need to revert this patch.
>>
>> Please check and fix.
>>
>> Cheers,
>> Nir
>> ___
>> Infra mailing list
>> in...@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/infra
>>
>>
>
>
>
> --
> Eyal Edri
> Associate Manager
> RHV DevOps
> EMEA ENG Virtualization R&D
> Red Hat Israel
>
> phone: +972-9-7692018
> irc: eedri (on #tlv #rhev-dev #rhev-integ)
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

Re: [ovirt-devel] [VDSM] build-artifacts failing on master

[Nir Soffer]

On Wed, Sep 14, 2016 at 10:40 PM, Irit Goihman  wrote:
> I think that what's missing in build-artifacts.sh is the following commands
> that exist in check-patch.sh:
>
> easy_install pip
> pip install -U nose==1.3.7

We cannot do this in brew/koji, you can use only packages from the distribution
when running make rpm.

>
> This should install the right version for nose (that doesn't exist in rhel
> yum repos)
>
> On Wed, Sep 14, 2016 at 10:31 PM, Eyal Edri  wrote:
>>
>> Its actually a good question to know if standard CI supports versions of
>> RPMs.
>> Barak - do you know if we can specify in build-artifacts.packages file a
>> version requirement?
>>
>> for e.g python-nose >= 1.3.7
>>
>> On Wed, Sep 14, 2016 at 10:21 PM, Nir Soffer  wrote:
>>>
>>> The build-artifacts job is failing on master now with this error:
>>>
>>> 19:09:23 Error: NOSE is too old, please install NOSE 1.3.7 or later
>>> 19:09:23 make[1]: *** [tests] Error 1
>>> 19:09:23 make[1]: Leaving directory
>>>
>>> `/home/jenkins/workspace/vdsm_master_build-artifacts-el7-x86_64/vdsm/rpmbuild/BUILD/vdsm-4.18.999'
>>> 19:09:23 error: Bad exit status from /var/tmp/rpm-tmp.LQXOfm (%check)
>>> 19:09:23
>>> 19:09:23
>>> 19:09:23 RPM build errors:
>>> 19:09:23 Bad exit status from /var/tmp/rpm-tmp.LQXOfm (%check)
>>>
>>> Looks like this patch is the cause:
>>>
>>> commit 4e729ddd2b243d0953e2de5d31c42fc59859bf23
>>> Author: Edward Haas 
>>> Date:   Sun Sep 11 14:10:01 2016 +0300
>>>
>>> build tests: Require NOSE 1.3.7 and up for running tests
>>>
>>> On RHEL7/Centos7 the provided NOSE version is 1.3.0.
>>> CI runs the tests with 1.3.7.
>>>
>>> To be consistent and avoid different behaviours, assure that the
>>> tests
>>> are running with a minimum nose version of 1.3.7.
>>>
>>> Specifically, between 1.3.0 and 1.3.7 a bug has been resolved
>>> regarding
>>> test labeling and its support with test class inheritance.
>>>
>>> Change-Id: If79d8624cee1c14a21840e4a08000fc33abb58e5
>>> Signed-off-by: Edward Haas 
>>> Reviewed-on: https://gerrit.ovirt.org/63638
>>> Continuous-Integration: Jenkins CI
>>> Reviewed-by: Petr Horáček 
>>> Reviewed-by: Irit Goihman 
>>> Reviewed-by: Yaniv Bronhaim 
>>> Reviewed-by: Piotr Kliczewski 
>>>
>>> I did not check the details, but it seems we need to revert this patch.
>>>
>>> Please check and fix.
>>>
>>> Cheers,
>>> Nir
>>> ___
>>> Infra mailing list
>>> in...@ovirt.org
>>> http://lists.ovirt.org/mailman/listinfo/infra
>>>
>>>
>>
>>
>>
>> --
>> Eyal Edri
>> Associate Manager
>> RHV DevOps
>> EMEA ENG Virtualization R&D
>> Red Hat Israel
>>
>> phone: +972-9-7692018
>> irc: eedri (on #tlv #rhev-dev #rhev-integ)
>>
>> ___
>> Devel mailing list
>> Devel@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/devel
>
>
>
>
> --
> Irit Goihman
> Software Engineer
> Red Hat Israel Ltd.
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

Re: [ovirt-devel] [VDSM] build-artifacts failing on master

[Nir Soffer]

On Wed, Sep 14, 2016 at 10:43 PM, Nir Soffer  wrote:
> On Wed, Sep 14, 2016 at 10:40 PM, Irit Goihman  wrote:
>> I think that what's missing in build-artifacts.sh is the following commands
>> that exist in check-patch.sh:
>>
>> easy_install pip
>> pip install -U nose==1.3.7
>
> We cannot do this in brew/koji, you can use only packages from the 
> distribution
> when running make rpm.

The best way to avoid such issues is to remove the "make tests"
from the %check section in the spec.

This allows using latest and greatest development tools which are not available
in brew or koji.

Here is a quick patch, please review:
https://gerrit.ovirt.org/63966

>> This should install the right version for nose (that doesn't exist in rhel
>> yum repos)
>>
>> On Wed, Sep 14, 2016 at 10:31 PM, Eyal Edri  wrote:
>>>
>>> Its actually a good question to know if standard CI supports versions of
>>> RPMs.
>>> Barak - do you know if we can specify in build-artifacts.packages file a
>>> version requirement?
>>>
>>> for e.g python-nose >= 1.3.7
>>>
>>> On Wed, Sep 14, 2016 at 10:21 PM, Nir Soffer  wrote:

 The build-artifacts job is failing on master now with this error:

 19:09:23 Error: NOSE is too old, please install NOSE 1.3.7 or later
 19:09:23 make[1]: *** [tests] Error 1
 19:09:23 make[1]: Leaving directory

 `/home/jenkins/workspace/vdsm_master_build-artifacts-el7-x86_64/vdsm/rpmbuild/BUILD/vdsm-4.18.999'
 19:09:23 error: Bad exit status from /var/tmp/rpm-tmp.LQXOfm (%check)
 19:09:23
 19:09:23
 19:09:23 RPM build errors:
 19:09:23 Bad exit status from /var/tmp/rpm-tmp.LQXOfm (%check)

 Looks like this patch is the cause:

 commit 4e729ddd2b243d0953e2de5d31c42fc59859bf23
 Author: Edward Haas 
 Date:   Sun Sep 11 14:10:01 2016 +0300

 build tests: Require NOSE 1.3.7 and up for running tests

 On RHEL7/Centos7 the provided NOSE version is 1.3.0.
 CI runs the tests with 1.3.7.

 To be consistent and avoid different behaviours, assure that the
 tests
 are running with a minimum nose version of 1.3.7.

 Specifically, between 1.3.0 and 1.3.7 a bug has been resolved
 regarding
 test labeling and its support with test class inheritance.

 Change-Id: If79d8624cee1c14a21840e4a08000fc33abb58e5
 Signed-off-by: Edward Haas 
 Reviewed-on: https://gerrit.ovirt.org/63638
 Continuous-Integration: Jenkins CI
 Reviewed-by: Petr Horáček 
 Reviewed-by: Irit Goihman 
 Reviewed-by: Yaniv Bronhaim 
 Reviewed-by: Piotr Kliczewski 

 I did not check the details, but it seems we need to revert this patch.

 Please check and fix.

 Cheers,
 Nir
 ___
 Infra mailing list
 in...@ovirt.org
 http://lists.ovirt.org/mailman/listinfo/infra


>>>
>>>
>>>
>>> --
>>> Eyal Edri
>>> Associate Manager
>>> RHV DevOps
>>> EMEA ENG Virtualization R&D
>>> Red Hat Israel
>>>
>>> phone: +972-9-7692018
>>> irc: eedri (on #tlv #rhev-dev #rhev-integ)
>>>
>>> ___
>>> Devel mailing list
>>> Devel@ovirt.org
>>> http://lists.ovirt.org/mailman/listinfo/devel
>>
>>
>>
>>
>> --
>> Irit Goihman
>> Software Engineer
>> Red Hat Israel Ltd.
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

[ovirt-devel] [ACTION REQUIRED] VDSM master builf failing on NOSE version check

[Sandro Bonazzola]

*http://jenkins.ovirt.org/job/vdsm_master_build-artifacts-el7-x86_64/836/console
*


*00:05:37.816* make[1]: Entering directory
`/home/jenkins/workspace/vdsm_master_build-artifacts-el7-x86_64/vdsm/rpmbuild/BUILD/vdsm-4.18.999'*00:05:37.817*
Makefile:980: warning: overriding recipe for target
`check-recursive'*00:05:37.818* Makefile:516: warning: ignoring old
recipe for target `check-recursive'*00:05:38.119* Error: NOSE is too
old, please install NOSE 1.3.7 or later*00:05:38.119* make[1]: ***
[tests] Error 1


Is a newer version of nose really needed?
If no: please require a version of nose which is available.
If yes: we can consider shipping nose in CentOS Virt SIG repos since it's
available for OpenStack repos:
http://cbs.centos.org/koji/buildinfo?buildID=10186

Please let me know.

-- 
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com

___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

[ovirt-devel] [ACTION REQUIKRED] vdsm check merged for 4.0 failing on Lago repository sync

[Sandro Bonazzola]

http://jenkins.ovirt.org/job/vdsm_4.0_check-merged-fc23-x86_64/146/console

Please either fix lago to be more reliable when syncing repos or configure
vdsm tests to use the right repos.

Thanks,
-- 
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com

___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel