Public bug reported:
When you create a VM with sub-ports via the trunk service plugin, the VM
must tag the traffic with the appropriate VLAN. Today there is no
specific VLAN config that's created by Nova (see:
https://cloudinit.readthedocs.io/en/latest/reference/network-config-
format-v2.html#vlans) and an example of this from a VM:
https://paste.opendev.org/show/bUPu5FoEmghimagw47nA/ The expectation is
that a cloud-init config is created to allow for having the VM tag the
traffic out of the box.
** Affects: nova
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/2091185
Title:
When the neutron trunk service plugin is used, nova does not generate
VLAN config in network-data.json
Status in OpenStack Compute (nova):
New
Bug description:
When you create a VM with sub-ports via the trunk service plugin, the
VM must tag the traffic with the appropriate VLAN. Today there is no
specific VLAN config that's created by Nova (see:
https://cloudinit.readthedocs.io/en/latest/reference/network-config-
format-v2.html#vlans) and an example of this from a VM:
https://paste.opendev.org/show/bUPu5FoEmghimagw47nA/ The expectation
is that a cloud-init config is created to allow for having the VM tag
the traffic out of the box.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/2091185/+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
