Re: [openstack-dev] [nova][neutron] How would nova microversion get-me-a-network in the API?

On 2/22/2016 2:27 PM, Sean Dague wrote: On 02/22/2016 02:50 PM, Andrew Laski wrote: On Mon, Feb 22, 2016, at 02:42 PM, Matt Riedemann wrote: On 2/22/2016 5:56 AM, Sean Dague wrote: On 02/19/2016 12:49 PM, John Garbutt wrote: Consider a user that uses these four clouds: * nova-network

Re: [openstack-dev] [nova][neutron] How would nova microversion get-me-a-network in the API?

On Mon, Feb 22, 2016, at 02:42 PM, Matt Riedemann wrote: > > > On 2/22/2016 5:56 AM, Sean Dague wrote: > > On 02/19/2016 12:49 PM, John Garbutt wrote: > > > >> > >> Consider a user that uses these four clouds: > >> * nova-network flat DHCP > >> * nova-network VLAN manager > >> * neutron with

Re: [openstack-dev] [nova][neutron] How would nova microversion get-me-a-network in the API?

On 2/22/2016 5:56 AM, Sean Dague wrote: On 02/19/2016 12:49 PM, John Garbutt wrote: Consider a user that uses these four clouds: * nova-network flat DHCP * nova-network VLAN manager * neutron with a single provider network setup * neutron where user needs to create their own network For

Re: [openstack-dev] [nova][neutron] How would nova microversion get-me-a-network in the API?

On 22 February 2016 at 15:14, John Garbutt wrote: > On 22 February 2016 at 12:01, Jay Pipes wrote: >> On 02/22/2016 06:56 AM, Sean Dague wrote: >>> On 02/19/2016 12:49 PM, John Garbutt wrote: >>> Consider a user that uses these four clouds: *

Re: [openstack-dev] [nova][neutron] How would nova microversion get-me-a-network in the API?

On 22 February 2016 at 12:01, Jay Pipes wrote: > On 02/22/2016 06:56 AM, Sean Dague wrote: >> On 02/19/2016 12:49 PM, John Garbutt wrote: >> >>> Consider a user that uses these four clouds: >>> * nova-network flat DHCP >>> * nova-network VLAN manager >>> * neutron with a

Re: [openstack-dev] [nova][neutron] How would nova microversion get-me-a-network in the API?

On Mon, Feb 22, 2016, at 07:07 AM, Chris Dent wrote: > On Mon, 22 Feb 2016, Sean Dague wrote: > > > that being said... I think the behavior of CLI tools should default to > > nic auto being implied. The user experience there is different. You use > > cli tools for one off boots of things, so

Re: [openstack-dev] [nova][neutron] How would nova microversion get-me-a-network in the API?

On Mon, 22 Feb 2016, Sean Dague wrote: that being said... I think the behavior of CLI tools should default to nic auto being implied. The user experience there is different. You use cli tools for one off boots of things, so should be as easy as possible. Thanks Sean, throughout this entire

Re: [openstack-dev] [nova][neutron] How would nova microversion get-me-a-network in the API?

On 02/22/2016 06:56 AM, Sean Dague wrote: On 02/19/2016 12:49 PM, John Garbutt wrote: Consider a user that uses these four clouds: * nova-network flat DHCP * nova-network VLAN manager * neutron with a single provider network setup * neutron where user needs to create their own network For

Re: [openstack-dev] [nova][neutron] How would nova microversion get-me-a-network in the API?

On 02/19/2016 12:49 PM, John Garbutt wrote: > > Consider a user that uses these four clouds: > * nova-network flat DHCP > * nova-network VLAN manager > * neutron with a single provider network setup > * neutron where user needs to create their own network > > For the first three, the user

Re: [openstack-dev] [nova][neutron] How would nova microversion get-me-a-network in the API?

Sorry for chiming in late. It sounds natural to me that when no --nic option is specified and no neutron network exists 'get-me-a-network' feature is used. After a network for a project is created by a get-me-a-network or when a project already has one network, a user do not need to specify --nic

Re: [openstack-dev] [nova][neutron] How would nova microversion get-me-a-network in the API?

On 2016-02-19 19:06:17 -0800 (-0800), Armando M. wrote: [...] > In fact, if we continue to keep --nic an optional parameter, we > can reconcile the behavior between nova-net and neutron (which is > really the win here - make different clouds behave alike). [...] Restated, Nova network feature

Re: [openstack-dev] [nova][neutron] How would nova microversion get-me-a-network in the API?

