<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">Hi,<br>
In fact, we can split Quantum network Node into two categories:<br>
one is for dhcp, which install ovs agent and dhcp agent. We can
have one such kind of node<br>
one is for l3 agent, we can deal with one external network on one
l3 agent. We can have many nodes of this kind.<br>
<br>
Regards,<br>
<br>
Yong Sheng Gong<br>
On 10/30/2012 02:27 PM, balaji patnala wrote:<br>
</div>
<blockquote
cite="mid:CANT02KSHQUYEtCtU2yWxiM4d9HwgvETFg4cmDpobkDgQsP+uMQ@mail.gmail.com"
type="cite">
<div>Hi Salvatore,</div>
<div> </div>
<div>Just want to understand more on Network Node in the below
given app_demo page.</div>
<div> </div>
<div>As i see in the setup, it looks like there will be one
Quantum Network Node for one Data centre setup. Please correct
me if my assumptions are wrong.</div>
<div> </div>
<div>This Quantum Network Node will have all the virtual routers,
gateway which can be created with quantum-l3-agent plugin.</div>
<div> </div>
<div>Also my assumption is that this quantum Network Node will
serve all the Tenant virtual gateways and routers created using
quantum.</div>
<div> </div>
<div>Please give us some more information on this to understand
the setup.</div>
<div> </div>
<div>Also do we have any specific reason for having quantum
Network Node instead of keeping these plugin on the Controller
Node similar to earlier release like Essex.</div>
<div> </div>
<div>Thanks in advance.</div>
<div> </div>
<div>Regards,</div>
<div>Balaji<br>
<br>
</div>
<div class="gmail_quote">On Fri, Oct 26, 2012 at 3:31 PM,
Salvatore Orlando <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:sorlando@nicira.com" target="_blank">sorlando@nicira.com</a>></span>
wrote:<br>
<blockquote style="BORDER-LEFT:#ccc 1px solid;MARGIN:0px 0px 0px
0.8ex;PADDING-LEFT:1ex" class="gmail_quote">Hi Trinath,
<div><br>
</div>
<div>Even if is perfectly reasonable to run the DHCP/L3 agents
in the controller node, the advice we give in the
administration guide is slightly different.</div>
<div>As suggested in [1], the only Quantum component running
on the controller node should be the API server.</div>
<div>The DHCP and L3 agents might run in a dedicated "network
node". Please note you will need also the L2 agent running
on that node.</div>
<div><br>
</div>
<div>Regards,</div>
<div>Salvatore</div>
<div><br>
</div>
<div>[1] <a moz-do-not-send="true"
href="http://docs.openstack.org/trunk/openstack-network/admin/content/app_demo.html"
target="_blank">http://docs.openstack.org/trunk/openstack-network/admin/content/app_demo.html</a><br>
<br>
<div class="gmail_quote">
<div>
<div class="h5">On 26 October 2012 10:50, Trinath
Somanchi <span dir="ltr"><<a
moz-do-not-send="true"
href="mailto:trinath.somanchi@gmail.com"
target="_blank">trinath.somanchi@gmail.com</a>></span>
wrote:<br>
</div>
</div>
<blockquote style="BORDER-LEFT:#ccc 1px solid;MARGIN:0px
0px 0px 0.8ex;PADDING-LEFT:1ex" class="gmail_quote">
<div>
<div class="h5">Hi Stackers-
<div><br>
</div>
<div>I have found many installation and
configuration manuals for Openstack Folsom which
state the installation and configuration of
Quantum-DHCP-Agent in the Controller machine.</div>
<div><br>
</div>
<div>But I have doubt here, </div>
<div><br>
</div>
<div>Can't we have the Quantum-DHCP/L3-Agent to be
running in the Compute NODE rather than in the
controller.</div>
<div><br>
</div>
<div>How does the Installation and configuration
change with this type of Installation?</div>
<div><br>
</div>
<div>Please guide me on How to achieve the same.</div>
<div><br>
</div>
<div>Thanking you <span><font color="#888888"><br
clear="all">
<div><br>
</div>
-- <br>
Regards,<br>
----------------------------------------------<br>
Trinath Somanchi,
<div><a moz-do-not-send="true"
href="tel:%2B91%209866%20235%20130"
target="_blank" value="+919866235130">+91
9866 235 130</a></div>
<br>
</font></span></div>
<br>
</div>
</div>
_______________________________________________<br>
Mailing list: <a moz-do-not-send="true"
href="https://launchpad.net/%7Eopenstack"
target="_blank">https://launchpad.net/~openstack</a><br>
Post to : <a moz-do-not-send="true"
href="mailto:openstack@lists.launchpad.net"
target="_blank">openstack@lists.launchpad.net</a><br>
Unsubscribe : <a moz-do-not-send="true"
href="https://launchpad.net/%7Eopenstack"
target="_blank">https://launchpad.net/~openstack</a><br>
More help : <a moz-do-not-send="true"
href="https://help.launchpad.net/ListHelp"
target="_blank">https://help.launchpad.net/ListHelp</a><br>
<br>
</blockquote>
</div>
<br>
</div>
<br>
_______________________________________________<br>
Mailing list: <a moz-do-not-send="true"
href="https://launchpad.net/%7Eopenstack" target="_blank">https://launchpad.net/~openstack</a><br>
Post to : <a moz-do-not-send="true"
href="mailto:openstack@lists.launchpad.net">openstack@lists.launchpad.net</a><br>
Unsubscribe : <a moz-do-not-send="true"
href="https://launchpad.net/%7Eopenstack" target="_blank">https://launchpad.net/~openstack</a><br>
More help : <a moz-do-not-send="true"
href="https://help.launchpad.net/ListHelp" target="_blank">https://help.launchpad.net/ListHelp</a><br>
<br>
</blockquote>
</div>
<br>
<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>