<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="Titre" content="">
<meta name="Mots clés" content="">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@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:0cm;
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:595.0pt 842.0pt;
margin:70.85pt 70.85pt 70.85pt 70.85pt;}
div.WordSection1
{page:WordSection1;}
--></style>
</head>
<body bgcolor="white" lang="FR" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:Calibri;mso-fareast-language:EN-US">Hey Kevin,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:Calibri;mso-fareast-language:EN-US">Thanks for your interest in this project.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:Calibri;mso-fareast-language:EN-US">We found etcd very convenient to store desired states as well as operational states. It made the design easy to provide production grade features
(e.g. agent restart, mechanical driver restart, …) in a very concise code. In addition to that, debugging is simple to do using simple “etcdwatch” commands. Please note that etcd is not an alternative to rabbitmq even though communication protocol is HTTP/JSON.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:Calibri;mso-fareast-language:EN-US">Jerome<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:Calibri;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span style="font-family:Calibri;color:black">De : </span>
</b><span style="font-family:Calibri;color:black">Kevin Benton <kevin@benton.pub><br>
<b>Répondre à : </b>"OpenStack Development Mailing List (not for usage questions)" <openstack-dev@lists.openstack.org><br>
<b>Date : </b>jeudi 6 octobre 2016 00:27<br>
<b>À : </b>"OpenStack Development Mailing List (not for usage questions)" <openstack-dev@lists.openstack.org><br>
<b>Objet : </b>Re: [openstack-dev] [neutron][networking-vpp]Introducing networking-vpp<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Cool. Always like to see more drivers. <o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">I'm curious about the choice of etcd instead of rabbitmq as the communication mechanism between the mech driver and the agents since it introduces a new dependency into the deployment. Is this because the agent is written to work with other
things like Kubernetes, Docker, etc as well?<o:p></o:p></p>
</div>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">On Wed, Oct 5, 2016 at 12:01 PM, Ian Wells <<a href="mailto:ijw.ubuntu@cack.org.uk" target="_blank">ijw.ubuntu@cack.org.uk</a>> wrote:<o:p></o:p></p>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm">
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt">We'd like to introduce the VPP mechanism driver, networking-vpp[1], to the developer community.<br>
<br>
networking-vpp is an ML2 mechanism driver to control DPDK-based VPP user-space forwarders on OpenStack compute nodes. The code does what mechanism drivers do - it connects VMs to each other and to other Neutron-provided network services like routers. It also
does it with care - we aim to make sure this is a robust design that can withstand common cloud problems and failures - and with clarity - so that it's straightforward to see what it's chosen to do and what it's thinking.<br>
<br>
To give some background:<br>
<br>
VPP is an open source network forwarder originally developed by Cisco and now part of the Linux Foundation FD.io project for fast dataplanes. It's very very good at moving packets around, and has demonstrated performance up to and well beyond 10Gbps - of tiny
packets: ten times the number of packets iperf uses to fill a 10Gbps link. This makes it especially useful for NFV use cases. It's a user space forwarder, which has other benefits versus kernel packet forwarding: it can be stopped and upgraded without rebooting
the host, and (in the worst case) it can crash without bringing down the whole system.<br>
<br>
networking-vpp is its driver for OpenStack. We've written about 3,000 lines of code, consisting of a mechanism driver and an agent to program VPP through its Python API, and we use etcd to be a robust datastore and communication channel living between the
two.<br>
<br>
<br>
The code, at the moment, is in a fairly early stage, so please play with it and fix or report any problems you find. It will move packets between VLANs and flat networks and VMs, and will connect to DHCP servers, routers and the metadata server in your cloud,
so for basic uses it will work just the way you expect. However, we certainly don't support every feature of Neutron just yet. In particular, we haven't tested some things like LBaaS and VPNaaS with it - they should work, we just haven't tried - and, most
obviously, security groups are not yet implemented - that's on the way. However, we'd like to get it into your hands so that you can have a go with it, see what you like and don't like about it, and help us file down the rough edges if you feel like joining
us. Enjoy!<br>
<br>
[1]<br>
<a href="https://github.com/openstack/networking-vpp" target="_blank">https://github.com/openstack/networking-vpp</a> for all your code needs<br>
<a href="https://review.openstack.org/#/q/status:open+project:openstack/networking-vpp" target="_blank">https://review.openstack.org/#/q/status:open+project:openstack/networking-vpp</a> to help<br>
<a href="https://launchpad.net/networking-vpp" target="_blank">https://launchpad.net/networking-vpp</a> for bugs<o:p></o:p></p>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><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>
</blockquote>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</body>
</html>