Re: [openstack-dev] [Neutron][Magnum] Container + OpenStack Integration

2015-05-21 Thread Antoni Segura Puimedon
OpenStack Development Mailing List (not for usage questions) > *Subject:* Re: [openstack-dev] [Neutron][Magnum] Container + OpenStack > Integration > > Hi, > > Just brainstorming here, but IMHO it would be good to keep it extensible > and not to lock in VLAN as the sole

Re: [openstack-dev] [Neutron][Magnum] Container + OpenStack Integration

2015-05-21 Thread Fox, Kevin M
: [openstack-dev] [Neutron][Magnum] Container + OpenStack Integration Hi, Just brainstorming here, but IMHO it would be good to keep it extensible and not to lock in VLAN as the sole container "VIF" mechanism. For instance, there is the ipvlan [1] technology that was purpose-built to be more a

Re: [openstack-dev] [Neutron][Magnum] Container + OpenStack Integration

2015-05-21 Thread Brenden Blanco
Hi, Just brainstorming here, but IMHO it would be good to keep it extensible and not to lock in VLAN as the sole container "VIF" mechanism. For instance, there is the ipvlan [1] technology that was purpose-built to be more appropriate for container systems. This tech actually comes from some of th

Re: [openstack-dev] [Neutron][Magnum] Container + OpenStack Integration

2015-05-20 Thread Kevin Benton
Hi, I wasn't able to make it to the session but from the etherpad I saw that the VLAN-aware VMs mentioned there. Would that be enough to cover this particular use-case? On Wed, May 20, 2015 at 3:28 AM, Adrian Otto wrote: > Magnum and Neutron Teams, > > If you are in Vancouver today and can help

[openstack-dev] [Neutron][Magnum] Container + OpenStack Integration

2015-05-20 Thread Adrian Otto
Magnum and Neutron Teams, If you are in Vancouver today and can help design or implement native networking support to obviate the need for overlay networks when using containers, please join this design session: http://sched.co/3CjK (3:30 PM, Room 303) This will be based on feedback gathered a