<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 14 (filtered medium)"><!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","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;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
tt
{mso-style-priority:99;
font-family:"Courier New";}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.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><!--[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=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>I have also tried it out in my lab by following steps documented in this URL,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><a href="http://docs.openstack.org/trunk/openstack-network/admin/content/app_demo.html">http://docs.openstack.org/trunk/openstack-network/admin/content/app_demo.html</a><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>The floating IP address assigned to VM spawned off in controller node is working from, however, for VMs spawned off on compute node, floating IP address associated to them are not reachable from controller node or anywhere else. I don’t have a dedicated physical machine running as network node; this node is combined into the controller node which is a real physical machine. <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>In the pages following the network diagram, the CLIs provided using eth1, eth2 etc, but didn’t associate these network interface names with the three network links (mgmt net, data net, and public net) illustrated in the diagram. So maybe I’m still missing magic CLIs here to get multi node deployment working. Appreciate a lot if someone can shed some light here.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Thanks.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Dennis Qin<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> openstack-bounces+xiaohong.qin=emc.com@lists.launchpad.net [mailto:openstack-bounces+xiaohong.qin=emc.com@lists.launchpad.net] <b>On Behalf Of </b>Mohammad Banikazemi<br><b>Sent:</b> Thursday, October 18, 2012 6:15 AM<br><b>To:</b> Dan Wendlandt<br><b>Cc:</b> openstack-bounces+mb=us.ibm.com@lists.launchpad.net; openstack@lists.launchpad.net<br><b>Subject:</b> Re: [Openstack] Quantum features in the folsom release<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p>Trying to setup something similar to the Demo Setup described on the Openstack Quantum Admin Guide posted at: <a href="http://docs.openstack.org/trunk/openstack-network/admin/content/app_demo.html">http://docs.openstack.org/trunk/openstack-network/admin/content/app_demo.html</a>. I am using devstack to do the installation. <o:p></o:p></p><p>For the Network Node it says three network interfaces are required: <o:p></o:p></p><p>>The node must have at least three network interfaces. The first is used to communicate with the controller node,<br>>this is via the management network. The IP address of this interface should be configured to 100.1.1.12/24.<br>>The second interface will be used for the VM traffic, this is on the data network. The third interface will be used to<br>>connect to the external gateway on the network. This interface will be bridged to the Open vSwitch bridge "br-ex" interface. <o:p></o:p></p><p>1- Anyway we can set things up with only one or two interfaces? This is a real requirement or just to make the demo setup easier to implement? <o:p></o:p></p><p>2- Right now I only have two interfaces on my server and if I connect either of them to br-ex my server (the node and all the VMs on it) becomes unreachable. Right now I want to have only one single server for my experiments so I really do not need the network for VM traffic. <o:p></o:p></p><p>3- Is the br-eht1 bridge required for VM to VM communication is there to deal with namespaces? Earlier all I had to do to connect VMs on the same network together was to connect say eth1 directly to br-int. Now, there is this additional br-eth1 that needs to be created. <o:p></o:p></p><p>Thanks.<br><br><img border=0 width=16 height=16 id="_x0000_i1025" src="cid:image001.gif@01CDAD1A.C1A0D3B0" alt="Inactive hide details for Dan Wendlandt ---09/10/2012 02:43:07 PM---On Mon, Sep 10, 2012 at 11:07 AM, Bilel Msekni <skible@hotm"><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:#424282'>Dan Wendlandt ---09/10/2012 02:43:07 PM---On Mon, Sep 10, 2012 at 11:07 AM, Bilel Msekni <<a href="mailto:skible@hotmail.fr">skible@hotmail.fr</a>> wrote: > Hi Stackers,</span><br><br><span style='font-size:7.5pt;font-family:"Arial","sans-serif";color:#5F5F5F'>From: </span><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>Dan Wendlandt <<a href="mailto:dan@nicira.com">dan@nicira.com</a>></span><br><span style='font-size:7.5pt;font-family:"Arial","sans-serif";color:#5F5F5F'>To: </span><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>Bilel Msekni <<a href="mailto:skible@hotmail.fr">skible@hotmail.fr</a>>, </span><br><span style='font-size:7.5pt;font-family:"Arial","sans-serif";color:#5F5F5F'>Cc: </span><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'><a href="mailto:openstack@lists.launchpad.net">openstack@lists.launchpad.net</a></span><br><span style='font-size:7.5pt;font-family:"Arial","sans-serif";color:#5F5F5F'>Date: </span><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>09/10/2012 02:43 PM</span><br><span style='font-size:7.5pt;font-family:"Arial","sans-serif";color:#5F5F5F'>Subject: </span><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>Re: [Openstack] Quantum features in the folsom release</span><br><span style='font-size:7.5pt;font-family:"Arial","sans-serif";color:#5F5F5F'>Sent by: </span><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'><a href="mailto:openstack-bounces+mb=us.ibm.com@lists.launchpad.net">openstack-bounces+mb=us.ibm.com@lists.launchpad.net</a></span><o:p></o:p></p><div class=MsoNormal><hr size=2 width="100%" noshade style='color:#8091A5' align=left></div><p class=MsoNormal style='margin-bottom:12.0pt'><br><br><br><tt><span style='font-size:10.0pt'>On Mon, Sep 10, 2012 at 11:07 AM, Bilel Msekni <<a href="mailto:skible@hotmail.fr">skible@hotmail.fr</a>> wrote:</span></tt><span style='font-size:10.0pt;font-family:"Courier New"'><br><tt>> Hi Stackers,</tt><br><tt>></tt><br><tt>> Can someone here help me out by detailing the new Quantum features that will</tt><br><tt>> be available in the Folsom release. Even a link or anything could help ! i</tt><br><tt>> can't seem to find any proper documentation and i have to persuade my boss</tt><br><tt>> about the potentials of Quantum :)</tt><br><br><tt>Hi Bilel,</tt><br><br><tt>Don't worry, the Quantum team is working hard on docs for Folsom as we speak.</tt><br><br><tt>At an extremely high-level, the two main things that Quantum provides are:</tt><br><br><tt>1) A rich tenant-facing API for defining networks. This let's tenants</tt><br><tt>create rich network topologies, including multiple private networks,</tt><br><tt>multi-tier web applications, etc. and choose which IP subnets are used</tt><br><tt>on these networks (this even works if two tenants decide to use the</tt><br><tt>same subnet).</tt><br><br><tt>2) Quantum has pluggable backends that allow cloud operators to use</tt><br><tt>more advanced network technologies on the back-end. For example, you</tt><br><tt>can use Open vSwitch tunneling to avoid limitations around VLANs or</tt><br><tt>take advantage of a plugin that is aware of advanced hardware</tt><br><tt>capabilities.</tt><br><br><tt>The Quantum Admin Guide is still in draft form and we're hoping to</tt><br><tt>have a publicly consumable draft near the end of this week. That</tt><br><tt>should provide the additional details about specific capabilities.</tt><br><br><tt>Dan</tt><br><br><br><tt>></tt><br><tt>> Thanks</tt><br><tt>></tt><br><tt>> _______________________________________________</tt><br><tt>> Mailing list: <a href="https://launchpad.net/~openstack">https://launchpad.net/~openstack</a></tt><br><tt>> Post to : <a href="mailto:openstack@lists.launchpad.net">openstack@lists.launchpad.net</a></tt><br><tt>> Unsubscribe : <a href="https://launchpad.net/~openstack">https://launchpad.net/~openstack</a></tt><br><tt>> More help : <a href="https://help.launchpad.net/ListHelp">https://help.launchpad.net/ListHelp</a></tt><br><br><br><br><tt>-- </tt><br><tt>~~~~~~~~~~~~~~~~~~~~~~~~~~~</tt><br><tt>Dan Wendlandt</tt><br><tt>Nicira, Inc: <a href="http://www.nicira.com">www.nicira.com</a></tt><br><tt>twitter: danwendlandt</tt><br><tt>~~~~~~~~~~~~~~~~~~~~~~~~~~~</tt><br><br><tt>_______________________________________________</tt><br><tt>Mailing list: <a href="https://launchpad.net/~openstack">https://launchpad.net/~openstack</a></tt><br><tt>Post to : <a href="mailto:openstack@lists.launchpad.net">openstack@lists.launchpad.net</a></tt><br><tt>Unsubscribe : <a href="https://launchpad.net/~openstack">https://launchpad.net/~openstack</a></tt><br><tt>More help : <a href="https://help.launchpad.net/ListHelp">https://help.launchpad.net/ListHelp</a></tt><br><br></span><o:p></o:p></p></div></body></html>