Re: [openstack-dev] [Heat] rough draft of Heat autoscaling API

Top-posting *and* replying to myself today :D I realised that I could have implemented this in less time than I've spent arguing about it already, so I did: https://review.openstack.org/#/c/58357/ https://review.openstack.org/#/c/58358/ cheers, Zane. On 19/11/13 23:27, Zane Bitter wrote: O

Re: [openstack-dev] [Heat] rough draft of Heat autoscaling API

On Thu, Nov 21, 2013 at 12:18 PM, Zane Bitter wrote: > On 20/11/13 23:49, Christopher Armstrong wrote: >> https://wiki.openstack.org/wiki/Heat/AutoScaling#LBMember.3F >> >> Basically, the LoadBalancerMember resource (which is very similar to the >> CinderVolumeAttachment) would be responsible for

Re: [openstack-dev] [Heat] rough draft of Heat autoscaling API

On Thu, Nov 21, 2013 at 12:31 PM, Zane Bitter wrote: > On 21/11/13 18:44, Christopher Armstrong wrote: > >> >> 2) It relies on a plugin being present for any type of thing you >> might want to notify. >> >> >> I don't understand this point. What do you mean by a plugin? I was >> assuming

Re: [openstack-dev] [Heat] rough draft of Heat autoscaling API

To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [Heat] rough draft of Heat autoscaling API On Thu, Nov 21, 2013 at 5:18 AM, Zane Bitter mailto:zbit...@redhat.com>> wrote: On 20/11/13 23:49, Christopher Armstrong wrote: On Wed, Nov 20, 2013 at 2

Re: [openstack-dev] [Heat] rough draft of Heat autoscaling API

On 21/11/13 18:44, Christopher Armstrong wrote: 2) It relies on a plugin being present for any type of thing you might want to notify. I don't understand this point. What do you mean by a plugin? I was assuming OS::Neutron::PoolMember (not LoadBalancerMember -- I went and looked up the

Re: [openstack-dev] [Heat] rough draft of Heat autoscaling API

On Thu, Nov 21, 2013 at 5:18 AM, Zane Bitter wrote: > On 20/11/13 23:49, Christopher Armstrong wrote: > >> On Wed, Nov 20, 2013 at 2:07 PM, Zane Bitter > > wrote: >> >> On 20/11/13 16:07, Christopher Armstrong wrote: >> >> On Tue, Nov 19, 2013 at 4:27 PM, Za

Re: [openstack-dev] [Heat] rough draft of Heat autoscaling API

On 20/11/13 23:49, Christopher Armstrong wrote: On Wed, Nov 20, 2013 at 2:07 PM, Zane Bitter mailto:zbit...@redhat.com>> wrote: On 20/11/13 16:07, Christopher Armstrong wrote: On Tue, Nov 19, 2013 at 4:27 PM, Zane Bitter mailto:zbit...@redhat.com>

Re: [openstack-dev] [Heat] rough draft of Heat autoscaling API

On Wed, Nov 20, 2013 at 2:07 PM, Zane Bitter wrote: > On 20/11/13 16:07, Christopher Armstrong wrote: > >> On Tue, Nov 19, 2013 at 4:27 PM, Zane Bitter > > wrote: >> >> On 19/11/13 19:14, Christopher Armstrong wrote: >> >> >> >> [snip] >> >> >> >> >> There are a

Re: [openstack-dev] [Heat] rough draft of Heat autoscaling API

On 20/11/13 16:07, Christopher Armstrong wrote: On Tue, Nov 19, 2013 at 4:27 PM, Zane Bitter mailto:zbit...@redhat.com>> wrote: On 19/11/13 19:14, Christopher Armstrong wrote: [snip] There are a number of advantages to including the whole template, rather than a resource snipp

Re: [openstack-dev] [Heat] rough draft of Heat autoscaling API

On Tue, Nov 19, 2013 at 4:27 PM, Zane Bitter wrote: > On 19/11/13 19:14, Christopher Armstrong wrote: > >> >> [snip] >> It'd be interesting to see some examples, I think. I'll provide some >> examples of my proposals, with the following caveats: >> > > Excellent idea, thanks :) > > > - I'm as

Re: [openstack-dev] [Heat] rough draft of Heat autoscaling API

