@Eran,
Please discard my previous comment.
It is not possible do config the vlan because you pass all the PF to the guest.
The you should create the vlan by himself or cloud init.
I am not aware of easy solution for this.
** Changed in: nova
Status: Confirmed => Won't Fix
** Changed in: nova
Status: Won't Fix => Incomplete
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1614092
Title:
SRIOV - PF / VM that assign to PF does not get vlan tag
Status in neutron:
Invalid
Status in OpenStack Compute (nova):
Incomplete
Bug description:
During RFE testing Manage SR-IOV PFs as Neutron ports, I found VM booted with
Neutron port vnic_type direct-physical but it does not get access to DHCP
server.
The problem is that the PF / VM does not get VLAN tag with the internal vlan.
Workaround :
Enter to the VM via console and set vlan interface.
version RHOS 10
python-neutronclient-4.2.1-0.20160721230146.3b1c538.el7ost.noarch
openstack-neutron-common-9.0.0-0.20160726001729.6a23add.el7ost.noarch
python-neutron-9.0.0-0.20160726001729.6a23add.el7ost.noarch
openstack-neutron-fwaas-9.0.0-0.20160720211704.c3e491c.el7ost.noarch
openstack-neutron-metering-agent-9.0.0-0.20160726001729.6a23add.el7ost.noarch
openstack-neutron-openvswitch-9.0.0-0.20160726001729.6a23add.el7ost.noarch
puppet-neutron-9.1.0-0.20160725142451.4061b39.el7ost.noarch
python-neutron-lib-0.2.1-0.20160726025313.405f896.el7ost.noarch
openstack-neutron-ml2-9.0.0-0.20160726001729.6a23add.el7ost.noarch
openstack-neutron-9.0.0-0.20160726001729.6a23add.el7ost.noarch
openstack-neutron-sriov-nic-agent-9.0.0-0.20160726001729.6a23add.el7ost.noarch
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1614092/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
