<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif;">
<div>I agree, that is my take too. </div>
<div><br>
</div>
<div>Russell, since you lead the OVN session in Vancouver, would it be possible to include the VLAN-aware-vms BP in that session? </div>
<div><br>
</div>
<div>Thanks, </div>
<div>Bob</div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<div style="font-family:Calibri; font-size:11pt; text-align:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style="font-weight:bold">From: </span>Ian Wells <<a href="mailto:ijw.ubuntu@cack.org.uk">ijw.ubuntu@cack.org.uk</a>><br>
<span style="font-weight:bold">Reply-To: </span>"OpenStack Development Mailing List (not for usage questions)" <<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>><br>
<span style="font-weight:bold">Date: </span>fredag 3 april 2015 13:17<br>
<span style="font-weight:bold">To: </span>"OpenStack Development Mailing List (not for usage questions)" <<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>><br>
<span style="font-weight:bold">Subject: </span>Re: [openstack-dev] [Magnum] Containers and networking<br>
</div>
<div><br>
</div>
<div>
<div>
<div dir="ltr">
<div>This puts me in mind of a previous proposal, from the Neutron side of things. Specifically, I would look at Erik Moe's proposal for VM ports attached to multiple networks:
<a href="https://blueprints.launchpad.net/neutron/+spec/vlan-aware-vms">https://blueprints.launchpad.net/neutron/+spec/vlan-aware-vms</a> .<br>
<br>
</div>
<div>I believe that you want logical ports hiding behind a conventional port (which that has); the logical ports attached to a variety of Neutron networks despite coming through the same VM interface (ditto); and an encap on the logical port with a segmentation
ID (that uses exclusively VLANs, which probably suits here, though there's no particular reason why it has to be VLANs or why it couldn't be selectable). The original concept didn't require multiple ports attached to the same incoming subnetwork, but that's
a comparatively minor adaptation.<br>
</div>
<div>-- <br>
</div>
<div>Ian.<br>
</div>
<div><br>
</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On 2 April 2015 at 11:35, Russell Bryant <span dir="ltr">
<<a href="mailto:rbryant@redhat.com" target="_blank">rbryant@redhat.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<span class="">On 04/02/2015 01:45 PM, Kevin Benton wrote:<br>
> +1. I added a suggestion for a container networking suggestion to the<br>
> etherpad for neutron. It would be sad if the container solution built<br>
> yet another overlay on top of the Neutron networks with yet another<br>
> network management workflow. By the time the packets are traveling<br>
> across the wires, it would be nice not to have double encapsulation from<br>
> completely different systems.<br>
<br>
</span>Yeah, that's what I like about this proposal. Most of the existing work<br>
in this space seems to result in double encapsulation. Now we just need<br>
to finish building it ...<br>
<div class="HOEnZb">
<div class="h5"><br>
--<br>
Russell Bryant<br>
<br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank">
OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</div>
</div>
</span>
</body>
</html>