[openstack-dev] Neutron -- creating networks with no assigned tenant
nachi at ntti3.com
Tue Jul 16 19:30:15 UTC 2013
I agree for that usecase is needed.
# But some users wan't to setup their own networks, so this case
usecase will be also exists.
This function needes keystone notification bp (and it looks targeted for H3).
I'm not sure this kind of function should be in Neutron or not.
IMO, if there is some kind of orchestrator, it is best.
2013/7/16 Jay Pipes <jaypipes at gmail.com>:
> On 07/16/2013 02:03 PM, Nachi Ueno wrote:
>> Hi Jay
>> It is not supported now, and there is no bp proposed to do that.
>> It can be done via API (CLI), so we can write a script for tenant setup.
> Hi Nachi,
> IMO, this is a step backwards and a deficiency. Basically, the user
> interface was needlessly made more complicated for the tenant. Instead of
> just launching their instance, the tenant now needs to create a subnet and
> then launch their instance, passing the subnet ID in the nova boot command.
>> 2013/7/16 Jay Pipes <jaypipes at gmail.com>:
>>> The way that folsom and nova + nova-network works is that you create a
>>> of unassigned (no tenant assigned to the networks) networks and when a
>>> tenant first launches an instance, nova grabs an available network for
>>> tenant and assigns it to the tenant. Then each instance the tenant spins
>>> after that gets an IP in the specific network it was assigned.
>>> How can I do the same thing with Neutron? I don't want my tenants or an
>>> admin to have to manually create a network in Neutron every time a tenant
>>> OpenStack-dev mailing list
>>> OpenStack-dev at lists.openstack.org
>> OpenStack-dev mailing list
>> OpenStack-dev at lists.openstack.org
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
More information about the OpenStack-dev