This document discusses lessons learned from public clouds like AWS and DigitalOcean that could be applied to OpenStack projects. It covers areas like service delivery, service management, cost optimization, elastic infrastructure, and developing a DevOps culture. For each area, examples from AWS, Azure, and DigitalOcean are discussed. The document advocates taking approaches used by public clouds like custom hardware, automation, capacity planning, and ensuring easy scaling of infrastructure.

1. Lesson Learned
from Public Clouds
for OpenStack Projects
@duongkai

2. About me
• An engineer at Telco
• Interested in cloud
stuff
• It’s my personal view.

3. What I am using
• DigitalOcean -‐ personal stuff
• AWS -‐ working stuff
• OpenStack for Food
• Others: Google Cloud,
Linode, Rackspace, HP Cloud
for fun

4. WHERE ARE WE GOING?
Before we go

5. Why we want OpenStack?
• Hot term?
• VMWare alternatives?
• Choose it because of no alternatations?
• For others?

6. Subbu
Cloud Architect, Ebay
http://www.subbu.org/blog/2013/07/openstack-‐is-‐not-‐cloud

7. A cloud is a Service
and not just Software.

8. OpenStack is
a Cloud Controller Software

9. So what I learnt
• Service Delivery
• Service Management
• Cost Optimization
• Elastic Infrastructure
• DevOps culture

10. SERVICE DELIVERY
What I have learnt

11. AWS

12. Digital Ocean

13. https://wiki.openstack.org/wiki/Programs

14. Actions
• We know what we want
ü Customers
ü Current IT processes
ü Which services will we deliver? How
• VMs management solution
• Complete private cloud (﴾IaaS)﴿

15. SERVICE MANAGEMENT
What I have learnt

16. AWS

17. Digital Ocean

18. Let’s imagine
• A hardware infrastructure with dozens of
servers.
• Hundreds of VMs are running on.
è How to Manage IT EFFECTIVELY

19. Actions
• Class of service with SLA
• High-‐availability from hardware to software
• Automation is the best friend
• Processes, Change management,… è ITIL?
• Microsoft Operations Framework (﴾MOF)﴿ is a
good start.

20. COST OPTIMIZATION
What I have learnt

21. Costis always a Problems

22. COST
• Hardware, network equipments
• Operation costs
• Capacity planning and procurement
• Investment

23. Azure

24. AWS

25. AWS’s low prices
• Custom hardware
• Supply chain efficiencies
• Scale
• Frugality
"We try not to spend money on things that don’t
matter to customers.”
http://www.crn.com.au/News/382683,four-‐secrets-‐of-‐awss-‐low-‐prices.aspx#ixzz3009nMIjk

26. Actions
• Classes of HW
– Commodity hardware is prefered to Brand HW
– SANs or iSCSI
– Appliance??? NO
– VMs density. Storage density
• Software controls everything
• Automation vs Manual

27. Open Compute
Project

28. ELASTIC INFRASTRUCTURE
What I have learnt

30. Elastic Infrastructure
• Easy to scale. Scale in mindset
• Know your business carefully.
• Think big, Start small.
• Capacity Planning is a must-‐work
• Know your demand.

31. DEVOPS CULTURE
What I have learnt

32. DevOps
• DevOps (﴾a portmanteau of development and
operations)﴿ is a software development method that
stresses communication, collaboration and integration
between software developers and
information technology (﴾IT)﴿ operations professionals.
DevOps is a response to the interdependence of
software development and IT operations. It aims to help
an organization rapidly produce software products and
services.

33. DevOps
• Use of agile and other development processes
and methodologies
• Increased usage of data center automation and
configuration management tools

34. Software is Eating the world(﴾*)﴿
Marc
Andreessen
(*)
h5p://online.wsj.com/news/ar>cles/SB10001424053111903480904576512250915629460

35. Infrastructure as Code

36. Actions
• Learn how to program. Automate daily tasks
• Learn using Configuration Management
software
• Communicate effectively among developers
and ops
• OpenStack API

37. Q&A