Hi Salvatore-<div><br></div><div>Thanks a lot for the reply.</div><div><br></div><div>In the Setup diagram, I'm planning to make a 2 machine setup in my test environment. </div><div><br></div><div>Where Can I have the Installation guideline for the Quantum L2 agent. </div>
<div><br></div><div>Have few doubts in the Quantum DHCP agent Source Code.</div><div><br></div><div>As I have gone through the source code, the DHCP agent runs as an RPC daemon. </div><div><br></div><div>It places messages in the ampq. I was confused with the following code in /quantum/db/dhcp_rpc_base.py </div>
<div><br></div><div>in the method: def get_network_info()</div><div><br></div><div><div> plugin = manager.QuantumManager.get_plugin() <-------- To what plugin its mapping to ? Is the appropriate plugin configured in the configuration files.</div>
<div> network = plugin.get_network(context, network_id)</div></div><div><br></div><div>How do the mapping to plugin made here?</div><div><br></div><div>Can you please help understand these... </div><div><br></div><div>
Thanking you</div><div><br></div><div>-</div><div>Trinath</div><div><br><br><div class="gmail_quote">On Fri, Oct 26, 2012 at 3:31 PM, Salvatore Orlando <span dir="ltr"><<a href="mailto:sorlando@nicira.com" target="_blank">sorlando@nicira.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">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 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 href="mailto:trinath.somanchi@gmail.com" target="_blank">trinath.somanchi@gmail.com</a>></span> wrote:<br>
</div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><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 href="tel:%2B91%209866%20235%20130" value="+919866235130" target="_blank">+91 9866 235 130</a></div><br>
</font></span></div>
<br></div></div>_______________________________________________<br>
Mailing list: <a href="https://launchpad.net/~openstack" target="_blank">https://launchpad.net/~openstack</a><br>
Post to : <a href="mailto:openstack@lists.launchpad.net" target="_blank">openstack@lists.launchpad.net</a><br>
Unsubscribe : <a href="https://launchpad.net/~openstack" target="_blank">https://launchpad.net/~openstack</a><br>
More help : <a href="https://help.launchpad.net/ListHelp" target="_blank">https://help.launchpad.net/ListHelp</a><br>
<br></blockquote></div><br></div>
</blockquote></div><br><br clear="all"><div><br></div>-- <br>Regards,<br>----------------------------------------------<br>Trinath Somanchi,<div>+91 9866 235 130</div><br>
</div>