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
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
Hi Jay
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).
https://blueprints.launchpad.net/keystone/+spec/notifications
I'm not sure this
Hi Jay
IMO, you are mixing 'What' and How.
This is my understandings.
What is needed (Requirement)
[Requirement1] Network and Subnet will be assigned for new tenant
automatically
by the configuration
How to do it (Implementation)
- [nova-network] PreCreate list of networks which
