Build cloud like Rackspace with OpenStack Ansible Workshop in 2nd Cloud OpenStack-Container Conference and Workshop 2016 at Grand Postal Building, Bangrak, Bangkok on September 22-23, 2016

1. Build Cloud like
Rackspace with
OpenStack Ansible
Jirayut Nimsaeng
DevOps & Cloud Architect
2nd Cloud OpenStack-Container Conference and Workshop 2016
Grand Postal Building, Bangrak, Bangkok | September 22-23, 2016

2. What is OpenStack
● Open source software for creating private and
public clouds
● Coordinated collection of software from a few
dozen related projects

3. What is OpenStack

4. OpenStack Core Services

5. OpenStack Optional Services

6. OpenStack Release Cycle

7. Why OpenStack?

8. Maturity

9. High Availability and Scalability

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

11. Automation Infrastructure

12. OpenStack
Core Services

13. Overview

14. OpenStack Dashboard (Horizon)
● A graphical interface to OpenStack services
● Develop on Django web application that is Python

15. Play with
Horizon

16. OpenStack Image Service (Glance)
● Managed pre-built OS images
● Accepts API requests for disk or server images
● Images can have metadata definitions
● Supports the storage of disk or server images on various
repository types

17. Play with
Glance

18. OpenStack Networking (Neutron)
● Provide networks and connectivity for instances
● Create and attach interfaces devices
● Plug-ins use to accommodate different networking
equipment and software
● It is Software Defined Networking or SDN
● And provided functionality to do Network Function
Virtualization or NFV

19. Traditional Switch Topology

20. Data Plane and Control Plane

21. Neutron Components

22. Play with
Neutron

23. Security Groups
● Named collection of network access rules to limit the types of
traffic that have access to instance
● You can assign one or more security groups to instance
● Basically it is iptables
● Any incoming traffic that is not matched by a rule is denied
access by default
● What you can configure are
○ Source of traffic
○ Protocol
○ Destination port
● Rules are automatically enforced as soon as you create or modify

24. Play with
Security Groups

25. Key Pairs
● SSH keys
● Provides SSH access to the instances
● Image must has cloud-init package
● Key pair is belongs to an individual user, not to a project

26. Play with
Key Pairs

27. OpenStack Compute (Nova)
● Virtualization
● Start and Stop VMs
● Keep track of all running VMs to do load balancing
● Report back to the cloud VM states

28. Nova Hypervisors Supported
● KVM
● LXC
● Qemu
● VMWare vSphere
● Xen
● IBM PowerVM
● Microsoft Hyper-V

29. Play with
Nova

30. Floating IP
● An IP address that a project can associate with a VM

31. Play with
Floating IP

32. OpenStack Block Storage (Cinder)
● Adds persistent storage to a virtual machine
● Managing volumes, volume snapshots and volume types
● Interacts with Nova to provide volumes for instances

33. Storage types

34. Play with
Cinder

35. OpenStack Identity (Keystone)
● Provides a single point of integration for managing
○ Authentication
○ Authorization
○ Catalog of services
● Can integrate with external user management systems such
as LDAP

36. Service Catalog
● Users and services can locate other services by using the
service catalog
● A service catalog is a collection of available services
● Each service can have one or many endpoints
● Endpoint has three types
○ admin
○ internal
○ public

37. OpenStack Keystone API V2

38. OpenStack Keystone API V3

39. OpenStack Identity Design

40. Domains

41. Groups

42. OpenStack and Active Directory

43. OpenStack Policy

44. OpenStack policy.json

45. Play with
Keystone

46. Summary

47. OpenStack
Optional Services

50. OpenStack Object Storage (Swift)
● Multi-tenant object storage system
● Highly scalable
● Can manage large amounts of unstructured data
● Low cost
● Interact with RESTful HTTP API

51. Play with
Swift

52. OpenStack Telemetry (Ceilometer)
● Collect data, store in database and provide API service
● Uses an agent-based architecture
● Still need to use command for almost features

53. Play with
Ceilometer

