<html xmlns:v="urn:schemas-microsoft-com:vml" 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=us-ascii"><meta name=Generator content="Microsoft Word 12 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:SimSun;
panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
{font-family:SimSun;
panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:SimSun;
panose-1:2 1 6 0 3 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
text-align:justify;
text-justify:inter-ideograph;
font-size:10.5pt;
font-family:"Calibri","sans-serif";}
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-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;}
/* Page Definitions */
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=ZH-CN link=blue vlink=purple style='text-justify-trim:punctuation'><div class=WordSection1><p class=MsoNormal><span lang=EN-US>Hi,<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US>At my experiment of openstack implementing of production environment, cause of the factors of performance, stability ,security and maintanence, I think the VLAN model of nova-network multihost is quiet good choice to perform, I also like quantum of different network namespace to separate tenants and give the freedom let client to create their own network , but the problem was how only two(active/active base on pacemaker) network node servers could support tens of thousands VMs and so complicated N to N GRE tunnels in the system, whatever performance and stability and bad security of the metadata service to use external network to provide service? <o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US>Like the electric newspaper was not instead of paper media at the internet era, and I also did not believe the central network node, software based switch solution in the server is a better choice than hardware network equipment even SDN is so hot at present, is that a right decision to waste the powerful capacity of mature network technologies and equipment?<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US>Except the weakness of quantum, nova-network in Vlan mode also have a big problem in large and multiple cloud centers, the 4096 vlans limitation within one cloud system, it not only limits the the total number tenants and also the free transportation of VMs in same tenants from one could region to another, only because the 4096 vlans.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US>At my corner, if nova-network could be got continue supporting and vxlan feature would be support in the roadmap of next version, openstack system would get big confidence of implementing, because each tenant could get different VNI and each cloud region would use different range of VNI numbers, for example the regionOne would use 1-10000 VNIs and the regionTwo use 100001-20000,and if the vm in regionOne want move to regionTwo, it could still use the same VNI number in regionTwo, so it could still communicate with different openstack region but in same tenant and get same network. Of course we can use VPLS/MPLS VPN connect the different openstack region and across the service provider network.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US>Another way is to let the quantum pluging in compute node to support the “multi host” model like nova-network, to utilize the natural VXLAN support of openvswitch and pass the traffic directly through the compute node nic to outside Vxlan enabled network equipment,such as cisco, juniper and others but not a centralized software based “network node”.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US>So, my question is, can nova-network would still continue developing and support VXLAN in openstack H and later version? <o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US>That is very importance to us in production environment and multiple openstack regions.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US>Romi<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p></div></body></html>