OpenStack Journey to implement private cloud at Kaidee in 2nd Cloud OpenStack-Container Conference and Workshop 2016 at Grand Postal Building, Bangrak, Bangkok on September 22-23, 2016.

1. OpenStack at
OpenStack Ansible use case for private cloud
Jirayut Nimsaeng (Dear)
DevOps & Cloud Architect
2nd Cloud OpenStack-Container Conference and Workshop 2016
Grand Postal Building, Bangrak, Bangkok | September 22-23, 2016

2. $ WHOAMI
● Jirayut Nimsaeng (Dear)
● DevOps and Cloud Architect at
● Interested in Open Source and
Cloud Automation
● OpenStack Contributor

3. We are the biggest used goods
marketplace in Thailand

4. Source: http://www.fmi.org/research-resources/supermarket-facts
More than 1.3M items online everyday
Our market is equivalent to 30 supermarkets
combined.

5. 40 milion
screen views
per day

6. 650,000 daily unique visitors
It is eight times bigger than Thailand’s
national football stadium.

7. 4
Seconds
a new
item is
listed
every

8. http://bits.citrusbyte.com/microservices/
We do microservices architecture.
many microservices
has been added in past year

9. Why Cloud?

10. Automation Infrastructure

11. Self Service

12. Faster Business

13. Public or Private Cloud?

14. Public and Private Cloud players

15. Public and Private Cloud characteristics
Public Cloud
● OPEX
● No admin expense
● Easy to scale
● Easy to start with small price
● Difficult to track resource
● Difficult to limit quota
● Difficult to control expense
Private Cloud
● CAPEX
● Need expert admin or vendors
● Need time to buy hardware to scale
● High invest and effort
● Easy tracking resource
● Easy to setup quota on project
● Allocated expense

16. Why OpenStack?

17. APIs first

18. Maturity

19. High Availability and Scalability

20. Cost saving
http://www.slideshare.net/randybias/openstack-architected-like-aws-and-gcp

21. Open Source & Ready for Production

22. No vendor lock-in

23. Awesome Team

24. Kaidee’s
OpenStack
Journey

31. Why OpenStack
Ansible?

32. Use and maintain by Rackspace and Big Tent

33. Because it is Ansible
● Agentless architecture
● No centralized server
● Human readable
● Open Source
● Highly flexible and configurable
● Idempotent

34. Infrastructure as Code
From example configuration in OpenStack Ansible document

35. Complies with Security Technical Implementation Guidelines
http://docs.openstack.org/developer/openstack-ansible-security/auto_controls-all.html

36. The best way to learn how OpenStack works

37. Kaidee after
OpenStack

38. Reduced time to deploy a new service
Significantly reduce from daysto an hour

39. Playground for Developer

40. Cost for scaling

41. Next steps

42. Maintenance and Upgrading

43. OpenStack Ironic

44. OpenStack Designate