54. OpenStack Bare-Metal Provisioning (Ironic)
● Provides physical hardware as opposed to virtual machines
● Configure via PXE or IPMI
● Make it easy to provision physical servers like a virtual
machines in a cloud

55. OpenStack Orchestration (Heat)
● Tool for orchestrating cloud
● Automated configures and deploys resources in stacks
● Defined with templates. Heat Orchestration Template (HOT)
or Cloud Formation

56. Heat Orchestration Template

57. And many more...

58. OpenStack
Distributed Storage

59. Distributed Storage Solution

60. What is Ceph?
● Distributed storage platform
● Software-defined Storage
● Maintain by Red Hat (that acquired InkTank)
● Support Block, Object, File

61. Why Ceph?
● Enterprise Class
● Data Protection with Replication
● Self-healing
● No RAID needed
● Flexibility and Scalability (to exabyte!!)
● Performance (with RADOS)
● Lower cost (free and open source)
● Fully-tested with OpenStack

62. Way to deploy
OpenStack

64. Vendor lock-in

65. No vendor lock-in

66. Why OpenStack
Ansible?

67. Use and maintain by Rackspace and Big Tent

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

69. Infrastructure as a Code

70. Comply Security Technical Implementation Guide
http://docs.openstack.org/developer/openstack-ansible-security/auto_controls-all.html

71. Best way to learn how OpenStack working

72. OpenStack Ansible
(OSA)

73. OpenStack Ansible (OSA)
● OSA uses Ansible to automate deploy OpenStack
environment on Ubuntu Linux
● OSA deploy OpenStack components into Linux container
(LXC) for isolation and ease of maintenance

74. Ansible
● Ansible provides an automation platform to simplify system
and application deployment
● Ansible manages systems using Secure Shell (SSH)
● Ansible uses playbooks written in the YAML language for
orchestration
● Ansible host types
○ Deployment host
○ Target hosts

75. YAML

76. Linux Containers (LXC)
● Containers provide operating-system level virtualization
● No overhead and complexity of virtual machines
● Access to the same kernel, devices and file systems
● It is Linux kernel namespaces

77. Software requirements
● Ubuntu 16.04 LTS or Ubuntu 14.04 LTS
● Secure Shell (SSH) client and server that supports public
key authentication
● Network Time Protocol (NTP) client for time synchronization
● Python 2.7.x must be on the hosts
● en_US.UTF-8 as locale

78. Hardware requirements
● CPU support hardware-assisted virtualization extensions
● Disk for install OS should be SSD and doing RAID1
● Network recommended 10 Gigabit Ethernet with bonded
LACP network interfaces
● Enable jumbo frames
● Switch L3 for VLAN and support LACP

79. OpenStack Ansible Architecture

80. Infrastructure services
● MariaDB/Galera
● RabbitMQ
● MemcacheD
● Repository
● Load Balancer
● Utility Container
● Log Aggregation Host
● Unbound DNS Container

81. OpenStack Services supported
Enabled by default
● Cinder
● Nova
● Horizon
● Keystone
● Glance
● Neutron
● Heat
Not enabled by default
● Swift
● Ironic
● Aodh, Ceilometer, Gnocchi
● Magnum
● Sahara
● Aodh
● Ceilometer
● Gnocchi

82. Networking
● OSA uses Linux bridges to provide layer 2 connectivity
between interfaces and containers

83. OpenStack Ansible Network

84. OSA Network on Compute Host

85. VXLAN and VLAN

86. Cinder

87. Glance

88. Ephemeral storage

89. Storage choice
● LVM
● iSCSI
● Ceph
● SANs

90. Swift

91. How to Deploy with
OpenStack Ansible

92. OpenStack Ansible Deploy Steps

93. Q/A

94. Backup Slides

95. OpenStack CLI

96. Automated configure commands

97. Some tips

98. Caching

99. OpenStack
Network

100. OpenStack Network
● Single Flat Network
● Multiple Flat Networks
● Mixed Flat + Private Networks
● Single Provider Router
● Per-Tenant Router

101. OpenStack Network

102. VLANs or VXLANs?

103. VLANs Network Traffic Flow