On 19/11/13 19:14, Christopher Armstrong wrote: On Mon, Nov 18, 2013 at 5:57 AM, Zane Bitter mailto:zbit...@redhat.com>> wrote: On 16/11/13 11:15, Angus Salkeld wrote: On 15/11/13 08:46 -0600, Christopher Armstrong wrote: On Fri, Nov 15, 2013 at 3:57 AM, Zane Bitter

Re: [openstack-dev] [Heat] rough draft of Heat autoscaling API

On 11/17/2013 01:57 PM, Steve Baker wrote: On 11/15/2013 05:19 AM, Christopher Armstrong wrote: http://docs.heatautoscale.apiary.io/ I've thrown together a rough sketch of the proposed API for autoscaling. It's written in API-Blueprint format (which is a simple subset of Markdown) and provides

Re: [openstack-dev] [Heat] rough draft of Heat autoscaling API

On Mon, Nov 18, 2013 at 5:57 AM, Zane Bitter wrote: > On 16/11/13 11:15, Angus Salkeld wrote: > >> On 15/11/13 08:46 -0600, Christopher Armstrong wrote: >> >>> On Fri, Nov 15, 2013 at 3:57 AM, Zane Bitter wrote: >>> >>> On 15/11/13 02:48, Christopher Armstrong wrote: On Thu, Nov 14,

Re: [openstack-dev] [Heat] rough draft of Heat autoscaling API

On 18/11/13 12:57 +0100, Zane Bitter wrote: On 16/11/13 11:15, Angus Salkeld wrote: On 15/11/13 08:46 -0600, Christopher Armstrong wrote: On Fri, Nov 15, 2013 at 3:57 AM, Zane Bitter wrote: On 15/11/13 02:48, Christopher Armstrong wrote: On Thu, Nov 14, 2013 at 5:40 PM, Angus Salkeld mailt

Re: [openstack-dev] [Heat] rough draft of Heat autoscaling API

On 15/11/13 21:06, Mike Spreitzer wrote: Zane Bitter wrote on 11/14/2013 12:56:22 PM: > ... > My 2c: the way I designed the Heat API was such that extant stacks can > be addressed uniquely by name. Humans are pretty good with names, not so > much with 128 bit numbers. The consequences of th

Re: [openstack-dev] [Heat] rough draft of Heat autoscaling API

On 16/11/13 11:15, Angus Salkeld wrote: On 15/11/13 08:46 -0600, Christopher Armstrong wrote: On Fri, Nov 15, 2013 at 3:57 AM, Zane Bitter wrote: On 15/11/13 02:48, Christopher Armstrong wrote: On Thu, Nov 14, 2013 at 5:40 PM, Angus Salkeld mailto:asalk...@redhat.com>> wrote: On 14/11/

Re: [openstack-dev] [Heat] rough draft of Heat autoscaling API

On 16/11/13 11:11, Angus Salkeld wrote: On 15/11/13 16:32 +0100, Zane Bitter wrote: On 14/11/13 19:53, Christopher Armstrong wrote: I'm a little unclear as to what point you're making here. Right now, the "launch configuration" is specified in the scaling group by the "resources" property of th

Re: [openstack-dev] [Heat] rough draft of Heat autoscaling API

On 17/11/13 21:57, Steve Baker wrote: On 11/15/2013 05:19 AM, Christopher Armstrong wrote: http://docs.heatautoscale.apiary.io/ I've thrown together a rough sketch of the proposed API for autoscaling. It's written in API-Blueprint format (which is a simple subset of Markdown) and provides schem

Re: [openstack-dev] [Heat] rough draft of Heat autoscaling API

On 11/18/2013 01:03 PM, Christopher Armstrong wrote: > On Sun, Nov 17, 2013 at 2:57 PM, Steve Baker > wrote: > > On 11/15/2013 05:19 AM, Christopher Armstrong wrote: > > http://docs.heatautoscale.apiary.io/ > > > > I've thrown together a rough sketch of th

Re: [openstack-dev] [Heat] rough draft of Heat autoscaling API

