-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add IISNode IICluster and Autoscaler classes #58
Conversation
I don't think you'll need to worry about Classiclinking. We've got all of our prod web server in VPC, and we're probably not going to need to classic link when migrating or stage servers |
"cloudwatch:ListMetrics", | ||
"cloudwatch:PutMetricAlarm", | ||
"cloudwatch:PutMetricData", | ||
"cloudwatch:SetAlarmState" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
would need access to route53:ChangeResourceRecordSets
as well
Autoscaler setup class | ||
''' | ||
|
||
log = logging.getLogger('Clusters.AutoScaler') |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This module should either be moved to the tyr.clusters
package or the logger name should be changed to correctly reflect the package it belongs to - perhaps Autoscaling.Autoscaler
(if the package were renamed autoscaling
).
OK, I have made changes as discussed. |
Add IISNode IICluster and Autoscaler classes
Meh, my revert didn't reopen the pull request. Not sure what's happened there. I will create a new pull request for these changes |
I have been using the following to test.
There are a few issues that need ironing out: