<div dir="ltr">i think both a new vnic_type and a new vif_type should be added. now vnic has three types: normal, direct, macvtap, then we need a new type of "uservhost". <div><br></div><div>as for vif_type, now we have <span style="font-family:arial,sans-serif;font-size:12.727272033691406px">VIF_TYPE_OVS, VIF_TYPE_QBH/QBG, </span><span style="font-family:arial,sans-serif;font-size:12.727272033691406px">VIF_HW_VEB, so we need a new VIF_TYPE_USEROVS</span></div>
<div><span style="font-family:arial,sans-serif;font-size:12.727272033691406px"><br></span></div><div><span style="font-family:arial,sans-serif;font-size:12.727272033691406px">I don't think it's a good idea to directly reuse ovs agent, for we have to consider use cases that ovs and userovs co-exists. Now it's a little painful to fork and write a new agent, but it will be easier when ML2 agent BP is merged in the future. (</span><font face="arial, sans-serif"><a href="https://etherpad.openstack.org/p/modular-l2-agent-outline">https://etherpad.openstack.org/p/modular-l2-agent-outline</a></font><span style="font-family:arial,sans-serif;font-size:12.727272033691406px">)</span></div>
</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Jul 9, 2014 at 11:08 PM, Czesnowicz, Przemyslaw <span dir="ltr"><<a href="mailto:przemyslaw.czesnowicz@intel.com" target="_blank">przemyslaw.czesnowicz@intel.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div lang="EN-IE" link="blue" vlink="purple">
<div>
<p class="MsoNormal">Hi<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">We (Intel Openstack team) would like to add support for dpdk based userspace openvswitch using mech_openvswitch and mech_odl from ML2 plugin.<u></u><u></u></p>
<p class="MsoNormal">The dpdk enabled ovs comes in two flavours one is netdev incorporated into vanilla ovs the other is a fork of ovs with a dpdk datapath (<a href="https://github.com/01org/dpdk-ovs" target="_blank">https://github.com/01org/dpdk-ovs</a> ).<u></u><u></u></p>
<p class="MsoNormal">Both flavours use userspace vhost mechanism to connect the VMs to the switch.<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">Our initial approach was to extend ovs vif bindings in nova and add a config parameter to specify when userspace vhost should be used.<u></u><u></u></p>
<p class="MsoNormal"><span lang="PL">Spec : <a href="https://review.openstack.org/95805" target="_blank">
https://review.openstack.org/95805</a><u></u><u></u></span></p>
<p class="MsoNormal"><span lang="PL">Code: <a href="https://review.openstack.org/100256" target="_blank">
https://review.openstack.org/100256</a><u></u><u></u></span></p>
<p class="MsoNormal"><span lang="PL"><u></u> <u></u></span></p>
<p class="MsoNormal">Nova devs rejected this approach saying that Neutron should pass all necessary information to nova to select vif bindings.<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">Currently we are looking for a way to pass information from Neutron to Nova that dpdk enabled ovs is being used while still being able to use mech_openvswitch and ovs_neutron_agent or mech_odl.<u></u><u></u></p>
<p class="MsoNormal">
<u></u><u></u></p>
<p class="MsoNormal">We thought of two possible solutions:<u></u><u></u></p>
<p><u></u><span>1.<span style="font:7.0pt "Times New Roman"">
</span></span><u></u>Use binding_profile to provide node specific info to nova.
<u></u><u></u></p>
<p>Agent rpc api would be extended to allow agents to send node profile to neutron plugin.<u></u><u></u></p>
<p>That info would be stored in db and passed to nova when binding on this specific host is requested.<u></u><u></u></p>
<p>This could be used to support our use case or pass other info to nova (i.e name of integration bridge)<u></u><u></u></p>
<p><u></u> <u></u></p>
<p><u></u><span>2.<span style="font:7.0pt "Times New Roman"">
</span></span><u></u>Let mech_openvswitch and mech_odl detect what binding type to use.<u></u><u></u></p>
<p>When asked for port binding mech_openvswitch and mech_odl would call the agent or odl to check what bindings to use (VIF_TYPE_OVS or VIF_TYPE_DPDKVHOST)<u></u><u></u></p>
<p><u></u> <u></u></p>
<p class="MsoNormal">So, what would be the best way to support our usecase, is it one of the above ?
<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">Best regards<u></u><u></u></p>
<p class="MsoNormal">Przemek<u></u><u></u></p>
</div>
<p>--------------------------------------------------------------<br>
Intel Shannon Limited<br>
Registered in Ireland<br>
Registered Office: Collinstown Industrial Park, Leixlip, County Kildare<br>
Registered Number: 308263<br>
Business address: Dromore House, East Park, Shannon, Co. Clare</p>
<p>This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies.</p>
<p></p></div>
<br>_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</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>
<br></blockquote></div><br></div>