Skip to content
This repository has been archived by the owner on Jun 14, 2023. It is now read-only.

Allow configuration of ASG termination policies #14

Merged
merged 3 commits into from
Oct 14, 2015
Merged

Conversation

atayarani
Copy link
Contributor

@Tapjoy/eng-group-ops @StabbyCutyou

This allows more flexibility around which instances get scaled out.

@StabbyCutyou
Copy link
Contributor

Makes sense, but failing specs

@atayarani
Copy link
Contributor Author

@StabbyCutyou specs are fixed

@atayarani
Copy link
Contributor Author

@StabbyCutyou @marcuswalser @ehealy
/cc @Tapjoy/eng-group-ops

Accidentally made this PR bigger, but WONTFIX.

New notes:

  • Laid the groundwork for static and dynamic scaling options
  • Cleaned up a lot of stuff
  • Deprecated/removed --config-dir. It was confusing, but is no longer.
  • Reworked some of the specs to better match actual code flow.


config.merge!(aws_env.merge(user_data: Base64.encode64("#{user_data}")))
Tapjoy::AutoscalingBootstrap::Audit.new(config)
when 'scale'

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We'd discussed potentially having min/max stored in the yaml file. Desired probably ought to remain a CLI option - maybe include the ability to do it either way?

@marcuswalser
Copy link

This is LGTM, we can address the min/max stuff in a followup PR.

atayarani added a commit that referenced this pull request Oct 14, 2015
Allow configuration of ASG termination policies
@atayarani atayarani merged commit c7a09d2 into v100 Oct 14, 2015
@atayarani atayarani deleted the refactor_elb_code branch November 24, 2015 16:09
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants