This document discusses moving from traditional on-premise data centers to cloud and DevOps models. It emphasizes automating servers, treating configuration as code, continuous integration and deployment, monitoring with metrics, and adopting an agile development approach to release more frequently with higher quality and reliability. The document is presented by Fernando Honig from Rackspace on cloud and new datacenter service models using DevOps.
6. 3 MYTHS ABOUT CLOUD:
• Is not secure:
– Truth: Public cloud is multi-tenant. You potentially could have noisy neighbors.
– Remediation: On-Premise cloud, Virtual Private Cloud, Hybrid Cloud
• Is too complex:
– Truth: Different types of cloud, with differing levels of complexity.
– Remediation: Choose a cloud provider who can offer you tools and support
• Cloud is for everything:
– Truth: Not all applications are suitable for cloud computing.
– Remediation: There will be situations where security requirements, flexibility,
performance or control will preclude the cloud
9. Let’s focus on..
• Server Automation
• Configuration Management
• Everything as a Code
• Code Repositories
• Testing Overview
• M-T-V
• Money
• Time
• Value
CLOUD + DEVOPS
NEW DATACENTER SERVICE MODEL
10. AUTOMATE YOUR SERVERS
Everything IS code!
Treat your Servers as Commodities
No Server should be “special”
• Should be no “droideka”, “skywalker”, “backup01” names
You might be able to remove a server with zero
consequences
15. EVERYTHING AS A CODE
Code repositories
Create the same Development lifecycle
Your Server code is also an application!
16. M-T-V
M-Money
No need to buy expensive tools
No “deployment nights/weekends” anymore
Less outage
T-Time
Speed up your deployment cycle
V-Value
Code Tested
Common goal across organizations
17.
18. DevOps!
• Culture and Work methodology
• Set of tools
• Config Management
• Code Management
• Testing
• Monitoring
CLOUD + DEVOPS
NEW DATACENTER SERVICE MODEL
21. DEVOPS!
Be Agile
Agile methodologies help you get there early
Release early, release often
Release several times a day
Code + CI/CD ensures quality
34. CONTINUOUS DEPLOYMENT
• Also known as CD
• It’s an optional extension to CI
• Once a piece of code has been through CI
releases it automatically
• Very useful for bugs and minor changes