<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">Hello all,<br>
<br>
I did report a bug about the lack of good documentation of quantum
and provider routing. <br>
<br>
If you find the solution, can you add it to the bug report? Maybe
I can write a 'fix' for it.<br>
<br>
The bug number is #1066782<br>
<br>
Kind regards,<br>
<br>
Jasper Aikema<br>
<br>
</div>
<blockquote
cite="mid:7C2808FDA62A0D408B1287392B55E95001214B9B@CORPUSMX30A.corp.emc.com"
type="cite">
<meta http-equiv="Context-Type" content="text/html;
charset=us-ascii">
<meta name="Generator" content="Microsoft Word 14 (filtered
medium)">
<div class="WordSection1">
<p class="MsoNormal"><span>I have also tried it out in my lab by
following steps documented in this URL,</span></p>
<p class="MsoNormal"><span> </span></p>
<p class="MsoNormal"><span><a moz-do-not-send="true"
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></span></p>
<p class="MsoNormal"><span> </span></p>
<p class="MsoNormal"><span>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. </span></p>
<p class="MsoNormal"><span> </span></p>
<p class="MsoNormal"><span>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.</span></p>
<p class="MsoNormal"><span> </span></p>
<p class="MsoNormal"><span>Thanks.</span></p>
<p class="MsoNormal"><span> </span></p>
<p class="MsoNormal"><span>Dennis Qin</span></p>
<p class="MsoNormal"><span> </span></p>
<div>
<div>
<p class="MsoNormal"><b><span>From:</span></b><span>
<a class="moz-txt-link-abbreviated" href="mailto:openstack-bounces+xiaohong.qin=emc.com@lists.launchpad.net">openstack-bounces+xiaohong.qin=emc.com@lists.launchpad.net</a>
[<a class="moz-txt-link-freetext" href="mailto:openstack-bounces+xiaohong.qin=emc.com@lists.launchpad.net">mailto:openstack-bounces+xiaohong.qin=emc.com@lists.launchpad.net</a>]
<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>
<a class="moz-txt-link-abbreviated" href="mailto:openstack-bounces+mb=us.ibm.com@lists.launchpad.net">openstack-bounces+mb=us.ibm.com@lists.launchpad.net</a>;
<a class="moz-txt-link-abbreviated" href="mailto:openstack@lists.launchpad.net">openstack@lists.launchpad.net</a><br>
<b>Subject:</b> Re: [Openstack] Quantum features in the
folsom release</span></p>
</div>
</div>
<p class="MsoNormal"> </p>
<p>Trying to setup something similar to the Demo Setup described
on the Openstack Quantum Admin Guide posted at: <a
moz-do-not-send="true"
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. </p>
<p>For the Network Node it says three network interfaces are
required: </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. </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? </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. </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. </p>
<p>Thanks.<br>
<br>
<img id="_x0000_i1025"
src="cid:part3.02090001.00020906@aikema.nl" 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" width="16" height="16"><span>Dan Wendlandt
---09/10/2012 02:43:07 PM---On Mon, Sep 10, 2012 at 11:07
AM, Bilel Msekni <<a moz-do-not-send="true"
href="mailto:skible@hotmail.fr">skible@hotmail.fr</a>>
wrote: > Hi Stackers,</span><br>
<br>
<span>From: </span><span>Dan Wendlandt <<a
moz-do-not-send="true" href="mailto:dan@nicira.com">dan@nicira.com</a>></span><br>
<span>To: </span><span>Bilel Msekni <<a
moz-do-not-send="true" href="mailto:skible@hotmail.fr">skible@hotmail.fr</a>>,
</span><br>
<span>Cc: </span><span><a moz-do-not-send="true"
href="mailto:openstack@lists.launchpad.net">openstack@lists.launchpad.net</a></span><br>
<span>Date: </span><span>09/10/2012 02:43 PM</span><br>
<span>Subject: </span><span>Re: [Openstack] Quantum features
in the folsom release</span><br>
<span>Sent by: </span><span><a moz-do-not-send="true"
href="mailto:openstack-bounces+mb=us.ibm.com@lists.launchpad.net">openstack-bounces+mb=us.ibm.com@lists.launchpad.net</a></span></p>
<div class="MsoNormal">
<hr width="100%"></div>
<p class="MsoNormal"><br>
<br>
<br>
<tt><span>On Mon, Sep 10, 2012 at 11:07 AM, Bilel Msekni <<a
moz-do-not-send="true" href="mailto:skible@hotmail.fr">skible@hotmail.fr</a>>
wrote:</span></tt><span><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 moz-do-not-send="true"
href="https://launchpad.net/%7Eopenstack">https://launchpad.net/~openstack</a></tt><br>
<tt>> Post to : <a moz-do-not-send="true"
href="mailto:openstack@lists.launchpad.net">openstack@lists.launchpad.net</a></tt><br>
<tt>> Unsubscribe : <a moz-do-not-send="true"
href="https://launchpad.net/%7Eopenstack">https://launchpad.net/~openstack</a></tt><br>
<tt>> More help : <a moz-do-not-send="true"
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 moz-do-not-send="true"
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 moz-do-not-send="true"
href="https://launchpad.net/%7Eopenstack">https://launchpad.net/~openstack</a></tt><br>
<tt>Post to : <a moz-do-not-send="true"
href="mailto:openstack@lists.launchpad.net">openstack@lists.launchpad.net</a></tt><br>
<tt>Unsubscribe : <a moz-do-not-send="true"
href="https://launchpad.net/%7Eopenstack">https://launchpad.net/~openstack</a></tt><br>
<tt>More help : <a moz-do-not-send="true"
href="https://help.launchpad.net/ListHelp">https://help.launchpad.net/ListHelp</a></tt><br>
<br>
</span></p>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Mailing list: <a class="moz-txt-link-freetext" href="https://launchpad.net/~openstack">https://launchpad.net/~openstack</a>
Post to : <a class="moz-txt-link-abbreviated" href="mailto:openstack@lists.launchpad.net">openstack@lists.launchpad.net</a>
Unsubscribe : <a class="moz-txt-link-freetext" href="https://launchpad.net/~openstack">https://launchpad.net/~openstack</a>
More help : <a class="moz-txt-link-freetext" href="https://help.launchpad.net/ListHelp">https://help.launchpad.net/ListHelp</a>
</pre>
</blockquote>
<br>
</body>
</html>