Cluj.DevOps Meetup - presentation from June 29, 2016 on how Packer, Ansible and Terraform can be used to implement Infrastructure as Code.

2. Welcome

3. Who am I?

4. Liviu Damian
Freelancer

5. Cluj.DevOps

6. Why?

7. How?

8. When?

9. We want you here :-)

10. Partners

11. Co-organizer and Technology Partner

12. Venue

13. Recruitment Partner

14. Code your Infrastructure
with Packer, Ansible and Terraform

15. Today’s Landscape

16. Complex apps === Complex infrastructure

17. Hundreds of repetitive tasks === less time for innovation

18. Infrastructure roll-back is difficult

19. ● Complex apps === Complex infrastructure
● Hundreds of repetitive tasks === less time for innovation
● Infrastructure roll-back is difficult

20. Possible Solutions?

21. Configuration Management
(Ansible, Chef, cfengine, Puppet, SaltStack)

22. Continuous Deployment
(Spinnaker, GoCD)

23. Infrastructure Orchestration
(Packer, Terraform, CloudFormation, Heat)

24. ● Configuration Management
○ Ansible
● Infrastructure Orchestration
○ Packer, Terraform

25. Benefits

26. Less risk for human error

27. Faster provisioning

28. Reduced downtime

29. Easier scalability

30. Consistency

31. Roll-back and Versioning

32. ● Less risk for human error
● Faster provisioning
● Reduced downtime
● Easier scalability
● Consistency
● Roll-back and Versioning

33. Packer

34. Modern tool for creating (not only) Cloud machine images

35. Packer Components

36. Multiple Providers
(AWS, Azure, DO, GCE, OpenStack, VirtualBox, etc.)

37. Great provisioner support
(Shell scripts, Ansible, Chef, Puppet, Salt, Powershell)

38. Post-processors
(save artifacts as Docker Image, Vagrant Machine, etc.)

39. Extendable through plugins

40. JSON Configuration File

41. ● Multiple Providers
○ AWS, Azure, DO, GCE, OpenStack, VirtualBox, etc.
● Great provisioner support
○ Shell scripts, Ansible, Chef, Puppet, Salt, Powershell
● Post-processors
○ Save artifacts as Docker Image, Vagrant Machine, etc.
● Extendable through plugins

42. Ansible

43. Idempotent Configuration Management

44. Agentless architecture

45. Orchestration over SSH (might feel slower compared to other
solutions)

46. Actions are defined in “Playbooks”

47. Playbooks are essentially YAML files

48. Reusable components (roles) in Ansible Galaxy -
https://galaxy.ansible.com/

49. ● Idempotent Configuration Management
● Agentless architecture
● Orchestration over SSH (slower, but more secure than
other solutions)
● Actions are defined in “Playbooks”
● Playbooks are essentially YAML files
● Reusable components (roles) in Ansible Galaxy -
https://galaxy.ansible.com/

50. Terraform

51. Building, Changing and Versioning Infrastructure made easy

52. Platform Agnostic

53. Simultaneously orchestrate across multiple platforms

54. Not a Configuration Management tool

55. High Level Syntax for describing resources
(similar to JSON)

56. IaaS Support
(AWS, Azure, CloudStack, DO, GCE, OpenStack, etc.)

57. PaaS Support
(Heroku)

58. SaaS Support
(CloudFlare, DNSimple, Mailgun, etc.)

59. Service Support
(Cobbler, Consul, MySQL, PostgreSQL, PowerDNS )

60. ● Building, Changing and Versioning Infrastructure made
easy
● Platform Agnostic
● Simultaneously orchestrate across multiple platforms
● Not a Configuration Management tool
● High Level Syntax for describing resources
● IaaS Support

61. DEMO

62. github.com/liviudm/cdo_cyi

63. Q&A

64. Happy break :-)