openstack team mailing list archive

[<Logan_McLeod@xxxxxxxx>]

I haven’t tried it yet, but yes.  You should be able to add internal network interfaces from the external router setup to a common internal network to which each of the tenant routers is also connected to.  Setting the external network gateway of the tenant routers to that of the ext_net router should then complete the connection…

Logan
From: openstack-bounces+logan_mcleod=dell.com@xxxxxxxxxxxxxxxxxxx [mailto:openstack-bounces+logan_mcleod=dell.com@xxxxxxxxxxxxxxxxxxx] On Behalf Of Skible OpenStack
Sent: Monday, November 12, 2012 8:21 AM
To: openstack@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Openstack] how to configure l3_agent when you have Per-tenant Routers !

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@xxxxxxxx<mailto:Logan_McLeod@xxxxxxxx> 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@xxxxxxxxxxxxxxxxxxx<mailto:openstack-bounces+logan_mcleod=dell.com@xxxxxxxxxxxxxxxxxxx> [mailto:openstack-bounces+logan_mcleod=dell.com@xxxxxxxxxxxxxxxxxxx] On Behalf Of Emilien Macchi
Sent: Monday, November 12, 2012 3:58 AM
To: Skible OpenStack
Cc: openstack@xxxxxxxxxxxxxxxxxxx<mailto:openstack@xxxxxxxxxxxxxxxxxxx>
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@xxxxxxxxxxxx<mailto:emilien@xxxxxxxxxxxx>     ☎ +33 (0)1 49 70 99 80
// 10 rue de la Victoire 75009 Paris

________________________________
De: "Skible OpenStack" <skible.openstack@xxxxxxxxx><mailto:skible.openstack@xxxxxxxxx>
À: "gong yong sheng" <gongysh@xxxxxxxxxxxxxxxxxx><mailto:gongysh@xxxxxxxxxxxxxxxxxx>
Cc: openstack@xxxxxxxxxxxxxxxxxxx<mailto:openstack@xxxxxxxxxxxxxxxxxxx>
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@xxxxxxxxx<mailto:razique.mahroua@xxxxxxxxx>

[cid:image001.jpg@01CDC0B8.1FD7E350]

Le 10 nov. 2012 à 17:57, Skible OpenStack <skible.openstack@xxxxxxxxx<mailto:skible.openstack@xxxxxxxxx>> 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@xxxxxxxxxxxxxxxxxxx<mailto:openstack@xxxxxxxxxxxxxxxxxxx>
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@xxxxxxxxxxxxxxxxxxx<mailto:openstack@xxxxxxxxxxxxxxxxxxx>

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@xxxxxxxxxxxxxxxxxxx<mailto:openstack@xxxxxxxxxxxxxxxxxxx>
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@xxxxxxxxxxxxxxxxxxx<mailto:openstack@xxxxxxxxxxxxxxxxxxx>

Unsubscribe : https://launchpad.net/~openstack

More help   : https://help.launchpad.net/ListHelp