april25-26sanfranciscocloud success starts hereDeployment Checkup: How to RegularlyTune Your Cloud EnvironmentBrian Adler,...
#2#2#RightscaleComputeTune Ups - Why They Make Sense• Over time, deployments grow organically• Some things are done quickl...
#3#3#RightscaleComputeWhys and Whats• Deployment Checkups (the “why”)• Cost• Performance• Best Practices• Deployment Consi...
#4#rightscalecomputeDeployment CheckupCost Optimization
#5#5#RightscaleComputeCost Optimization• Unused/Unneeded Resources
#6#6#RightscaleComputeCost Optimization• Unused/Unneeded Resources
#7#7#RightscaleComputeCost Optimization• Unused/Unneeded Resources
#8#8#RightscaleComputeCost Optimization• Unused/Unneeded Resources
#9#9#RightscaleComputeCost Optimization• Unused/Unneeded Resources• EBS Volumes
#10#10#RightscaleComputeCost Optimization• Unused/Unneeded Resources• EBS Snapshots
#11#11#RightscaleComputeCost Optimization• Unused/Unneeded Resources• EIPs
#12#12#RightscaleComputeCost Optimization• Unused/Unneeded Resources• S3 objects
#13#13#RightscaleComputeCost Optimization• Storage• Don’t over-allocate initially. Increase capacity when needed.
#14#14#RightscaleComputeCost Optimization• Bandwidth• Cross-AZ• Generally acceptable/recommended for HA configurations• Cr...
#15#rightscalecomputeDeployment CheckupServer Utilization
#16#16#RightscaleComputeServer Utilization• Choose the right sized instance for the task at hand• Utilize Reserved Instanc...
#17#17#RightscaleComputeServer Utilization• CPU affinity• taskset• irqbalanceSpread the loadif/when possible
#18#18#RightscaleComputeServer Utilization• Memory• Numerous different memory options – find the right fit• 613 MiB instan...
#19#19#RightscaleComputeServer Utilization• Load average• Good indicator of overall capacity utilization• 1.0 x Number of ...
#20#20#RightscaleComputeServer Utilization• Monitoring and Alerts• Use them! Find small problems before they become big pr...
#21#rightscalecomputeDeployment CheckupHigh Availability and Disaster Recovery
#22#22#RightscaleComputeHA/DR Considerations• Avoid single points of failure (SPOF)• Use Availability Zones (AZ) to your b...
#23#23#RightscaleComputeHA/DR Implementation• Availability Zone Distribution
#24#24#RightscaleComputeHA/DR Implementation• Availability Zone Distribution
#25#25#RightscaleComputeHA/DR Implementation• Availability Zone and Regional Distribution
#26#26#RightscaleComputeHA/DR Implementation• Availability Zone and Regional Distribution
#27#27#RightscaleComputeHA/DR Implementation• Availability Zone and Regional Distribution
#28#28#RightscaleComputeHA/DR Implementation• Availability Zone and Regional Distribution
#29#29#RightscaleComputeHA/DR Implementation• Availability Zone and Regional Distribution
#30#30#RightscaleComputeHA/DR Implementation• Availability Zone and Regional Distribution
#31#31#RightscaleComputeHA/DR Implementation• Availability Zone and Regional Distribution
#32#rightscalecomputeDeployment CheckupSecurity
#33#33#RightscaleComputeSecurity• Security Groups
#34#34#RightscaleComputeSecurity• iptables
#35#35#RightscaleComputeSecurity• iptables
#36#36#RightscaleComputeSecurity• iptables
#37#37#RightscaleComputeSecurity – OS Patching• Upcoming ServerTemplate release (v13.4) will have recipes to:• Unfreeze Se...
#38#rightscalecomputeDeployment CheckupBest Practices
#39#39#RightscaleComputeBest Practices• Image Bundling - Friends don’t let friends bundle• Use ServerTemplate with base Ri...
#40#40#RightscaleComputeBest Practices• No SPOF• Distribute servers in each tier across multiple AZs• Use Deployments as A...
#41#41#RightscaleComputeBest Practices• Commit your ServerTemplates (don’t use HEAD)
#42#42#RightscaleComputeBest Practices• Use Credentials for all sensitive inputs
#43#43#RightscaleComputeBest Practices• Use autoscaling in combination with right-sized instances forthe task at hand• Aut...
#44#44#RightscaleComputeSummary• Deployment sprawl can lead to cost and operationalinefficiencies• Cost Optimizations can ...
april25-26sanfranciscocloud success starts hereQuestions?
Upcoming SlideShare
Loading in...5
×

