[Openstack] how to configure l3_agent when you have Per-tenant Routers !

Skible OpenStack skible.openstack at gmail.com
Mon Nov 12 14:21:07 UTC 2012


This means that each tenant router should be linked to the external 
network router ? is that what you mean Logan ?
Le 12/11/2012 15:10, Logan_McLeod at Dell.com a écrit :
>
> You have to create multiple routers.  You have one provider level 
> router that will be your external network router, You can then create 
> a router either for each tenant or for all tenants to support the 
> internal network depending on your needs/topology.
>
> *Logan *
>
> *From:*openstack-bounces+logan_mcleod=dell.com at lists.launchpad.net 
> [mailto:openstack-bounces+logan_mcleod=dell.com at lists.launchpad.net] 
> *On Behalf Of *Emilien Macchi
> *Sent:* Monday, November 12, 2012 3:58 AM
> *To:* Skible OpenStack
> *Cc:* openstack at lists.launchpad.net
> *Subject:* Re: [Openstack] how to configure l3_agent when you have 
> Per-tenant Routers !
>
> Hi,
>
> I suggest you reading my script [1] which helps to create virtual 
> networking in Folsom with OVS Plugin for you use case.
>
> [1] 
> https://github.com/EmilienM/openstack-folsom-guide/blob/master/scripts/quantum-networking.sh 
> <http://[1]%20https:/github.com/EmilienM/openstack-folsom-guide/blob/master/scripts/quantum-networking.sh>
>
>
> Regards,
>
> Emilien Macchi
> ----------------------------------------------------
> // eNovance Inc. http://enovance.com
> // ?emilien at enovance.com <mailto:emilien at enovance.com> ?+33 (0)1 49 70 
> 99 80
> // 10 rue de la Victoire 75009 Paris
>
> ------------------------------------------------------------------------
>
> *De: *"Skible OpenStack" <skible.openstack at gmail.com>
> *À: *"gong yong sheng" <gongysh at linux.vnet.ibm.com>
> *Cc: *openstack at lists.launchpad.net
> *Envoyé: *Lundi 12 Novembre 2012 06:12:15
> *Objet: *Re: [Openstack] how to configure l3_agent when you have 
> Per-tenant Routers !
>
> Thank you for responding back but i think when you configure the l3 
> agent to use one router the other tenant won't be able to connect to 
> internet because their routers are not configured !
> i repeat : i wish to have a router for each of my tenants and they all 
> connect to the internet
> Le 12/11/2012 01:31, gong yong sheng a écrit :
>
>     There is a router_id in l3_agent.ini, You can create a router for
>     a tenant and then start a l3 agent for it.
>     On 11/11/2012 01:34 AM, Skible OpenStack wrote:
>
>         https://github.com/mseknibilel/OpenStack-Folsom-Install-guide/blob/GRE-Tunneling/OpenStack_Folsom_Install_Guide_WebVersion.rst
>
>         i have set my namespace in l3 agent and dhcp agent to true.
>         set external network id to my external network id in the l3
>         agent file
>
>         do i need to run multiple l3 agents to have the per tenant
>         router usecase ?
>
>         Le 10/11/2012 18:29, Razique Mahroua a écrit :
>
>             Hey there,
>
>             which guide did you followed ?
>
>             *Nuage & Co - Razique Mahroua *
>
>             razique.mahroua at gmail.com <mailto:razique.mahroua at gmail.com>
>
>
>             Le 10 nov. 2012 à 17:57, Skible OpenStack
>             <skible.openstack at gmail.com
>             <mailto:skible.openstack at gmail.com>> a écrit :
>
>                 Hello,
>
>                 I am having trouble configuring my l3 agent when i
>                 have a quantum router for each of my tenants. None of
>                 my VMs seem to be internet accessible !
>                 However, It seems that i can only use one router and
>                 set the router_id in the l3_agent to allow VMs access
>                 to internet !
>
>                 please help
>
>                 _______________________________________________
>                 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/20121112/52a9bb1b/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/jpeg
Size: 10122 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack/attachments/20121112/52a9bb1b/attachment.jpe>


More information about the Openstack mailing list