Re: [openstack-dev] [neutron] Vlan aware VMs or trunking

I think we will probably end up having to support the direct pass through anyway. The reason that landed in the spec is because someone claimed they had switches that couldn't do translation very well. We will just need volunteers to make the changes required on the Neutron side. On Wed, Dec 7,

Re: [openstack-dev] [neutron] Vlan aware VMs or trunking

On Wed, Dec 7, 2016 at 7:34 PM, Kevin Benton wrote: > >It work only when whole switch is aimed by single customer, it will not > work when several customers sharing the same switch. > > Do you know what vendors have this limitation? I know the broadcom > chipsets didn't prevent

Re: [openstack-dev] [neutron] Vlan aware VMs or trunking

>It work only when whole switch is aimed by single customer, it will not work when several customers sharing the same switch. Do you know what vendors have this limitation? I know the broadcom chipsets didn't prevent this (we allowed VLAN rewrites scoped to ports at Big Switch). If it's common to

Re: [openstack-dev] [neutron] Vlan aware VMs or trunking

On Wed, Dec 7, 2016 at 7:12 PM, Kevin Benton wrote: > > > On Wed, Dec 7, 2016 at 8:47 AM, Vasyl Saienko > wrote: > >> @Armando: IMO the spec [0] is not about enablement of Trunks and >> baremetal. This spec is rather about trying to make user request

Re: [openstack-dev] [neutron] Vlan aware VMs or trunking

On Wed, Dec 7, 2016 at 8:47 AM, Vasyl Saienko wrote: > @Armando: IMO the spec [0] is not about enablement of Trunks and > baremetal. This spec is rather about trying to make user request with any > network configuration (number of requested NICs) to be able successfully >

Re: [openstack-dev] [neutron] Vlan aware VMs or trunking

@Armando: IMO the spec [0] is not about enablement of Trunks and baremetal. This spec is rather about trying to make user request with any network configuration (number of requested NICs) to be able successfully deployed on ANY ironic node (even when number of hardware interfaces is less than

Re: [openstack-dev] [neutron] Vlan aware VMs or trunking

Just to be clear, in this case the switches don't support VLAN translation (e.g. [1])? Because that also solves the problem you are running into. This is the preferable path for bare metal because it avoids exposing provider details to users and doesn't tie you to VLANs on the backend. 1.

Re: [openstack-dev] [neutron] Vlan aware VMs or trunking

On 7 December 2016 at 04:02, Vasyl Saienko wrote: > Armando, Kevin, > > Thanks for your comments. > > To be more clear we are trying to use neutron trunks implementation with > baremetal servers (Ironic). Baremetal servers are plugged to Tor (Top of > the Rack) switch.

Re: [openstack-dev] [neutron] Vlan aware VMs or trunking

Armando, Kevin, Thanks for your comments. To be more clear we are trying to use neutron trunks implementation with baremetal servers (Ironic). Baremetal servers are plugged to Tor (Top of the Rack) switch. User images are spawned directly onto hardware. Ironic uses Neutron ML2 drivers to plug

Re: [openstack-dev] [neutron] Vlan aware VMs or trunking

On 6 December 2016 at 08:49, Vasyl Saienko wrote: > Hello Neutron Community, > > > I've found that nice feature vlan-aware-vms was implemented in Newton [0]. > However the usage of this feature for regular users is impossible, unless > I'm missing something. > > As I

Re: [openstack-dev] [neutron] Vlan aware VMs or trunking

The segmentation type of the trunk (how the VM attached to the parent port sees the traffic) has nothing to do with the provider segmentation details (how the traffic will be encapsulated when it leaves the compute node). You're right that a normal user won't know the latter details, but they

[openstack-dev] [neutron] Vlan aware VMs or trunking

Hello Neutron Community, I've found that nice feature vlan-aware-vms was implemented in Newton [0]. However the usage of this feature for regular users is impossible, unless I'm missing something. As I understood correctly it should work in the following way: 1. It is possible to group