On Sun, Nov 17, 2013 at 2:57 PM, Steve Baker wrote: > On 11/15/2013 05:19 AM, Christopher Armstrong wrote: > > http://docs.heatautoscale.apiary.io/ > > > > I've thrown together a rough sketch of the proposed API for > > autoscaling. It's written in API-Blueprint format (which is a simple > > subs

Re: [openstack-dev] [Heat] rough draft of Heat autoscaling API

On 11/15/2013 05:19 AM, Christopher Armstrong wrote: > http://docs.heatautoscale.apiary.io/ > > I've thrown together a rough sketch of the proposed API for > autoscaling. It's written in API-Blueprint format (which is a simple > subset of Markdown) and provides schemas for inputs and outputs using

Re: [openstack-dev] [Heat] rough draft of Heat autoscaling API

On 11/15/2013 05:19 AM, Christopher Armstrong wrote: > http://docs.heatautoscale.apiary.io/ > > I've thrown together a rough sketch of the proposed API for > autoscaling. It's written in API-Blueprint format (which is a simple > subset of Markdown) and provides schemas for inputs and outputs using

Re: [openstack-dev] [Heat] rough draft of Heat autoscaling API

On 15/11/13 08:46 -0600, Christopher Armstrong wrote: On Fri, Nov 15, 2013 at 3:57 AM, Zane Bitter wrote: On 15/11/13 02:48, Christopher Armstrong wrote: On Thu, Nov 14, 2013 at 5:40 PM, Angus Salkeld mailto:asalk...@redhat.com>> wrote: On 14/11/13 10:19 -0600, Christopher Armstrong wro

Re: [openstack-dev] [Heat] rough draft of Heat autoscaling API

On 15/11/13 16:32 +0100, Zane Bitter wrote: On 14/11/13 19:53, Christopher Armstrong wrote: Thanks for the comments, Zane. On Thu, Nov 14, 2013 at 9:56 AM, Zane Bitter mailto:zbit...@redhat.com>> wrote: A few comments... #1 thing is that the launch configuration needs to be somehow r

Re: [openstack-dev] [Heat] rough draft of Heat autoscaling API

Zane Bitter wrote on 11/14/2013 12:56:22 PM: > ... > My 2c: the way I designed the Heat API was such that extant stacks can > be addressed uniquely by name. Humans are pretty good with names, not so > much with 128 bit numbers. The consequences of this for the design were: > - names must be

Re: [openstack-dev] [Heat] rough draft of Heat autoscaling API

On 14/11/13 19:53, Christopher Armstrong wrote: Thanks for the comments, Zane. On Thu, Nov 14, 2013 at 9:56 AM, Zane Bitter mailto:zbit...@redhat.com>> wrote: A few comments... #1 thing is that the launch configuration needs to be somehow represented. In general we want the launch

Re: [openstack-dev] [Heat] rough draft of Heat autoscaling API

On Fri, Nov 15, 2013 at 4:16 AM, Zane Bitter wrote: > On 14/11/13 19:58, Christopher Armstrong wrote: > >> On Thu, Nov 14, 2013 at 10:44 AM, Zane Bitter > > wrote: >> >> On 14/11/13 18:51, Randall Burt wrote: >> >> Perhaps, but I also miss important informat

Re: [openstack-dev] [Heat] rough draft of Heat autoscaling API

On Fri, Nov 15, 2013 at 3:57 AM, Zane Bitter wrote: > On 15/11/13 02:48, Christopher Armstrong wrote: > >> On Thu, Nov 14, 2013 at 5:40 PM, Angus Salkeld > > wrote: >> >> On 14/11/13 10:19 -0600, Christopher Armstrong wrote: >> >> http://docs.heatautoscale.

Re: [openstack-dev] [Heat] rough draft of Heat autoscaling API

On 15/11/13 11:58, Steven Hardy wrote: On Fri, Nov 15, 2013 at 11:16:19AM +0100, Zane Bitter wrote: On 14/11/13 19:58, Christopher Armstrong wrote: On 14/11/13 18:51, Randall Burt wrote: Perhaps, but I also miss important information as a legitimate caller as to whe

Re: [openstack-dev] [Heat] rough draft of Heat autoscaling API