On 19 February 2016 at 09:49, John Garbutt wrote: > On 19 February 2016 at 16:28, Andrew Laski wrote: > > On Fri, Feb 19, 2016, at 11:14 AM, Sean Dague wrote: > >> On 02/19/2016 09:30 AM, Andrew Laski wrote: > >> > > >> > > >> > On Thu, Feb 18, 2016, at

Re: [openstack-dev] [nova][neutron] How would nova microversion get-me-a-network in the API?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 02/19/2016 11:49 AM, John Garbutt wrote: > Now, if we step back and created this again, I would agree that > --nic=auto is a good idea, so its explicit. However, all our users > are used to automatic being the default, all be it a very patchy >

Re: [openstack-dev] [nova][neutron] How would nova microversion get-me-a-network in the API?

On 19 February 2016 at 16:28, Andrew Laski wrote: > On Fri, Feb 19, 2016, at 11:14 AM, Sean Dague wrote: >> On 02/19/2016 09:30 AM, Andrew Laski wrote: >> > >> > >> > On Thu, Feb 18, 2016, at 05:34 PM, melanie witt wrote: >> >> On Feb 12, 2016, at 14:49, Jay Pipes

Re: [openstack-dev] [nova][neutron] How would nova microversion get-me-a-network in the API?

On Fri, Feb 19, 2016, at 11:14 AM, Sean Dague wrote: > On 02/19/2016 09:30 AM, Andrew Laski wrote: > > > > > > On Thu, Feb 18, 2016, at 05:34 PM, melanie witt wrote: > >> On Feb 12, 2016, at 14:49, Jay Pipes wrote: > >> > >>> This would be my preference as well, even

Re: [openstack-dev] [nova][neutron] How would nova microversion get-me-a-network in the API?

On 02/19/2016 09:30 AM, Andrew Laski wrote: > > > On Thu, Feb 18, 2016, at 05:34 PM, melanie witt wrote: >> On Feb 12, 2016, at 14:49, Jay Pipes wrote: >> >>> This would be my preference as well, even though it's technically a >>> backwards-incompatible API change. >>> >>>

Re: [openstack-dev] [nova][neutron] How would nova microversion get-me-a-network in the API?

On Thu, Feb 18, 2016, at 05:34 PM, melanie witt wrote: > On Feb 12, 2016, at 14:49, Jay Pipes wrote: > > > This would be my preference as well, even though it's technically a > > backwards-incompatible API change. > > > > The idea behind get-me-a-network was specifically

Re: [openstack-dev] [nova][neutron] How would nova microversion get-me-a-network in the API?

On Feb 12, 2016, at 14:49, Jay Pipes wrote: > This would be my preference as well, even though it's technically a > backwards-incompatible API change. > > The idea behind get-me-a-network was specifically to remove the current > required complexity of the nova boot command

Re: [openstack-dev] [nova][neutron] How would nova microversion get-me-a-network in the API?

enstack.org>> Date: Monday, February 15, 2016 at 7:06 AM To: OpenStack List <openstack-dev@lists.openstack.org <mailto:openstack-dev@lists.openstack.org>> Subject: Re: [openstack-dev] [nova][neutron] How would nova microversion get-me-a-network in the API? May I ask can we pu

Re: [openstack-dev] [nova][neutron] How would nova microversion get-me-a-network in the API?

On Fri, 12 Feb 2016, Doug Wiegley wrote: It hurts discoverability, and “expectedness”. If I’m new to openstack, having it default boot unusable just means the first time I use ’nova boot’, I’ll end up with a useless VM. People don’t read docs first, it should “just work” as far as that’s sane.

Re: [openstack-dev] [nova][neutron] How would nova microversion get-me-a-network in the API?

uary 15, 2016 at 7:06 AM To: OpenStack List <openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>> Subject: Re: [openstack-dev] [nova][neutron] How would nova microversion get-me-a-network in the API? May I ask can we put those thing in to the CLI? I guess there s

Re: [openstack-dev] [nova][neutron] How would nova microversion get-me-a-network in the API?

2016-02-13 19:05 GMT+08:00 Andrew Laski : > > > On Fri, Feb 12, 2016, at 03:51 PM, Ed Leafe wrote: > > -BEGIN PGP SIGNED MESSAGE- > > Hash: SHA512 > > > > On 02/12/2016 02:41 PM, Andrew Laski wrote: > > > > >> I think if the point of the experience for this API is to be

Re: [openstack-dev] [nova][neutron] How would nova microversion get-me-a-network in the API?

May I ask can we put those thing in to the CLI? I guess there should have similar discussion and I missed. As we didn't want to provide more neutron API proxy, this works sounds like adding more proxy. And API is more simple and more flexible, this make the API have more complex behaviour. Just

Re: [openstack-dev] [nova][neutron] How would nova microversion get-me-a-network in the API?

On 2/14/16, 3:59 PM, "Ken'ichi Ohmichi" wrote: >2016-02-12 11:19 GMT-08:00 Andrew Laski : >> On Fri, Feb 12, 2016, at 01:45 PM, John Garbutt wrote: >>> On 12 February 2016 at 18:17, Andrew Laski wrote: >>> > >>> > >>> > On Fri, Feb

Re: [openstack-dev] [nova][neutron] How would nova microversion get-me-a-network in the API?

On Fri, Feb 12, 2016, at 03:51 PM, Ed Leafe wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA512 > > On 02/12/2016 02:41 PM, Andrew Laski wrote: > > >> I think if the point of the experience for this API is to be > >> working out > >>> of the box. So I very much like the idea of a

[openstack-dev] [nova][neutron] How would nova microversion get-me-a-network in the API?

Forgive me for thinking out loud, but I'm trying to sort out how nova would use a microversion in the nova API for the get-me-a-network feature recently added to neutron [1] and planned to be leveraged in nova (there isn't a spec yet for nova, I'm trying to sort this out for a draft).

Re: [openstack-dev] [nova][neutron] How would nova microversion get-me-a-network in the API?

On 12 February 2016 at 18:17, Andrew Laski wrote: > > > On Fri, Feb 12, 2016, at 12:15 PM, Matt Riedemann wrote: >> Forgive me for thinking out loud, but I'm trying to sort out how nova >> would use a microversion in the nova API for the get-me-a-network >> feature recently

Re: [openstack-dev] [nova][neutron] How would nova microversion get-me-a-network in the API?

Perhaps another option for '--nic'? nova boot --nic auto-allocate On Fri, Feb 12, 2016 at 10:17 AM, Andrew Laski wrote: > > > On Fri, Feb 12, 2016, at 12:15 PM, Matt Riedemann wrote: > > Forgive me for thinking out loud, but I'm trying to sort out how nova > > would use a

Re: [openstack-dev] [nova][neutron] How would nova microversion get-me-a-network in the API?

On 2/12/2016 12:45 PM, John Garbutt wrote: On 12 February 2016 at 18:17, Andrew Laski wrote: On Fri, Feb 12, 2016, at 12:15 PM, Matt Riedemann wrote: Forgive me for thinking out loud, but I'm trying to sort out how nova would use a microversion in the nova API for the

Re: [openstack-dev] [nova][neutron] How would nova microversion get-me-a-network in the API?

On Fri, Feb 12, 2016, at 01:45 PM, John Garbutt wrote: > On 12 February 2016 at 18:17, Andrew Laski wrote: > > > > > > On Fri, Feb 12, 2016, at 12:15 PM, Matt Riedemann wrote: > >> Forgive me for thinking out loud, but I'm trying to sort out how nova > >> would use a

Re: [openstack-dev] [nova][neutron] How would nova microversion get-me-a-network in the API?

> On Feb 12, 2016, at 12:03 PM, Matt Riedemann > wrote: > > > > On 2/12/2016 12:45 PM, John Garbutt wrote: >> On 12 February 2016 at 18:17, Andrew Laski wrote: >>> >>> >>> On Fri, Feb 12, 2016, at 12:15 PM, Matt Riedemann wrote: Forgive

Re: [openstack-dev] [nova][neutron] How would nova microversion get-me-a-network in the API?

On 12 February 2016 at 09:15, Matt Riedemann wrote: > Forgive me for thinking out loud, but I'm trying to sort out how nova > would use a microversion in the nova API for the get-me-a-network feature > recently added to neutron [1] and planned to be leveraged in nova

Re: [openstack-dev] [nova][neutron] How would nova microversion get-me-a-network in the API?

On 2/12/2016 12:44 PM, Armando M. wrote: On 12 February 2016 at 09:15, Matt Riedemann > wrote: Forgive me for thinking out loud, but I'm trying to sort out how nova would use a microversion in the nova API for the

Re: [openstack-dev] [nova][neutron] How would nova microversion get-me-a-network in the API?

On 12 February 2016 at 11:08, Matt Riedemann wrote: > > > On 2/12/2016 12:44 PM, Armando M. wrote: > >> >> >> On 12 February 2016 at 09:15, Matt Riedemann > > wrote: >> >> Forgive me for thinking out

Re: [openstack-dev] [nova][neutron] How would nova microversion get-me-a-network in the API?

On 02/12/2016 02:19 PM, Andrew Laski wrote: > > > On Fri, Feb 12, 2016, at 01:45 PM, John Garbutt wrote: >> On 12 February 2016 at 18:17, Andrew Laski wrote: >>> >>> >>> On Fri, Feb 12, 2016, at 12:15 PM, Matt Riedemann wrote: Forgive me for thinking out loud, but I'm

Re: [openstack-dev] [nova][neutron] How would nova microversion get-me-a-network in the API?

> On Feb 12, 2016, at 2:15 PM, Andrew Laski wrote: > > > > On Fri, Feb 12, 2016, at 04:03 PM, Doug Wiegley wrote: >> Correct me if I’m wrong, but with nova-net, ‘nova boot’ automatically >> gives it one nic with an IP, right? >> >> So how is this changing that behavior?

Re: [openstack-dev] [nova][neutron] How would nova microversion get-me-a-network in the API?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 02/12/2016 02:41 PM, Andrew Laski wrote: >> I think if the point of the experience for this API is to be >> working out >>> of the box. So I very much like the idea of a defaults change >>> here to the thing we want to be easy. And an explicit

Re: [openstack-dev] [nova][neutron] How would nova microversion get-me-a-network in the API?

On Fri, Feb 12, 2016, at 04:03 PM, Doug Wiegley wrote: > Correct me if I’m wrong, but with nova-net, ‘nova boot’ automatically > gives it one nic with an IP, right? > > So how is this changing that behavior? Making it harder to use, for the > sake of preserving a really unusual corner case (no

Re: [openstack-dev] [nova][neutron] How would nova microversion get-me-a-network in the API?

On Fri, Feb 12, 2016, at 05:29 PM, Doug Wiegley wrote: > > > On Feb 12, 2016, at 3:17 PM, Andrew Laski wrote: > > > > > > > > On Fri, Feb 12, 2016, at 04:53 PM, Doug Wiegley wrote: > >> > >>> On Feb 12, 2016, at 2:15 PM, Andrew Laski wrote: > >>> >

Re: [openstack-dev] [nova][neutron] How would nova microversion get-me-a-network in the API?

On Fri, Feb 12, 2016, at 03:11 PM, Sean Dague wrote: > On 02/12/2016 02:19 PM, Andrew Laski wrote: > > > > > > On Fri, Feb 12, 2016, at 01:45 PM, John Garbutt wrote: > >> On 12 February 2016 at 18:17, Andrew Laski wrote: > >>> > >>> > >>> On Fri, Feb 12, 2016, at 12:15 PM,

Re: [openstack-dev] [nova][neutron] How would nova microversion get-me-a-network in the API?

Correct me if I’m wrong, but with nova-net, ‘nova boot’ automatically gives it one nic with an IP, right? So how is this changing that behavior? Making it harder to use, for the sake of preserving a really unusual corner case (no net with neutron), seems a much worse user experience here.

Re: [openstack-dev] [nova][neutron] How would nova microversion get-me-a-network in the API?

> On Feb 12, 2016, at 3:17 PM, Andrew Laski wrote: > > > > On Fri, Feb 12, 2016, at 04:53 PM, Doug Wiegley wrote: >> >>> On Feb 12, 2016, at 2:15 PM, Andrew Laski wrote: >>> >>> >>> >>> On Fri, Feb 12, 2016, at 04:03 PM, Doug Wiegley wrote:

Re: [openstack-dev] [nova][neutron] How would nova microversion get-me-a-network in the API?

On 02/12/2016 02:18 PM, Doug Wiegley wrote: I thought one of the original notions behind this was to make ‘nova boot’ as simple as in the nova-net case, which would imply not needing to use —nic at all. I personally like the idea of the flag being for the no network case. This would be my

Re: [openstack-dev] [nova][neutron] How would nova microversion get-me-a-network in the API?

On Fri, Feb 12, 2016, at 04:53 PM, Doug Wiegley wrote: > > > On Feb 12, 2016, at 2:15 PM, Andrew Laski wrote: > > > > > > > > On Fri, Feb 12, 2016, at 04:03 PM, Doug Wiegley wrote: > >> Correct me if I’m wrong, but with nova-net, ‘nova boot’ automatically > >> gives it

Re: [openstack-dev] [nova][neutron] How would nova microversion get-me-a-network in the API?

>plus I think a VM with a network is kinda nonsensical, On the contrary, that's when I find them the most useful! On Feb 12, 2016 14:33, "Doug Wiegley" wrote: > > > On Feb 12, 2016, at 3:17 PM, Andrew Laski wrote: > > > > > > > > On Fri, Feb 12,