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: ydary@redhat.com
IRC : ydary
On September 14, 2016 at 3:13:41 AM, Yaniv Dary (ydary@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: ydary@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
> >
>