On Fri, Nov 15, 2013 at 11:16:19AM +0100, Zane Bitter wrote: > On 14/11/13 19:58, Christopher Armstrong wrote: > >On 14/11/13 18:51, Randall Burt wrote: > > > >Perhaps, but I also miss important information as a legitimate > >caller as > >to whether or not my scaling act

Re: [openstack-dev] [Heat] rough draft of Heat autoscaling API

On 14/11/13 19:58, Christopher Armstrong wrote: On Thu, Nov 14, 2013 at 10:44 AM, Zane Bitter mailto:zbit...@redhat.com>> wrote: On 14/11/13 18:51, Randall Burt wrote: Perhaps, but I also miss important information as a legitimate caller as to whether or not my scali

Re: [openstack-dev] [Heat] rough draft of Heat autoscaling API

On 15/11/13 02:48, Christopher Armstrong wrote: On Thu, Nov 14, 2013 at 5:40 PM, Angus Salkeld mailto:asalk...@redhat.com>> wrote: On 14/11/13 10:19 -0600, Christopher Armstrong wrote: http://docs.heatautoscale.__apiary.io/ I'v

Re: [openstack-dev] [Heat] rough draft of Heat autoscaling API

On 11/15/2013 02:48 PM, Christopher Armstrong wrote: > > The thinking here was: > - this makes the new config stuff easier to scale (config get applied > per scaling stack) > - you can potentially place notification resources in the scaling > stack (think marconi message res

Re: [openstack-dev] [Heat] rough draft of Heat autoscaling API

On Thu, Nov 14, 2013 at 5:40 PM, Angus Salkeld wrote: > On 14/11/13 10:19 -0600, Christopher Armstrong wrote: > >> http://docs.heatautoscale.apiary.io/ >> >> I've thrown together a rough sketch of the proposed API for autoscaling. >> It's written in API-Blueprint format (which is a simple subset

Re: [openstack-dev] [Heat] rough draft of Heat autoscaling API

On 14/11/13 10:19 -0600, Christopher Armstrong wrote: http://docs.heatautoscale.apiary.io/ I've thrown together a rough sketch of the proposed API for autoscaling. It's written in API-Blueprint format (which is a simple subset of Markdown) and provides schemas for inputs and outputs using JSON-S

Re: [openstack-dev] [Heat] rough draft of Heat autoscaling API

On Thu, Nov 14, 2013 at 12:52 PM, Randall Burt wrote: > > On Nov 14, 2013, at 1:05 PM, Christopher Armstrong < > chris.armstr...@rackspace.com> wrote: > > On Thu, Nov 14, 2013 at 11:00 AM, Randall Burt < > randall.b...@rackspace.com> wrote: > >> >> On Nov 14, 2013, at 12:44 PM, Zane Bitter >>

Re: [openstack-dev] [Heat] rough draft of Heat autoscaling API

On Nov 14, 2013, at 1:05 PM, Christopher Armstrong mailto:chris.armstr...@rackspace.com>> wrote: On Thu, Nov 14, 2013 at 11:00 AM, Randall Burt mailto:randall.b...@rackspace.com>> wrote: On Nov 14, 2013, at 12:44 PM, Zane Bitter mailto:zbit...@redhat.com>> wrote: > On 14/11/13 18:51, Randal

Re: [openstack-dev] [Heat] rough draft of Heat autoscaling API

On Thu, Nov 14, 2013 at 11:00 AM, Randall Burt wrote: > > On Nov 14, 2013, at 12:44 PM, Zane Bitter > wrote: > > > On 14/11/13 18:51, Randall Burt wrote: > >> > >> On Nov 14, 2013, at 11:30 AM, Christopher Armstrong > >> mailto:chris.armstr...@rackspace.com>> > >> wrote: > >> > >>> On Thu, Nov

Re: [openstack-dev] [Heat] rough draft of Heat autoscaling API

On Nov 14, 2013, at 12:44 PM, Zane Bitter wrote: > On 14/11/13 18:51, Randall Burt wrote: >> >> On Nov 14, 2013, at 11:30 AM, Christopher Armstrong >> mailto:chris.armstr...@rackspace.com>> >> wrote: >> >>> On Thu, Nov 14, 2013 at 11:16 AM, Randall Burt >>> mailto:randall.b...@rackspace.com>

Re: [openstack-dev] [Heat] rough draft of Heat autoscaling API

On Thu, Nov 14, 2013 at 10:44 AM, Zane Bitter wrote: > On 14/11/13 18:51, Randall Burt wrote: > >> >> On Nov 14, 2013, at 11:30 AM, Christopher Armstrong >> mailto:chris.armstr...@rackspace.com>> >> wrote: >> >> On Thu, Nov 14, 2013 at 11:16 AM, Randall Burt >>> mailto:randall.b...@rackspace.c

Re: [openstack-dev] [Heat] rough draft of Heat autoscaling API

On Thu, Nov 14, 2013 at 10:46 AM, Georgy Okrokvertskhov < gokrokvertsk...@mirantis.com> wrote: > Hi, > > It would be great if API specs contain a list of attributes\parameters one > can pass during group creation. I believe Zane already asked about > LaunchConfig, but I think new autoscaling API c

Re: [openstack-dev] [Heat] rough draft of Heat autoscaling API

Thanks for the comments, Zane. On Thu, Nov 14, 2013 at 9:56 AM, Zane Bitter wrote: > On 14/11/13 17:19, Christopher Armstrong wrote: > >> http://docs.heatautoscale.apiary.io/ >> >> I've thrown together a rough sketch of the proposed API for autoscaling. >> It's written in API-Blueprint format (

Re: [openstack-dev] [Heat] rough draft of Heat autoscaling API

Hi, It would be great if API specs contain a list of attributes\parameters one can pass during group creation. I believe Zane already asked about LaunchConfig, but I think new autoscaling API creation was specifically designed to move from limited AWS ElasticLB to something with more broad feature

Re: [openstack-dev] [Heat] rough draft of Heat autoscaling API

On 14/11/13 18:51, Randall Burt wrote: On Nov 14, 2013, at 11:30 AM, Christopher Armstrong mailto:chris.armstr...@rackspace.com>> wrote: On Thu, Nov 14, 2013 at 11:16 AM, Randall Burt mailto:randall.b...@rackspace.com>> wrote: Regarding web hook execution and cool down, I think the respo

Re: [openstack-dev] [Heat] rough draft of Heat autoscaling API

On 14/11/13 17:19, Christopher Armstrong wrote: http://docs.heatautoscale.apiary.io/ I've thrown together a rough sketch of the proposed API for autoscaling. It's written in API-Blueprint format (which is a simple subset of Markdown) and provides schemas for inputs and outputs using JSON-Schema.

Re: [openstack-dev] [Heat] rough draft of Heat autoscaling API

On Nov 14, 2013, at 11:30 AM, Christopher Armstrong mailto:chris.armstr...@rackspace.com>> wrote: On Thu, Nov 14, 2013 at 11:16 AM, Randall Burt mailto:randall.b...@rackspace.com>> wrote: Good stuff! Some questions/comments: If web hooks are associated with policies and policies are independe

Re: [openstack-dev] [Heat] rough draft of Heat autoscaling API

On Thu, Nov 14, 2013 at 11:16 AM, Randall Burt wrote: > Good stuff! Some questions/comments: > > If web hooks are associated with policies and policies are independent > entities, how does a web hook specify the scaling group to act on? Does > calling the web hook activate the policy on every as

Re: [openstack-dev] [Heat] rough draft of Heat autoscaling API

Good stuff! Some questions/comments: If web hooks are associated with policies and policies are independent entities, how does a web hook specify the scaling group to act on? Does calling the web hook activate the policy on every associated scaling group? Regarding web hook execution and cool d

Re: [openstack-dev] [Heat] rough draft of Heat autoscaling API

On Nov 14, 2013, at 10:19 AM, Christopher Armstrong mailto:chris.armstr...@rackspace.com>> wrote: http://docs.heatautoscale.apiary.io/ I've thrown together a rough sketch of the proposed API for autoscaling. It's written in API-Blueprint format (which is a simple subset of Markdown) and prov

[openstack-dev] [Heat] rough draft of Heat autoscaling API

http://docs.heatautoscale.apiary.io/ I've thrown together a rough sketch of the proposed API for autoscaling. It's written in API-Blueprint format (which is a simple subset of Markdown) and provides schemas for inputs and outputs using JSON-Schema. The source document is currently at https://githu