1 / 18

Replace Your Iron With a Cloud

Clouds are like cotton candy, and irons … make shirts flat?. Replace Your Iron With a Cloud. Barney Boisvert http://www.barneyb.com/. Who Am I?. Agenda. What is “the cloud”? Different approaches of cloud services Pros and cons of using the cloud AWS components

aliya
Télécharger la présentation

Replace Your Iron With a Cloud

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Clouds are like cotton candy, and irons … make shirts flat? Replace Your Iron With a Cloud Barney Boisvert http://www.barneyb.com/

  2. Who Am I?

  3. Agenda • What is “the cloud”? • Different approaches of cloud services • Pros and cons of using the cloud • AWS components • How Mentor migrated to the cloud • The AWS us-east-1 outage of April 20th

  4. What is “The Cloud”? • Cloud is a class of services, not technologies • Non-hardware resources • Compute • Storage • Scaling • Cloud != virtualization

  5. Approaches to Cloud Services • Amazon Web Services (AWS) • Cloudy hardware-ish resources • Good for migration • Google App Engine (GAE) • Pure cloud resources • Bad for migration • Heroku • GAE-style services atop AWS

  6. Pros and Cons The Good The Bad No custom hardware Requires new skills IT-free Net/Info Sec • Horizontal scaling • No initial investment ($$) • IT-free • Playtime!

  7. Major Issues • Backups • Appliances • Sending email • No private internal network • No balancing on IP addresses

  8. Migrating to AWS • Hardware-ish resources • Minimal code impact • Easier migration path • Allows gradual expansion

  9. AWS Organization • AWS • 5 Regions • 2-4 Availability Zones per region

  10. AWS Components • EC2 – Elastic Compute Cloud • ELB – Elastic Load Balancer • EBS – Elastic Block Store • S3 – Simple Storage Service

  11. AWS Components • EC2 • ELB • EBS • S3 • Route 53 • Elastic Beanstalk • AutoScaling • SES • RDS • SimpleDB

  12. How We Migrated: Code • Moved MS SQL -> MySQL • Moved Windows -> Windows/Linux • Upgraded ColdFusion 8 -> 9 • Scripts for stock AMIs

  13. How We Migrated: Infrastructure • Expanded DB cluster to include AWS • Expanded App cluster to include AWS • Contracted App cluster to exclude RS • Moved DNS from RS load balancer to ELB • Contracted DB cluster to exclude RS

  14. How We Migrated: Aftermath • I/O constraints • Build parallel cluster, tested, and switched over • Background processing • Launched another app server • no user traffic / all background tasks

  15. The April 20th Outage • One AZ’s EBS freaked • No launching EBS-rooted instances in any AZ • No new volumes in any AZ • We lost ~40% of our instances • manually repointed DNS for our GSA cluster • No other user-facing failure • Multi-AZ is simply required. Period.

  16. Cloud-Based Software Evals • User requests eval • Spin up evaluation environment • RDP and run through tests • Tear down • Retain tests for later “reanimation”

  17. Soapbox* • If you're not using version control, start. Before you write another line of code. • If you don't use a Front Controller framework, start. (I like FB3Lite, but then I wrote it) • Learn about your tools. They're all far more powerful than you believe. * I’m going to read this one verbatim. Sorry.

  18. Contact bboisvert@gmail.com http://www.barneyb.com/ @barneyb

More Related