Re: [openstack-dev] [neutron][nova][stable][sr-iov] Status of physical_device_mappings

2016-03-30 Thread Ihar Hrachyshka
Seems like the explanation below indeed suggests that’s a regression for Mitaka. We’ll track the bug for a backport. I don’t think that we can block the initial Mitaka release for that though. So let’s work on the master fix right now, and target the fix for Mitaka for one of the first minor

Re: [openstack-dev] [neutron][nova][stable][sr-iov] Status of physical_device_mappings

2016-03-29 Thread Vladimir Eremin
Hi jay, There was no ability to setup this configuration WITH Neutron SR-IOV ML2 agent in Liberty. That what you pointed out and you’re totally correct. But in Liberty, you’re not required to use Neutron SR-IOV ML2 agent to get this functionality works. And if you configure only nova-compute

Re: [openstack-dev] [neutron][nova][stable][sr-iov] Status of physical_device_mappings

2016-03-24 Thread Mooney, Sean K
> -Original Message- > From: Jay Pipes [mailto:jaypi...@gmail.com] > Sent: Wednesday, March 23, 2016 8:01 PM > To: openstack-dev@lists.openstack.org > Subject: Re: [openstack-dev] [neutron][nova][stable][sr-iov] Status of > physical_device_mappings > > +tags for

Re: [openstack-dev] [neutron][nova][stable][sr-iov] Status of physical_device_mappings

2016-03-23 Thread Jay Pipes
+tags for stable and nova Hi Vladimir, comments inline. :) On 03/21/2016 05:16 AM, Vladimir Eremin wrote: Hey OpenStackers, I’ve recently found out, that changing of use neutron sriov-agent in Mitaka from optional to required[1] makes a kind of regression. While I understand that it is