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:
On 20/11/13 23:49, Christopher Armstrong wrote:
On Wed, Nov 20, 2013 at 2:07 PM, Zane Bitter zbit...@redhat.com
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 zbit...@redhat.com
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
zbit...@redhat.commailto:zbit...@redhat.com wrote:
On 20/11/13 23:49, Christopher Armstrong wrote:
On Wed, Nov 20
On Thu, Nov 21, 2013 at 5:18 AM, Zane Bitter zbit...@redhat.com wrote:
On 20/11/13 23:49, Christopher Armstrong wrote:
On Wed, Nov 20, 2013 at 2:07 PM, Zane Bitter zbit...@redhat.com
mailto:zbit...@redhat.com wrote:
On 20/11/13 16:07, Christopher Armstrong wrote:
On Tue, Nov
On Thu, Nov 21, 2013 at 12:18 PM, Zane Bitter zbit...@redhat.com 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
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
On Thu, Nov 21, 2013 at 12:31 PM, Zane Bitter zbit...@redhat.com 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
On Tue, Nov 19, 2013 at 4:27 PM, Zane Bitter zbit...@redhat.com 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
On 20/11/13 16:07, Christopher Armstrong wrote:
On Tue, Nov 19, 2013 at 4:27 PM, Zane Bitter zbit...@redhat.com
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
On Wed, Nov 20, 2013 at 2:07 PM, Zane Bitter zbit...@redhat.com wrote:
On 20/11/13 16:07, Christopher Armstrong wrote:
On Tue, Nov 19, 2013 at 4:27 PM, Zane Bitter zbit...@redhat.com
mailto:zbit...@redhat.com wrote:
On 19/11/13 19:14, Christopher Armstrong wrote:
[snip]
On Mon, Nov 18, 2013 at 5:57 AM, Zane Bitter 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 zbit...@redhat.com wrote:
On 15/11/13 02:48, Christopher Armstrong wrote:
On
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
On 19/11/13 19:14, Christopher Armstrong wrote:
On Mon, Nov 18, 2013 at 5:57 AM, Zane Bitter zbit...@redhat.com
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
On 11/18/2013 01:03 PM, Christopher Armstrong wrote:
On Sun, Nov 17, 2013 at 2:57 PM, Steve Baker sba...@redhat.com
mailto:sba...@redhat.com wrote:
On 11/15/2013 05:19 AM, Christopher Armstrong wrote:
http://docs.heatautoscale.apiary.io/
I've thrown together a rough
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
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 the
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 zbit...@redhat.com wrote:
On 15/11/13 02:48, Christopher Armstrong wrote:
On Thu, Nov 14, 2013 at 5:40 PM, Angus Salkeld asalk...@redhat.com
On 15/11/13 21:06, Mike Spreitzer wrote:
Zane Bitter zbit...@redhat.com 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
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 zbit...@redhat.com wrote:
On 15/11/13 02:48, Christopher Armstrong wrote:
On Thu, Nov 14, 2013 at 5:40 PM,
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
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
On Sun, Nov 17, 2013 at 2:57 PM, Steve Baker sba...@redhat.com 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
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 zbit...@redhat.com
mailto:zbit...@redhat.com wrote:
A few comments...
#1 thing is that the launch configuration needs
On 15/11/13 08:46 -0600, Christopher Armstrong wrote:
On Fri, Nov 15, 2013 at 3:57 AM, Zane Bitter zbit...@redhat.com wrote:
On 15/11/13 02:48, Christopher Armstrong wrote:
On Thu, Nov 14, 2013 at 5:40 PM, Angus Salkeld asalk...@redhat.com
mailto:asalk...@redhat.com wrote:
On 14/11/13
On 15/11/13 02:48, Christopher Armstrong wrote:
On Thu, Nov 14, 2013 at 5:40 PM, Angus Salkeld asalk...@redhat.com
mailto:asalk...@redhat.com wrote:
On 14/11/13 10:19 -0600, Christopher Armstrong wrote:
http://docs.heatautoscale.__apiary.io/
On 14/11/13 19:58, Christopher Armstrong wrote:
On Thu, Nov 14, 2013 at 10:44 AM, Zane Bitter zbit...@redhat.com
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
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 action
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
On Fri, Nov 15, 2013 at 4:16 AM, Zane Bitter zbit...@redhat.com wrote:
On 14/11/13 19:58, Christopher Armstrong wrote:
On Thu, Nov 14, 2013 at 10:44 AM, Zane Bitter zbit...@redhat.com
mailto:zbit...@redhat.com wrote:
On 14/11/13 18:51, Randall Burt wrote:
Perhaps, but I also
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 zbit...@redhat.com
mailto:zbit...@redhat.com wrote:
A few comments...
#1 thing is that the launch configuration needs to be somehow
represented. In general
Zane Bitter zbit...@redhat.com 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:
-
On Nov 14, 2013, at 10:19 AM, Christopher Armstrong
chris.armstr...@rackspace.commailto: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
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
On Thu, Nov 14, 2013 at 11:16 AM, Randall Burt
randall.b...@rackspace.comwrote:
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
On Nov 14, 2013, at 11:30 AM, Christopher Armstrong
chris.armstr...@rackspace.commailto:chris.armstr...@rackspace.com
wrote:
On Thu, Nov 14, 2013 at 11:16 AM, Randall Burt
randall.b...@rackspace.commailto:randall.b...@rackspace.com wrote:
Good stuff! Some questions/comments:
If web hooks are
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
On 14/11/13 18:51, Randall Burt wrote:
On Nov 14, 2013, at 11:30 AM, Christopher Armstrong
chris.armstr...@rackspace.com mailto:chris.armstr...@rackspace.com
wrote:
On Thu, Nov 14, 2013 at 11:16 AM, Randall Burt
randall.b...@rackspace.com mailto:randall.b...@rackspace.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 creation was specifically
designed to move from limited AWS ElasticLB to something with more broad
Thanks for the comments, Zane.
On Thu, Nov 14, 2013 at 9:56 AM, Zane Bitter zbit...@redhat.com 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
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
On Thu, Nov 14, 2013 at 10:44 AM, Zane Bitter zbit...@redhat.com wrote:
On 14/11/13 18:51, Randall Burt wrote:
On Nov 14, 2013, at 11:30 AM, Christopher Armstrong
chris.armstr...@rackspace.com mailto:chris.armstr...@rackspace.com
wrote:
On Thu, Nov 14, 2013 at 11:16 AM, Randall Burt
On Nov 14, 2013, at 12:44 PM, Zane Bitter zbit...@redhat.com
wrote:
On 14/11/13 18:51, Randall Burt wrote:
On Nov 14, 2013, at 11:30 AM, Christopher Armstrong
chris.armstr...@rackspace.com mailto:chris.armstr...@rackspace.com
wrote:
On Thu, Nov 14, 2013 at 11:16 AM, Randall Burt
On Thu, Nov 14, 2013 at 11:00 AM, Randall Burt
randall.b...@rackspace.comwrote:
On Nov 14, 2013, at 12:44 PM, Zane Bitter zbit...@redhat.com
wrote:
On 14/11/13 18:51, Randall Burt wrote:
On Nov 14, 2013, at 11:30 AM, Christopher Armstrong
chris.armstr...@rackspace.com
On Thu, Nov 14, 2013 at 12:52 PM, Randall Burt
randall.b...@rackspace.comwrote:
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
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
On Thu, Nov 14, 2013 at 5:40 PM, Angus Salkeld asalk...@redhat.com 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
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 resource
47 matches
Mail list logo
