<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Title" content="">
<meta name="Keywords" content="">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Arial;
panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
{font-family:"Cambria Math";
panose-1:0 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:Calibri;
color:windowtext;}
span.msoIns
{mso-style-type:export-only;
mso-style-name:"";
text-decoration:underline;
color:teal;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style>
</head>
<body bgcolor="white" lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">That is already supported in stable/mitaka – please see
<a href="https://review.openstack.org/#/c/260700/">https://review.openstack.org/#/c/260700/</a><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">I agree with Kevin<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"><o:p> </o:p></span></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-family:Calibri;color:black">From: </span>
</b><span style="font-family:Calibri;color:black">Kevin Benton <kevin@benton.pub><br>
<b>Reply-To: </b>OpenStack List <openstack-dev@lists.openstack.org><br>
<b>Date: </b>Monday, June 13, 2016 at 11:59 PM<br>
<b>To: </b>OpenStack List <openstack-dev@lists.openstack.org><br>
<b>Subject: </b>Re: [openstack-dev] [Neutron][os-vif] Expanding vif capability for wiring trunk ports<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<div>
<div>
<p class="MsoNormal">+1. Neutron should already be able to tell Nova which bridge to use for an OVS port.[1] For the Linux bridge implementation it's a matter of creating vlan interfaces and plugging them into bridges like regular VM ports, which is all the
responsibility of the L2 agent. We shouldn't need any changes from Nova or os-vif from what I can see.
<o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">1. <a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_openstack_nova_blob_6e2e1dc912199e057e5c3a5e07d39f26cbbbdd5b_nova_network_neutronv2_api.py-23L1618&d=CwMFaQ&c=Sqcl0Ez6M0X8aeM67LKIiDJAXVeAw-YihVMNtXt-uEs&r=VlZxHpZBmzzkWT5jqz9JYBk8YTeq9N3-diTlNj4GyNc&m=aLF644Euno1BNoUIMh7bFndKIXDcBjRS2_4IRRAOPd8&s=rZ57uFzphC8svGsKNC-YKhhE9VTkLoNxuEu4oOkJEAQ&e=">https://github.com/openstack/nova/blob/6e2e1dc912199e057e5c3a5e07d39f26cbbbdd5b/nova/network/neutronv2/api.py#L1618</a><o:p></o:p></p>
</div>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">On Mon, Jun 13, 2016 at 5:26 AM, Mooney, Sean K <<a href="mailto:sean.k.mooney@intel.com" target="_blank">sean.k.mooney@intel.com</a>> wrote:<o:p></o:p></p>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<p class="MsoNormal"><br>
<br>
> -----Original Message-----<br>
> From: Daniel P. Berrange [mailto:<a href="mailto:berrange@redhat.com">berrange@redhat.com</a>]<br>
> Sent: Monday, June 13, 2016 1:12 PM<br>
> To: Armando M. <<a href="mailto:armamig@gmail.com">armamig@gmail.com</a>><br>
> Cc: Carl Baldwin <<a href="mailto:carl@ecbaldwin.net">carl@ecbaldwin.net</a>>; OpenStack Development Mailing<br>
> List <<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>>; Jay Pipes<br>
> <<a href="mailto:jaypipes@gmail.com">jaypipes@gmail.com</a>>; Maxime Leroy <<a href="mailto:maxime.leroy@6wind.com">maxime.leroy@6wind.com</a>>; Moshe Levi<br>
> <<a href="mailto:moshele@mellanox.com">moshele@mellanox.com</a>>; Russell Bryant <<a href="mailto:rbryant@redhat.com">rbryant@redhat.com</a>>; sahid<br>
> <<a href="mailto:sahid.ferdjaoui@redhat.com">sahid.ferdjaoui@redhat.com</a>>; Mooney, Sean K <<a href="mailto:sean.k.mooney@intel.com">sean.k.mooney@intel.com</a>><br>
> Subject: Re: [Neutron][os-vif] Expanding vif capability for wiring trunk<br>
> ports<o:p></o:p></p>
<div>
<div>
<p class="MsoNormal">><br>
> On Mon, Jun 13, 2016 at 02:08:30PM +0200, Armando M. wrote:<br>
> > On 13 June 2016 at 10:35, Daniel P. Berrange <<a href="mailto:berrange@redhat.com">berrange@redhat.com</a>><br>
> wrote:<br>
> ><br>
> > > On Thu, Jun 09, 2016 at 05:31:13PM -0600, Carl Baldwin wrote:<br>
> > > > Hi,<br>
> > > ><br>
> > > > You may or may not be aware of the vlan-aware-vms effort [1] in<br>
> > > > Neutron. If not, there is a spec and a fair number of patches in<br>
> > > > progress for this. Essentially, the goal is to allow a VM to<br>
> > > > connect to multiple Neutron networks by tagging traffic on a<br>
> > > > single port with VLAN tags.<br>
> > > ><br>
> > > > This effort will have some effect on vif plugging because the<br>
> > > > datapath will include some changes that will effect how vif<br>
> > > > plugging is done today.<br>
> > > ><br>
> > > > The design proposal for trunk ports with OVS adds a new bridge for<br>
> > > > each trunk port. This bridge will demux the traffic and then<br>
> > > > connect to br-int with patch ports for each of the networks.<br>
> > > > Rawlin Peters has some ideas for expanding the vif capability to<br>
> > > > include this wiring.<br>
> > > ><br>
> > > > There is also a proposal for connecting to linux bridges by using<br>
> > > > kernel vlan interfaces.<br>
> > > ><br>
> > > > This effort is pretty important to Neutron in the Newton<br>
> > > > timeframe. I wanted to send this out to start rounding up the<br>
> > > > reviewers and other participants we need to see how we can start<br>
> > > > putting together a plan for nova integration of this feature (via<br>
> os-vif?).<br>
> > ><br>
> > > I've not taken a look at the proposal, but on the timing side of<br>
> > > things it is really way to late to start this email thread asking<br>
> > > for design input from os-vif or nova. We're way past the spec<br>
> > > proposal deadline for Nova in the Newton cycle, so nothing is going<br>
> > > to happen until the Ocata cycle no matter what Neutron want in<br>
> Newton.<br>
> ><br>
> ><br>
> > For sake of clarity, does this mean that the management of the os-vif<br>
> > project matches exactly Nova's, e.g. same deadlines and processes<br>
> > apply, even though the core team and its release model are different<br>
> from Nova's?<br>
> > I may have erroneously implied that it wasn't, also from past talks I<br>
> > had with johnthetubaguy.<br>
><br>
> No, we don't intend to force ourselves to only release at milestones<br>
> like nova does. We'll release the os-vif library whenever there is new<br>
> functionality in its code that we need to make available to<br>
> nova/neutron.<br>
> This could be as frequently as once every few weeks.<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal">[Mooney, Sean K]<br>
I have been tracking contributing to the vlan aware vm work in<br>
neutron since the Vancouver summit so I am quite familiar with what would have<br>
to be modified to support the vlan trucking. Provided the modifications do not<br>
delay the conversion to os-vif in nova this cycle I would be happy to review<br>
and help develop the code to support this use case.<br>
<br>
In the ovs case at lease which we have been discussing here<br>
<a href="https://review.openstack.org/#/c/318317/4/doc/source/devref/openvswitch_agent.rst" target="_blank">https://review.openstack.org/#/c/318317/4/doc/source/devref/openvswitch_agent.rst</a><br>
no changes should be required for nova and all changes will be confined to the ovs<br>
plugin. In is essence check if bridge exists, if not create it with port id,<br>
Then plug as normal.<br>
<br>
Again though I do agree that we should focus on completing the initial nova integration<br>
But I don't think that mean we have to exclude other feature enhancements as long as they<br>
do not prevent us achieving that goal.<o:p></o:p></p>
<div>
<div>
<p class="MsoNormal"><br>
<br>
><br>
> Regards,<br>
> Daniel<br>
> --<br>
> |: <a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__berrange.com&d=CwMFaQ&c=Sqcl0Ez6M0X8aeM67LKIiDJAXVeAw-YihVMNtXt-uEs&r=VlZxHpZBmzzkWT5jqz9JYBk8YTeq9N3-diTlNj4GyNc&m=aLF644Euno1BNoUIMh7bFndKIXDcBjRS2_4IRRAOPd8&s=Go-7xVc1yP_Ym6LjZZFuyvobsnfiVgda_2Us677ccLA&e=" target="_blank">
http://berrange.com</a> -o-<br>
> <a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__www.flickr.com_photos_dberrange_&d=CwMFaQ&c=Sqcl0Ez6M0X8aeM67LKIiDJAXVeAw-YihVMNtXt-uEs&r=VlZxHpZBmzzkWT5jqz9JYBk8YTeq9N3-diTlNj4GyNc&m=aLF644Euno1BNoUIMh7bFndKIXDcBjRS2_4IRRAOPd8&s=x9UIEEQ0B4Q8T50x_aQiGAyEv3IHMP7ZSlhBBzct2yQ&e=" target="_blank">
http://www.flickr.com/photos/dberrange/</a> :|<br>
> |: <a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__libvirt.org&d=CwMFaQ&c=Sqcl0Ez6M0X8aeM67LKIiDJAXVeAw-YihVMNtXt-uEs&r=VlZxHpZBmzzkWT5jqz9JYBk8YTeq9N3-diTlNj4GyNc&m=aLF644Euno1BNoUIMh7bFndKIXDcBjRS2_4IRRAOPd8&s=PX17BlN9dq54FyxHlpEFj0tAZNAANmwbCz-_7v243_s&e=" target="_blank">
http://libvirt.org</a> -o- <a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__virt-2D&d=CwMFaQ&c=Sqcl0Ez6M0X8aeM67LKIiDJAXVeAw-YihVMNtXt-uEs&r=VlZxHpZBmzzkWT5jqz9JYBk8YTeq9N3-diTlNj4GyNc&m=aLF644Euno1BNoUIMh7bFndKIXDcBjRS2_4IRRAOPd8&s=zSw6evbd50kY6qXOLbmvIYaNSHhdGWjvrqWagekvd6k&e=" target="_blank">http://virt-</a><br>
> <a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__manager.org&d=CwMFaQ&c=Sqcl0Ez6M0X8aeM67LKIiDJAXVeAw-YihVMNtXt-uEs&r=VlZxHpZBmzzkWT5jqz9JYBk8YTeq9N3-diTlNj4GyNc&m=aLF644Euno1BNoUIMh7bFndKIXDcBjRS2_4IRRAOPd8&s=fuoQA8upm3D0d8nTwaGFu_rw8B_ncN24rYJiDgEIOpI&e=" target="_blank">
manager.org</a> :|<br>
> |: <a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__autobuild.org&d=CwMFaQ&c=Sqcl0Ez6M0X8aeM67LKIiDJAXVeAw-YihVMNtXt-uEs&r=VlZxHpZBmzzkWT5jqz9JYBk8YTeq9N3-diTlNj4GyNc&m=aLF644Euno1BNoUIMh7bFndKIXDcBjRS2_4IRRAOPd8&s=Jkbd2nsHuyiRWxnMzvK6439_a7J1XyVHAGa2iHX7zHY&e=" target="_blank">
http://autobuild.org</a> -o-<br>
> <a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__search.cpan.org_-7Edanberr_&d=CwMFaQ&c=Sqcl0Ez6M0X8aeM67LKIiDJAXVeAw-YihVMNtXt-uEs&r=VlZxHpZBmzzkWT5jqz9JYBk8YTeq9N3-diTlNj4GyNc&m=aLF644Euno1BNoUIMh7bFndKIXDcBjRS2_4IRRAOPd8&s=KJaO0DvEmEZVq54kkc88G6Akd8zHs5tS-ES_prK1sOw&e=" target="_blank">
http://search.cpan.org/~danberr/</a> :|<br>
> |: <a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__entangle-2Dphoto.org&d=CwMFaQ&c=Sqcl0Ez6M0X8aeM67LKIiDJAXVeAw-YihVMNtXt-uEs&r=VlZxHpZBmzzkWT5jqz9JYBk8YTeq9N3-diTlNj4GyNc&m=aLF644Euno1BNoUIMh7bFndKIXDcBjRS2_4IRRAOPd8&s=9mu6yY4fxrHFgL-YNWyYRmwNiLgE7ca_qR7me58PO4w&e=" target="_blank">
http://entangle-photo.org</a> -o- <a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__live.gnome.org_gtk-2D&d=CwMFaQ&c=Sqcl0Ez6M0X8aeM67LKIiDJAXVeAw-YihVMNtXt-uEs&r=VlZxHpZBmzzkWT5jqz9JYBk8YTeq9N3-diTlNj4GyNc&m=aLF644Euno1BNoUIMh7bFndKIXDcBjRS2_4IRRAOPd8&s=3pQQ3-RX4l-Zo-432pIrqbmgiZY_z8gR3xESlKFhj8A&e=" target="_blank">http://live.gnome.org/gtk-</a><br>
> vnc :|<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><o:p></o:p></p>
</div>
</div>
</blockquote>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</div>
</div>
</body>
</html>