Deployment Checkup: How to Regularly Tune Your Cloud Environment - RightScale Compute 2013

151

Published on

Speaker: Brian Adler - Sr. Services Architect, RightScale

Periodic reviews of your cloud deployments are as important as a regular oil change and tune up at your mechanic. We will cover our RightScale deployment checklist to root out issues with server utilization, cost optimization, multi-zone balancing, auto-scaling, high-availability configuration, security groups, IP address assignment, security patching, and manual changes. You will leave with an easy-to-follow maintenance schedule for your cloud environment.

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
151
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
4
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Deployment Checkup: How to Regularly Tune Your Cloud Environment - RightScale Compute 2013

  1. 1. april25-26sanfranciscocloud success starts hereDeployment Checkup: How to RegularlyTune Your Cloud EnvironmentBrian Adler, Sr. Services Architect, RightScale
  2. 2. #2#2#RightscaleComputeTune Ups - Why They Make Sense• Over time, deployments grow organically• Some things are done quickly to solve an immediate issue andare never readdressed• “If it ain’t broke, don’t fix it”• Squeaky wheels get the grease. But over-greased wheels tendto get ignored – and can be costly
  3. 3. #3#3#RightscaleComputeWhys and Whats• Deployment Checkups (the “why”)• Cost• Performance• Best Practices• Deployment Considerations (the “what”)• Cost Optimization• Server Utilization• High Availability and Disaster Recovery (HA/DR) Implementation• Security• Best Practices
  4. 4. #4#rightscalecomputeDeployment CheckupCost Optimization
  5. 5. #5#5#RightscaleComputeCost Optimization• Unused/Unneeded Resources
  6. 6. #6#6#RightscaleComputeCost Optimization• Unused/Unneeded Resources
  7. 7. #7#7#RightscaleComputeCost Optimization• Unused/Unneeded Resources
  8. 8. #8#8#RightscaleComputeCost Optimization• Unused/Unneeded Resources
  9. 9. #9#9#RightscaleComputeCost Optimization• Unused/Unneeded Resources• EBS Volumes
  10. 10. #10#10#RightscaleComputeCost Optimization• Unused/Unneeded Resources• EBS Snapshots
  11. 11. #11#11#RightscaleComputeCost Optimization• Unused/Unneeded Resources• EIPs
  12. 12. #12#12#RightscaleComputeCost Optimization• Unused/Unneeded Resources• S3 objects
  13. 13. #13#13#RightscaleComputeCost Optimization• Storage• Don’t over-allocate initially. Increase capacity when needed.
  14. 14. #14#14#RightscaleComputeCost Optimization• Bandwidth• Cross-AZ• Generally acceptable/recommended for HA configurations• Cross-region/cloud• Compress/Optimize
  15. 15. #15#rightscalecomputeDeployment CheckupServer Utilization
  16. 16. #16#16#RightscaleComputeServer Utilization• Choose the right sized instance for the task at hand• Utilize Reserved Instances (PlanForCloud can be of greatbenefit here)Something odd happened around this time…use alerts tobe notified and load testing to find the right instance size for the task
  17. 17. #17#17#RightscaleComputeServer Utilization• CPU affinity• taskset• irqbalanceSpread the loadif/when possible
  18. 18. #18#18#RightscaleComputeServer Utilization• Memory• Numerous different memory options – find the right fit• 613 MiB instances through 244 GiB instances
  19. 19. #19#19#RightscaleComputeServer Utilization• Load average• Good indicator of overall capacity utilization• 1.0 x Number of Cores = fully utilized
  20. 20. #20#20#RightscaleComputeServer Utilization• Monitoring and Alerts• Use them! Find small problems before they become big problems• Look for trends and act on them (not on spikes or anomalies)• Look for underutilization as well as overutilization
  21. 21. #21#rightscalecomputeDeployment CheckupHigh Availability and Disaster Recovery
  22. 22. #22#22#RightscaleComputeHA/DR Considerations• Avoid single points of failure (SPOF)• Use Availability Zones (AZ) to your benefit• Always place one of each component (load balancers, app servers,databases) in at least two AZs• Replicate data across AZs (HA) and backup or replicate acrossregions/clouds for failover (DR)• Setup monitoring, alerts and operations to identify andautomate problem resolution or failover process
  23. 23. #23#23#RightscaleComputeHA/DR Implementation• Availability Zone Distribution
  24. 24. #24#24#RightscaleComputeHA/DR Implementation• Availability Zone Distribution
  25. 25. #25#25#RightscaleComputeHA/DR Implementation• Availability Zone and Regional Distribution
  26. 26. #26#26#RightscaleComputeHA/DR Implementation• Availability Zone and Regional Distribution
  27. 27. #27#27#RightscaleComputeHA/DR Implementation• Availability Zone and Regional Distribution
  28. 28. #28#28#RightscaleComputeHA/DR Implementation• Availability Zone and Regional Distribution
  29. 29. #29#29#RightscaleComputeHA/DR Implementation• Availability Zone and Regional Distribution
  30. 30. #30#30#RightscaleComputeHA/DR Implementation• Availability Zone and Regional Distribution
  31. 31. #31#31#RightscaleComputeHA/DR Implementation• Availability Zone and Regional Distribution
  32. 32. #32#rightscalecomputeDeployment CheckupSecurity
  33. 33. #33#33#RightscaleComputeSecurity• Security Groups
  34. 34. #34#34#RightscaleComputeSecurity• iptables
  35. 35. #35#35#RightscaleComputeSecurity• iptables
  36. 36. #36#36#RightscaleComputeSecurity• iptables
  37. 37. #37#37#RightscaleComputeSecurity – OS Patching• Upcoming ServerTemplate release (v13.4) will have recipes to:• Unfreeze Security repos on Ubuntu• Unfreeze Upstream repos on CentOS• Perform security update
  38. 38. #38#rightscalecomputeDeployment CheckupBest Practices
  39. 39. #39#39#RightscaleComputeBest Practices• Image Bundling - Friends don’t let friends bundle• Use ServerTemplate with base RightImage• Configure server at boot time• Use EBS-backed images to speed boot times if needed• Rare case where bundling is recommended• Manual install of software required• Boot time is unacceptably long to respond to dynamic event
  40. 40. #40#40#RightscaleComputeBest Practices• No SPOF• Distribute servers in each tier across multiple AZs• Use Deployments as Application containers
  41. 41. #41#41#RightscaleComputeBest Practices• Commit your ServerTemplates (don’t use HEAD)
  42. 42. #42#42#RightscaleComputeBest Practices• Use Credentials for all sensitive inputs
  43. 43. #43#43#RightscaleComputeBest Practices• Use autoscaling in combination with right-sized instances forthe task at hand• Automate all operations – no manual changes• Reboot – all is lost• Automation is documentation
  44. 44. #44#44#RightscaleComputeSummary• Deployment sprawl can lead to cost and operationalinefficiencies• Cost Optimizations can be found hiding in many places• Find the right size resource for the job• Don’t use a hammer if it ain’t a nail• High Availability should be designed in from the start• Look for SPOF and find ways to eliminate them• Disaster Recovery can be affordable• Security – open up only what you have to• Best Practices promote operational efficiencies
  45. 45. april25-26sanfranciscocloud success starts hereQuestions?
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.

×