On 07/16/2013 06:46 PM, Ian Wells wrote:
On 17 July 2013 00:11, Jay Pipes wrote:
Absolutely, that is what our tools team is now having to do. All I'm saying
is that this wasn't necessary in Folsom and wouldn't be necessary if the API
didn't force networks to be created with a tenant ID.
What'
On 17 July 2013 00:11, Jay Pipes wrote:
> Absolutely, that is what our tools team is now having to do. All I'm saying
> is that this wasn't necessary in Folsom and wouldn't be necessary if the API
> didn't force networks to be created with a tenant ID.
What's wrong with a shared network? It's be
On 07/16/2013 06:09 PM, Rick Jones wrote:
On 07/16/2013 02:56 PM, Jay Pipes wrote:
On 07/16/2013 05:14 PM, Nachi Ueno wrote:
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
On 07/16/2013 02:56 PM, Jay Pipes wrote:
On 07/16/2013 05:14 PM, Nachi Ueno wrote:
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 configur
On 07/16/2013 05:14 PM, Nachi Ueno wrote:
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)"
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 w
On 07/16/2013 03:30 PM, Nachi Ueno wrote:
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/keyst
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 k
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 ma
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.
Best
Nachi
2013/7/16 Jay Pipes :
> The way that folsom and nova + nova-network works is that you create a bunch
> of unassigned (no tenant assigned to
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
11 matches
Mail list logo
