Autoscale trigger support removed from latest? #180

Closed
liamf opened this Issue May 4, 2011 · 12 comments

Comments

Projects
None yet
7 participants
@liamf
Contributor

liamf commented May 4, 2011

Hello

Unsure if this is the correct forum to raise an issue like this ... apologies if not.

Boto release 2.0b4 had support (well I didn't test it, but the code was there) for auto-scaling triggers.

This suppot is no longer at the head of development.

This would be sorta bad. Was this removed on purpose?

Liam

@rlotun

This comment has been minimized.

Show comment Hide comment
@rlotun

rlotun May 4, 2011

Contributor

Hi, I maintain the autoscale code. In the latest version of the autoscale API (2010-08-01), the concept of Triggers has been removed, and replaced with cloudwatch alarms instead.

However, I suspect (and must verify) that old autoscale groups (with triggers associated with them), need this functionality however (there is no automatic translation process from triggers to cloudwatch alarms). This is unfortunate, and it seems that I have to add triggers back in, which I will do soon.

Thanks for reporting this.

Contributor

rlotun commented May 4, 2011

Hi, I maintain the autoscale code. In the latest version of the autoscale API (2010-08-01), the concept of Triggers has been removed, and replaced with cloudwatch alarms instead.

However, I suspect (and must verify) that old autoscale groups (with triggers associated with them), need this functionality however (there is no automatic translation process from triggers to cloudwatch alarms). This is unfortunate, and it seems that I have to add triggers back in, which I will do soon.

Thanks for reporting this.

@ghost ghost assigned rlotun May 4, 2011

@liamf

This comment has been minimized.

Show comment Hide comment
@liamf

liamf May 4, 2011

Contributor

Thanks for that ... on the boto-users forum someone had kindly posted an example of how to us the boto APIs to do this which I am currently trying out.

I was perhaps relying too literally on using CloudFormation templates as a model for how to make a boto script.
The CloudFormation templates (well, TemplateFormatVersion 2010-09-09 anyway) use the concept of an AWS::AutoScaling::Trigger to setup scaling conditions.

Although I have gone right off CloudFormation as it is too opaque for my liking. I like boto a lot more.
It will take me some time to find my way 'round though.

Thanks for the excellent work.

Contributor

liamf commented May 4, 2011

Thanks for that ... on the boto-users forum someone had kindly posted an example of how to us the boto APIs to do this which I am currently trying out.

I was perhaps relying too literally on using CloudFormation templates as a model for how to make a boto script.
The CloudFormation templates (well, TemplateFormatVersion 2010-09-09 anyway) use the concept of an AWS::AutoScaling::Trigger to setup scaling conditions.

Although I have gone right off CloudFormation as it is too opaque for my liking. I like boto a lot more.
It will take me some time to find my way 'round though.

Thanks for the excellent work.

@garnaat

This comment has been minimized.

Show comment Hide comment
@garnaat

garnaat Jul 29, 2011

Owner

So, did we come to a conclusion on this? Do we still need to support Triggers?

Owner

garnaat commented Jul 29, 2011

So, did we come to a conclusion on this? Do we still need to support Triggers?

@liamf

This comment has been minimized.

Show comment Hide comment
@liamf

liamf Aug 14, 2011

Contributor

I apologise Mitch,

I've been on vacation for three weeks, back tomorrow.

Following this comment from rlotun I implemented my autoscaling group using cloudwatch alarms and not triggers as he suggested. This is supported by boto 2.0 although strictly speaking I am using a fork into which I merged the changes from a 2.0 release candidate - not the very latest.

Next week I must review any differences between what I am using and the current head, to clean up any differences and move to using the release code in case of differences in approach.

from my point of view I didn't have to use Triggers, although rlotun being the expert might have a particular case where they are required.

Contributor

liamf commented Aug 14, 2011

I apologise Mitch,

I've been on vacation for three weeks, back tomorrow.

Following this comment from rlotun I implemented my autoscaling group using cloudwatch alarms and not triggers as he suggested. This is supported by boto 2.0 although strictly speaking I am using a fork into which I merged the changes from a 2.0 release candidate - not the very latest.

Next week I must review any differences between what I am using and the current head, to clean up any differences and move to using the release code in case of differences in approach.

from my point of view I didn't have to use Triggers, although rlotun being the expert might have a particular case where they are required.

@jpichon

This comment has been minimized.

Show comment Hide comment
@jpichon

jpichon Sep 8, 2011

Apologies if this isn't the right place to mention it, but at the moment the documentation also still references Triggers in the intro to Autoscaling -> http://boto.cloudhackers.com/autoscale_tut.html#scaling-a-group-up-or-down even though the code doesn't run using 2.0 (cannot import name Trigger).

jpichon commented Sep 8, 2011

Apologies if this isn't the right place to mention it, but at the moment the documentation also still references Triggers in the intro to Autoscaling -> http://boto.cloudhackers.com/autoscale_tut.html#scaling-a-group-up-or-down even though the code doesn't run using 2.0 (cannot import name Trigger).

@davidcoallier

This comment has been minimized.

Show comment Hide comment
@davidcoallier

davidcoallier Sep 30, 2011

Another issue with removing Triggers is that one can no longer delete Triggers by loading them then invoking Trigger.delete(). I do agree that creating new autoscaling infrastructures/setups using Triggers should be forbidden though however some "older" functions still have relevance. $0.02

Another issue with removing Triggers is that one can no longer delete Triggers by loading them then invoking Trigger.delete(). I do agree that creating new autoscaling infrastructures/setups using Triggers should be forbidden though however some "older" functions still have relevance. $0.02

@garnaat

This comment has been minimized.

Show comment Hide comment
@garnaat

garnaat Oct 1, 2011

Owner

Of course, you can always do that by using an earlier version of boto that supported the API version that included Triggers. I understand that's inconvenient so I will look into retrofitting some support for Triggers into the current version.

Owner

garnaat commented Oct 1, 2011

Of course, you can always do that by using an earlier version of boto that supported the API version that included Triggers. I understand that's inconvenient so I will look into retrofitting some support for Triggers into the current version.

@davidcoallier

This comment has been minimized.

Show comment Hide comment
@davidcoallier

davidcoallier Oct 3, 2011

Understandable, if there's anything I can do to help, feel free to let me know :-)

Understandable, if there's anything I can do to help, feel free to let me know :-)

@jarpy

This comment has been minimized.

Show comment Hide comment
@jarpy

jarpy Apr 11, 2012

The tutorial documentation still shows an example with Triggers.
http://boto.cloudhackers.com/en/latest/autoscale_tut.html

Can I entice someone to write a modern equivalent example? Could I perhaps mail you a box of cookies?

I'm really stuck with Autoscaling at the moment.

jarpy commented Apr 11, 2012

The tutorial documentation still shows an example with Triggers.
http://boto.cloudhackers.com/en/latest/autoscale_tut.html

Can I entice someone to write a modern equivalent example? Could I perhaps mail you a box of cookies?

I'm really stuck with Autoscaling at the moment.

@garnaat

This comment has been minimized.

Show comment Hide comment
@garnaat

garnaat Apr 11, 2012

Owner

I'm going to try to get that tutorial updated. Or provide some other description. I'm just not sure when I'll be able to get to it. In the meantime, you might want to check this out:

http://blog.codento.com/2012/03/hello-ec2-part-3-self-healing-cluster/

It's a nice example and might help you out.

Owner

garnaat commented Apr 11, 2012

I'm going to try to get that tutorial updated. Or provide some other description. I'm just not sure when I'll be able to get to it. In the meantime, you might want to check this out:

http://blog.codento.com/2012/03/hello-ec2-part-3-self-healing-cluster/

It's a nice example and might help you out.

@jarpy

This comment has been minimized.

Show comment Hide comment
@jarpy

jarpy May 25, 2012

Thanks. It was specifically dynamic scaling based on triggers/alarms that I was stuck on.

I have a working example now if anybody is interested:
https://gist.github.com/2785420

I'll see if I can write a patch to the boto docs to capture the new "alarms" (vs. "triggers") system.

jarpy commented May 25, 2012

Thanks. It was specifically dynamic scaling based on triggers/alarms that I was stuck on.

I have a working example now if anybody is interested:
https://gist.github.com/2785420

I'll see if I can write a patch to the boto docs to capture the new "alarms" (vs. "triggers") system.

@toastdriven

This comment has been minimized.

Show comment Hide comment
@toastdriven

toastdriven Jul 11, 2013

Contributor

Triggers have long since been deprecated & removed. Closing.

Contributor

toastdriven commented Jul 11, 2013

Triggers have long since been deprecated & removed. Closing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment