Transcript
Page 1: CloudStack Day 14 - Automation: The Key to Hybrid Cloud

Automation: The Key To Hybrid CloudMichael Ducy — Enterprise Architect — Chef @mfdii

Page 2: CloudStack Day 14 - Automation: The Key to Hybrid Cloud

• Linux Engineer

• Operations

• Performance Engineer

• Capacity Planning

• Cloud Architect

• Automation

• Chef

• MBA, MS

Page 3: CloudStack Day 14 - Automation: The Key to Hybrid Cloud
Page 4: CloudStack Day 14 - Automation: The Key to Hybrid Cloud

P2V Your Technical Debt

VM Converter

Page 5: CloudStack Day 14 - Automation: The Key to Hybrid Cloud

Why the technical debt?

Page 6: CloudStack Day 14 - Automation: The Key to Hybrid Cloud

Failure to capture configurations

• Manual Changes

• Not Captured in a repeatable format

• Changes poorly documented

Page 7: CloudStack Day 14 - Automation: The Key to Hybrid Cloud

Large cumbersome automation

• Hard to use

• Not Repeatable

• Not Idemoptent

• Not Convergent

Page 8: CloudStack Day 14 - Automation: The Key to Hybrid Cloud

Low perceived value of automation

• Quicker to do it manually

• Focuses on longer term results

• Payback period for automation

Page 9: CloudStack Day 14 - Automation: The Key to Hybrid Cloud

Images are all I need

• Golden Images

• Build images to repeat configurations

Page 10: CloudStack Day 14 - Automation: The Key to Hybrid Cloud

Enter Hybrid Cloud

Page 11: CloudStack Day 14 - Automation: The Key to Hybrid Cloud
Page 12: CloudStack Day 14 - Automation: The Key to Hybrid Cloud

Magic Bits

Page 13: CloudStack Day 14 - Automation: The Key to Hybrid Cloud

Magic Bits

Page 14: CloudStack Day 14 - Automation: The Key to Hybrid Cloud

Problems

• VMs are heavy

• C2Cing your technical debt

• Large management overhead

• Doesn’t really realize the benefits of Cloud

Page 15: CloudStack Day 14 - Automation: The Key to Hybrid Cloud

CFG

CFG

CFG

CFG

CFG

CFGCFG Automation

Page 16: CloudStack Day 14 - Automation: The Key to Hybrid Cloud

Solutions

• Configs lighter than VMs

• Reduces moving data already in your Clouds

• Can leverage things like SCM

• Define once, run anywhere

Page 17: CloudStack Day 14 - Automation: The Key to Hybrid Cloud

Problems

• Requires discipline

• Doesn’t solve data issues

• Requires upfront investment of time

Page 18: CloudStack Day 14 - Automation: The Key to Hybrid Cloud

The question isn’t: how do I get a server, defined by VM (or instance) into another

Cloud to serve my application

Page 19: CloudStack Day 14 - Automation: The Key to Hybrid Cloud

The question is: how do I get a server, defined by a set of finite configurations,

into another Cloud to serve my application

Page 20: CloudStack Day 14 - Automation: The Key to Hybrid Cloud

Some things I’ve seen work

• Ignore legacy

• Focus on Cloud first

• Get development buy-in to change app stack

• Build Composable, Data Driven Automation

Page 21: CloudStack Day 14 - Automation: The Key to Hybrid Cloud

Infrastructure as Code

Page 22: CloudStack Day 14 - Automation: The Key to Hybrid Cloud

TDD of Infrastructure Code

• Test Driven Development

• Verify before deployment

• Reduce development time

Page 23: CloudStack Day 14 - Automation: The Key to Hybrid Cloud

Leverages Software Development Lifecycle

• Infrastructure Code stored in Source Control

• Who, What, When, Why, How

Page 24: CloudStack Day 14 - Automation: The Key to Hybrid Cloud

Repeatable and Reusable

• Write once, Run anywhere

• Cross Cloud, Cross Platform

Page 25: CloudStack Day 14 - Automation: The Key to Hybrid Cloud

Additional Requirements

• API Based automation

• Node based evaluation and execution

• Declaritive DSL

• Flexibility of real language

Page 26: CloudStack Day 14 - Automation: The Key to Hybrid Cloud

Questions?

Page 27: CloudStack Day 14 - Automation: The Key to Hybrid Cloud

Automation: The Key To Hybrid CloudMichael Ducy


Top Related