AnsibleWorkshopMay2019.pdf

https://dipsas.github.io/AnsibleCourse/

Transcript

1. and infrastructure as code workshop Andreas Mosti
2. Key takeaways • Infrastructure as Code • Configuration Management • What can Ansible solve? • What can it not solve? • Enough knowledge to understand the key principles
3. Dev/Build Runtime
4. Dev/Build Runtime
5. Dev/Build Runtime
6. Dev/Build Runtime
8. The complexity moves
11. Site A Site A Replica Site B Replica Site B
12. • Application platforms / runtimes • Permissions • Users • Firewall rules • Config Files • Updates • Running Services • Upgrades
13. • Application platforms / runtimes • Permissions • Users • Firewall rules • Config Files • Updates • Running Services • Upgrades 20
15. Inconsistent server farms
16. Platform requirements, «What are we releasing on?»
17. «We need new environments quickly, in a reproducible fashion»
18. Automate the infrastructure
19. Snowflake vs. Phoenix Servers
20. Infrastructure as code:
21. Reproducible Environments
22. Servers in version control
23. Configuration management
24. Explicit process
25. Safety!
26. Code Review
27. Baked vs. Fried servers
28. The usual suspects
31. Why Ansible?
34. Open Source
35. SSH WinRM
36. Most important:
37. The correct abstraction (for us)
39. Playbooks push Database Appserver Load Balancer
41. Remember: Ansible keeps state
42. The benefits of Infrastructure as Code: 1) Automation 2) Version control 3) Code Review 4) Testing 5) Documentation 6) Reuse
43. The holy grale: Imutable infrastructure
44. Warning 1:
49. The files don’t represent reality!
51. Warning 2:
52. If not run often, the system might regress
53. Part 1: Inventory and connection
54. SSH WinRM
55. WinRM Port 5986 Local / AD admin user w. remoting Powershell 3.0 ConfigureRemotingForAnsible.ps1
56. SSH Port 22 root / dedicated user(s)
59. The Inventory
60. inventory/Example.inventory
61. inventory/Testlab18.inventory
62. Exercise 1: Inventory and server connection
63. Part 2: Playbooks and tasks
64. Playbooks push Database Appserver Loadbalancer
65. LoadBalancer.yaml Zookeeper.yaml Solr.yaml Database.yaml ArenaAppServer.yaml
66. WebServer.yaml
67. WebServer.yaml
68. WebServer.yaml
69. WebServer.yaml
70. roles/DotNet461/tasks/main.yaml
73. Exercise 2: Playbook and simple tasks
74. Part 3: Roles and variables
75. WebServer.yaml
76. To reuse tasks or implement components, we make roles
77. Example roles: • IIS • DotnetFramework45 • Oracle12C • TeamcityAgent • Java • GoogleChrome • SplunkForwarder
79. Buildserver.yaml
80. roles/Oracle12Driver/tasks/main.yaml
81. roles/Oracle12Driver/tasks/main.yaml
82. roles/Oracle12Driver/defaults/main.yaml
83. Lists and iterators
84. roles/Zookeeper/tasks/main.yaml roles/Zookeeper/defaults/main.yaml
85. A word on variable precendence
86. From least to most important: • role defaults • group_vars/ • host_vars/ • host facts • play vars • include_vars • set_facts • extra vars
87. A word on state and idempotency
88. Always pick modules over shell commands (if possible)
89. roles/MKDocs/tasks/main.yaml
90. roles/MKDocs/tasks/main.yaml
91. Exercise 3: Roles, variables and iterators
92. Part 4: Handlers, templates, files
94. Files vs Templates
95. roles/TeamCityAgent/tasks/main.yaml
96. True configuration management with templating and JINJA2
97. roles/TeamCityAgent/templates/buildAgent.properties
98. roles/SplunkForwarder/templates/input.conf.j2
99. roles/HAProxy/templates/haproxy.conf.j2
100. roles/Prometheus/templates/alertmanager.yml.j2
101. roles/Prometheus/defaults/main.yml
102. roles/TeamCityAgent/tasks/main.yaml
103. roles/TeamCityAgent/handlers/main.yaml
104. Exercise 4: Templates, handlers and files
105. Part 5: Ansible Vault
106. When working with secrets roles/TeamCityAgent/tasks/main.yaml
107. roles/TeamCityAgent/defaults/main.yaml
109. roles/TeamCityAgent/defaults/main.yaml
111. roles/TeamCityAgent/defaults/main.yaml
112. Exercise 5: Vault and encryptet secrets