• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
DevOps Days Tel Aviv 2013: Ignite Talk: How to make deployments work on multiple clouds - Leonid Mirsky
 

DevOps Days Tel Aviv 2013: Ignite Talk: How to make deployments work on multiple clouds - Leonid Mirsky

on

  • 421 views

In this talk Leonid will share his experience of taking an AWS only deployment process and extending it to support both private and public clouds (Openstack and Rackspace). If you think that all ...

In this talk Leonid will share his experience of taking an AWS only deployment process and extending it to support both private and public clouds (Openstack and Rackspace). If you think that all clouds were born the same, think again! The road to a truly multi cloud provisioning isn't so simple. Leonid will provide some technical tips about what you should expect when you are getting outside of the AWS garden, as well as some practical technical examples of how you can overcome some common pitfalls.

Speaker:

Leonid Mirsky

Leonid has more than 10 years experience in different IT operations roles. Currently, as an Independent consultant, he is helping small to medium sized companies to implement DevOps and to realize the potential power of cloud computing.

Statistics

Views

Total Views
421
Views on SlideShare
421
Embed Views
0

Actions

Likes
1
Downloads
8
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    DevOps Days Tel Aviv 2013: Ignite Talk: How to make deployments work on multiple clouds - Leonid Mirsky DevOps Days Tel Aviv 2013: Ignite Talk: How to make deployments work on multiple clouds - Leonid Mirsky Presentation Transcript

    • A Story of Multi-cloud Provisioning @leonidlm
    • multi-cloud? Disaster recovery Why go
    • multi-cloud? Best cloud for the job Why go
    • Xplenty Code free Hadoop
    • Xplenty Cluster deployment architecture 1 2 New Worker Queue Worker Worker 3
    • Xplenty Cluster deployment architecture 1 2 New Worker Queue Worker Worker 3
    • Amazon just works! How about the others?
    • 1 Lack of network automation Public DNS: ec2-54-224-106-95.compute-1.amazonaws.com Public IP: 54.224.106.95 Private DNS: ip-10-31-133-57.ec2.internal Private IP: 10.31.133.57
    • 1 Lack of network automation Public DNS: ec2-54-224-106-95.compute-1.amazonaws.com Public IP: 54.224.106.95 Private DNS: ip-10-31-133-57.ec2.internal Private IP: 10.31.133.57
    • 1 Lack of network automation Solutions ✓ Use public DNS service (route53) a. Manage your own DNS
    • 2 Tools compatibility Typical request for a new ec2 instance: a. b. c. d. Instance type image id Security groups user data (can be a script) #!/bin/bash apt-get -y update apt-get -y upgrade apt-get install puppet
    • 2 Tools compatibility #!/bin/bash apt-get -y update apt-get -y upgrade apt-get install puppet Solutions ✓ Configure using SSH after instance is ready
    • 3 Variable instance sizes m1.xlarge CPUs Similar instance size on another provider 4 8 Memory 15G 16G Storage 840G 160G
    • How does it work in Production?
    • 4 API behaviour nuances cloud has its own Weak spots! Each
    • 5 Performance Cloud Amazon HP Rackspace Region Virginia Oregon Az1 Az2 Az3 Chicago Dallas Average launch time 1.5 2 2.5 3 2.5 8 7 Error rate 1.12% 0.63% 3.30% 0.81% 2.33% 12.37% 9.16% http://www.ravellosystems.com/blog/cloud-dashboard-part-1-vm-provisioning/
    • 5 Performance Solutions ✓ Easy regions on/off switch ✓ Configure different retry times based on cloud performance
    • Summary a. b. c. d. Lack of network automation Tools compatibility Variable instance sizes Providers performance & behaviour differences
    • Plan for the lowest common denominator
    • Thank you! @leonidlm leonidlm@gmail.com