On Wed, 2014-12-03 at 02:08 -0800, Kevin Benton wrote:
There is a current blueprint under discussion[1] which would have
covered the external network access control as well, however it looks
like the scope is going to have to be reduced for this cycle so it
will be limited to shared networks
Hi,
I'm picking up this thread from a few months ago, as I have a
requirement for a private external network and after doing some testing
today came to the conclusion that this isn't currently possible. Rats.
On Tue, 2014-10-14 at 17:42 +, A, Keshava wrote:
Hi,
Across these private
There is a current blueprint under discussion[1] which would have covered
the external network access control as well, however it looks like the
scope is going to have to be reduced for this cycle so it will be limited
to shared networks if it's accepted at all.
1.
Hi Salvatore,
I like to propose a blueprint for the next Neutron release that permits to
dedicated an external network to a tenant. For that I though to rethink the
he conjunction of the two attributes `shared`
and `router:external' of the network resource.
I saw that you already initiate a work
The blueprint was untargeted mostly because the analysis indicated that
there was no easy solution, and that what we needed was a solution to do
some RBAC on neutron resources.
I think this would be a good addition to the Neutron resource model, and it
would be great if you could start the
Hi,
Across these private External network/tenant :: floating IP can be shared ?
Keshava
From: Salvatore Orlando [mailto:sorla...@nicira.com]
Sent: Tuesday, October 14, 2014 10:33 PM
To: Édouard Thuleau
Cc: OpenStack Development Mailing List
Subject: Re: [openstack-dev] [neutron] Private
