[Openstack] [Openstack :: Folsom] Quantum Network Node setup
Skible OpenStack
skible.openstack at gmail.com
Sat Nov 10 14:26:45 UTC 2012
Does anyone know how to configure l3 agent and dhcp agent when you have
a router for each of your tenants !
i am loosing internet connection each time i don't assign a value to
#router_id in the l3_agent.ini file !
Le 10/11/2012 15:06, balaji patnala a écrit :
> Hi Yong,
> I downloaded the Quantum Architecture in Folsom Powerpoint prepared by
> you and found that in slide-10:
>
> lL3-agent
> lTo implement floating Ipsand other L3 features, such as NAT
> _lOne per network_
> Can you elaborate on the comment 'one per network' for L3-Agent.
> As i understood that the L3-Agent will be only one for complete setup.
> If we have more than one Network Node then we must install dhcp-agent
> and L3-Agent in each of these Network Nodes.
> So, the comment of 'one per network' is like we can have one
> router/gateway per tenant network.
> Can you give us your comments on this.
> bye,
> balaji
>
> On Wed, Oct 31, 2012 at 10:38 AM, balaji patnala <patnala003 at gmail.com
> <mailto:patnala003 at gmail.com>> 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 understand what will be the advantages we are
> thinking of by doing so.
> 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
>
>
>
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack at lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help : https://help.launchpad.net/ListHelp
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack/attachments/20121110/b73b4dd4/attachment.html>
More information about the Openstack
mailing list