Open Stack

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.

-jay

> 2013/7/16 Jay Pipes <jaypipes at gmail.com>:
>> The way that folsom and nova + nova-network works is that you create a bunch
>> of unassigned (no tenant assigned to the networks) networks and when a
>> tenant first launches an instance, nova grabs an available network for the
>> tenant and assigns it to the tenant. Then each instance the tenant spins up
>> 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 is
>> added.
>>
>> Thanks,
>> -jay
>>
>> _______________________________________________
>> OpenStack-dev mailing list
>> OpenStack-dev at lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>