Open Stack

On 10/31/2012 01:08 PM, balaji patnala wrote:
> Hi Yong,
> Thanks for information.
> I think you mean to say that these Quantum Network Node is not per 
> Tenant basis and it can serve all the Tenants of DC setup.
> Just want to un derstand what will be the advantages we are thinking 
> of by doing so.
TO have multiple l3 agent nodes, we can distribute traffic from VMs 
among l3 agent nodes.
> Regards,
> Balaji
> On Tue, Oct 30, 2012 at 2:26 PM, gong yong sheng 
> <gongysh at linux.vnet.ibm.com <mailto:gongysh at linux.vnet.ibm.com>> wrote:
>
>     Hi,
>     In fact, we can split Quantum network Node into two categories:
>     one is for dhcp, which install ovs agent and dhcp agent. We can
>     have one such kind of node
>     one is for l3 agent, we can deal with one external network on one
>     l3 agent. We can have many nodes of this kind.
>
>     Regards,
>
>     Yong Sheng Gong
>
>     On 10/30/2012 02:27 PM, balaji patnala wrote:
>>     Hi Salvatore,
>>     Just want to understand more on Network Node in the below given
>>     app_demo page.
>>     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.
>>     This Quantum Network Node will have all the virtual routers,
>>     gateway which can be created with quantum-l3-agent plugin.
>>     Also my assumption is that this quantum Network Node will serve
>>     all the Tenant virtual gateways and routers created using quantum.
>>     Please give us some more information on this to understand the setup.
>>     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.
>>     Thanks in advance.
>>     Regards,
>>     Balaji
>>
>>     On Fri, Oct 26, 2012 at 3:31 PM, Salvatore Orlando
>>     <sorlando at nicira.com <mailto:sorlando at nicira.com>> wrote:
>>
>>         Hi Trinath,
>>
>>         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.
>>         As suggested in [1], the only Quantum component running on
>>         the controller node should be the API server.
>>         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.
>>
>>         Regards,
>>         Salvatore
>>
>>         [1]
>>         http://docs.openstack.org/trunk/openstack-network/admin/content/app_demo.html
>>
>>         On 26 October 2012 10:50, Trinath Somanchi
>>         <trinath.somanchi at gmail.com
>>         <mailto:trinath.somanchi at gmail.com>> wrote:
>>
>>             Hi Stackers-
>>
>>             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.
>>
>>             But I have doubt here,
>>
>>             Can't we have the Quantum-DHCP/L3-Agent to be running in
>>             the Compute NODE rather than in the controller.
>>
>>             How does the Installation and configuration change with
>>             this type of Installation?
>>
>>             Please guide me on How to achieve the same.
>>
>>             Thanking you
>>
>>             -- 
>>             Regards,
>>             ----------------------------------------------
>>             Trinath Somanchi,
>>             +91 9866 235 130 <tel:%2B91%209866%20235%20130>
>>
>>
>>             _______________________________________________
>>             Mailing list: https://launchpad.net/~openstack
>>             <https://launchpad.net/%7Eopenstack>
>>             Post to     : openstack at lists.launchpad.net
>>             <mailto:openstack at lists.launchpad.net>
>>             Unsubscribe : https://launchpad.net/~openstack
>>             <https://launchpad.net/%7Eopenstack>
>>             More help   : https://help.launchpad.net/ListHelp
>>
>>
>>
>>         _______________________________________________
>>         Mailing list: https://launchpad.net/~openstack
>>         <https://launchpad.net/%7Eopenstack>
>>         Post to     : openstack at lists.launchpad.net
>>         <mailto:openstack at lists.launchpad.net>
>>         Unsubscribe : https://launchpad.net/~openstack
>>         <https://launchpad.net/%7Eopenstack>
>>         More help   : https://help.launchpad.net/ListHelp
>>
>>
>>
>>
>>     _______________________________________________
>>     Mailing list:https://launchpad.net/~openstack  <https://launchpad.net/%7Eopenstack>
>>     Post to     :openstack at lists.launchpad.net  <mailto:openstack at lists.launchpad.net>
>>     Unsubscribe :https://launchpad.net/~openstack  <https://launchpad.net/%7Eopenstack>
>>     More help   :https://help.launchpad.net/ListHelp
>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack/attachments/20121031/0d31531b/attachment.html>