Upload
flux7
View
2.798
Download
2
Tags:
Embed Size (px)
DESCRIPTION
Citation preview
Let’s discuss Spot Instances
Spot Strategies
WHO AM I?
Aater Suleman
Part-time UT Professor Geek, Architect, Developer, Ops, DevOps …
Co-founder & CEO Flux7 Labs
○ DevOps Solutions
■ Deployments■ Cost/performance optimized large scale website (Ruby on rails, node.js, Django)
and Hadoop deployments
Spot Instances
Consumer chooses a maximum bid
AWS charges market price @ start of the hour
Can get terminated at any time
Spot Strategy Checklist
Spot terminations
Spot outages
Launch failures
Optimized price = min(spot price, on-demand price)
Ability to auto-scale
Similarities with Auto-scaling
Stateless instances
Apps can tolerate momentary dip in capacity
Apps can tolerate instance “swapping”
Launch failures
Differences from auto-scaling?
No programmable cooldown period
AppNeta’s (http://www.appneta.com/blog/aws-spot-instances/)
Two ASGs (spot and main)
SNS notifications on Spot ASGs
Outside daemon:
○ Spot instance termination ⇒ on-demand instance
Analysis
Spot terminations
Spot outages
Launch failures
Optimized price
Ability to auto-scale
Sanket’s Algorithm
Two ASGs (spot and on-demand)● Setup thresholds as follows:
ASG: On-demand
Scale up: CPU > 75%
Scale down: CPU < 55%
ASG: Spot
Scale up: CPU > 60%
Scale down: CPU < 45%
Analysis
Spot terminations
Spot outages
Launch failures
Optimized price
Ability to auto-scale
Flux7 v1.0
Our own auto-scaling solution that allows hybrid spot and on-demand
Step Up: If spot price < on-demand, launch spot
Spot Launch failure: Launch on-demand
Step Down: If on-demand is available, terminate it
End of hour: Treat like Step Up
Analysis
Spot terminations
Spot outages
Launch failures
Optimized price
Ability to auto-scale (in-house ASG)
Thank You