Re: [openstack-dev] Compute API (Was Re: [nova][cinder] how to handle AZ bug 1496235?)

2015-09-28 Thread Sylvain Bauza
Le 28/09/2015 16:19, Sean Dague a écrit : On 09/28/2015 10:11 AM, Andrew Laski wrote: On 09/28/15 at 08:50am, Monty Taylor wrote: On 09/28/2015 07:58 AM, Sylvain Bauza wrote: Specifically, I want "nova boot" to get me a VM with an IP address. I don't want it to do fancy orchestration - I

Re: [openstack-dev] Compute API (Was Re: [nova][cinder] how to handle AZ bug 1496235?)

2015-09-28 Thread Andrew Laski
On 09/28/15 at 10:19am, Sean Dague wrote: On 09/28/2015 10:11 AM, Andrew Laski wrote: On 09/28/15 at 08:50am, Monty Taylor wrote: On 09/28/2015 07:58 AM, Sylvain Bauza wrote: Specifically, I want "nova boot" to get me a VM with an IP address. I don't want it to do fancy orchestration - I

Re: [openstack-dev] Compute API (Was Re: [nova][cinder] how to handle AZ bug 1496235?)

2015-09-28 Thread Mike Spreitzer
> From: Monty Taylor <mo...@inaugust.com> > To: Sylvain Bauza <sba...@redhat.com>, "OpenStack Development > Mailing List (not for usage questions)" <openstack-dev@lists.openstack.org> > Date: 09/28/2015 09:54 AM > Subject: Re: [openstack-dev] Compute

Re: [openstack-dev] Compute API (Was Re: [nova][cinder] how to handle AZ bug 1496235?)

2015-09-28 Thread Ryan Brown
On 09/26/2015 12:04 AM, Joshua Harlow wrote: +1 from me, although I thought heat was supposed to be this thing? Maybe there should be a 'warm' project or something ;) Or we can call it 'bbs' for 'building block service' (obviously not bulletin board system); ask said service to build a set of

Re: [openstack-dev] Compute API (Was Re: [nova][cinder] how to handle AZ bug 1496235?)

2015-09-28 Thread Andrew Laski
On 09/28/15 at 08:50am, Monty Taylor wrote: On 09/28/2015 07:58 AM, Sylvain Bauza wrote: Le 28/09/2015 12:35, Duncan Thomas a écrit : On 28 September 2015 at 12:35, Sylvain Bauza > wrote: About the maintenance burden, I also consider that

Re: [openstack-dev] Compute API (Was Re: [nova][cinder] how to handle AZ bug 1496235?)

2015-09-28 Thread Sean Dague
On 09/28/2015 10:11 AM, Andrew Laski wrote: > On 09/28/15 at 08:50am, Monty Taylor wrote: >> On 09/28/2015 07:58 AM, Sylvain Bauza wrote: >> >> Specifically, I want "nova boot" to get me a VM with an IP address. I >> don't want it to do fancy orchestration - I want it to not need fancy >>

Re: [openstack-dev] Compute API (Was Re: [nova][cinder] how to handle AZ bug 1496235?)

2015-09-28 Thread Sylvain Bauza
Le 25/09/2015 16:12, Andrew Laski a écrit : On 09/24/15 at 03:13pm, James Penick wrote: At risk of getting too offtopic I think there's an alternate solution to doing this in Nova or on the client side. I think we're missing some sort of OpenStack API and service that can handle this.

Re: [openstack-dev] Compute API (Was Re: [nova][cinder] how to handle AZ bug 1496235?)

2015-09-28 Thread Sylvain Bauza
Le 28/09/2015 11:23, Duncan Thomas a écrit : The trouble with putting more intelligence in the clients is that there are more clients than just the one we provide, and the more smarts we require in the clients, the more divergence of functionality we're likely to see. Also, bugs and slowly

Re: [openstack-dev] Compute API (Was Re: [nova][cinder] how to handle AZ bug 1496235?)

2015-09-28 Thread Duncan Thomas
On 28 September 2015 at 12:35, Sylvain Bauza wrote: > About the maintenance burden, I also consider that patching clients is far > more easier than patching an API unless I missed something. > > I think I very much disagree there - patching a central installation is much, much

Re: [openstack-dev] Compute API (Was Re: [nova][cinder] how to handle AZ bug 1496235?)

2015-09-28 Thread Duncan Thomas
The trouble with putting more intelligence in the clients is that there are more clients than just the one we provide, and the more smarts we require in the clients, the more divergence of functionality we're likely to see. Also, bugs and slowly percolating bug fixes. On 28 Sep 2015 11:27,

Re: [openstack-dev] Compute API (Was Re: [nova][cinder] how to handle AZ bug 1496235?)

2015-09-28 Thread James Penick
>I see a clear line between something that handles the creation of all ancillary resources needed to boot a VM and then the creation of the VM itself. I agree. To me the line is the difference between creating a top level resource, and adding a host to that resource. For example, I do expect a

Re: [openstack-dev] Compute API (Was Re: [nova][cinder] how to handle AZ bug 1496235?)

2015-09-28 Thread Sylvain Bauza
Le 28/09/2015 12:35, Duncan Thomas a écrit : On 28 September 2015 at 12:35, Sylvain Bauza > wrote: About the maintenance burden, I also consider that patching clients is far more easier than patching an API unless I missed

Re: [openstack-dev] Compute API (Was Re: [nova][cinder] how to handle AZ bug 1496235?)

2015-09-28 Thread Monty Taylor
On 09/28/2015 07:58 AM, Sylvain Bauza wrote: Le 28/09/2015 12:35, Duncan Thomas a écrit : On 28 September 2015 at 12:35, Sylvain Bauza > wrote: About the maintenance burden, I also consider that patching clients is far more easier than

Re: [openstack-dev] Compute API (Was Re: [nova][cinder] how to handle AZ bug 1496235?)

2015-09-26 Thread Duncan Thomas
On 26 September 2015 at 07:04, Joshua Harlow wrote: > Maybe there should be a 'warm' project or something ;) > > Or we can call it 'bbs' for 'building block service' (obviously not > bulletin board system); ask said service to build a set of blocks into well > defined

Re: [openstack-dev] Compute API (Was Re: [nova][cinder] how to handle AZ bug 1496235?)

2015-09-25 Thread Duncan Thomas
I think there's a place for yet another service breakout from nova - some sort of like-weight platform orchestration piece, nothing as complicated or complete as heat, nothing that touches the inside of a VM, just something that can talk to cinder, nova and neutron (plus I guess ironic and

Re: [openstack-dev] Compute API (Was Re: [nova][cinder] how to handle AZ bug 1496235?)

2015-09-25 Thread Joshua Harlow
+1 from me, although I thought heat was supposed to be this thing? Maybe there should be a 'warm' project or something ;) Or we can call it 'bbs' for 'building block service' (obviously not bulletin board system); ask said service to build a set of blocks into well defined structures and let

Re: [openstack-dev] Compute API (Was Re: [nova][cinder] how to handle AZ bug 1496235?)

2015-09-25 Thread Sylvain Bauza
Le 25/09/2015 00:13, James Penick a écrit : At risk of getting too offtopic I think there's an alternate solution to doing this in Nova or on the client side. I think we're missing some sort of OpenStack API and service that can handle this. Nova is a low level

Re: [openstack-dev] Compute API (Was Re: [nova][cinder] how to handle AZ bug 1496235?)

2015-09-25 Thread Andrew Laski
On 09/24/15 at 03:13pm, James Penick wrote: At risk of getting too offtopic I think there's an alternate solution to doing this in Nova or on the client side. I think we're missing some sort of OpenStack API and service that can handle this. Nova is a low level infrastructure API and

[openstack-dev] Compute API (Was Re: [nova][cinder] how to handle AZ bug 1496235?)

2015-09-24 Thread James Penick
> > > At risk of getting too offtopic I think there's an alternate solution to > doing this in Nova or on the client side. I think we're missing some sort > of OpenStack API and service that can handle this. Nova is a low level > infrastructure API and service, it is not designed to handle these