openstack team mailing list archive

[Édouard Thuleau <thuleau@xxxxxxxxx>]

Yes, the provider network provide a way for that use case.

And I proposed a blueprint [1] to be able to isolate ports on a same
network/subnet.
So in you case, if you set a provider network as a public network and if
you like to share this network between tenants, you will be able to isolate
l2 traffic between ports on this network to respond to classical security
constraints (isolation between tenants).

[1] https://blueprints.launchpad.net/quantum/+spec/isolated-network

Édouard.


On Thu, May 30, 2013 at 8:07 AM, Aaron Rosen <arosen@xxxxxxxxxx> wrote:

> No but the provider network extention does provide a way to do this that
> might work for your usecase:
> http://docs.openstack.org/trunk/openstack-network/admin/content/provider_networks.html
>
>
> On Wed, May 29, 2013 at 11:02 PM, Veera Reddy <veeraready@xxxxxxxxx>wrote:
>
>> Hi,
>>
>> IS there any way to access VM from external network without using quantum
>> l3 agent.
>>
>> --
>> Regards,
>> VeeraReddy.B
>>
>>
>> _______________________________________________
>> Mailing list: https://launchpad.net/~openstack
>> Post to     : openstack@xxxxxxxxxxxxxxxxxxx
>> Unsubscribe : https://launchpad.net/~openstack
>> More help   : https://help.launchpad.net/ListHelp
>>
>>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to     : openstack@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
>