Downloaded 1,095 times
![60 #Dynatrace
Ansible Concepts: Inventories
Group
Host
Numeric Range
Alphabetic Range
# production
[balancers]
www.example.com
[webservers]
www[0-9].example.com
[dbservers]
db[a:f].example.com
[monitoring]
dynatrace.example.com](https://image.slidesharecdn.com/southfloridausergroup-automateddeployments-150331141640-conversion-gate01/85/Automated-Deployments-with-Ansible-60-320.jpg)
Uploaded byMartin Etmajer
Automated Deployments with Ansible
The document provides an overview of automated deployments using Ansible, highlighting its principles and advantages in continuous delivery environments. Key points include minimizing cycle times for feature releases, the importance of early and continuous delivery of customer value, and detailed concepts such as inventories, playbooks, and roles used in Ansible. It also discusses deployment scenarios and the integration of Dynatrace with Ansible for efficient application monitoring and management.
More Related Content
Similar to Automated Deployments with Ansible
![20260201 [FOSDEM] gomodjail - library sandboxing for Go modules.pdf](https://cdn.slidesharecdn.com/ss_thumbnails/20260201fosdemgomodjail-librarysandboxingforgomodules-260201225659-76609ec4-thumbnail.jpg?width=640&height=640&fit=bounds)
Automated Deployments with Ansible
- 1. 1 #Dynatrace South FloridaUser Group, Fort Lauderdale, 31st March 2015 Martin Etmajer, Technology Strategist @Dynatrace Automated Deployments with Ansible
- 2. 2 #Dynatrace Insert image here MartinEtmajer Technology Strategist @ Dynatrace martin.etmajer@dynatrace.com @metmajer
- 3.
- 4. 4 #Dynatrace The PhoenixProject
- 5. 5 #Dynatrace The PhoenixProject: Review
- 6. 6 #Dynatrace Continuous Delivery ReliableSoftware Releases through Build, Test and Deployment Automation
- 7. 7 #Dynatrace Utmost Goal:Minimize Cycle Time feature cycle time time Customer Users
- 8. 8 #Dynatrace Utmost Goal:Minimize Cycle Time feature cycle time time Customer minimize Users
- 9. 9 #Dynatrace Utmost Goal:Minimize Cycle Time feature cycle time time Customer This is when you create value! minimize
- 10. 10 #Dynatrace Utmost Goal:Minimize Cycle Time feature cycle time time Customer You This is when you create value! minimize
- 11. 11 #Dynatrace Utmost Goal:Minimize Cycle Time feature cycle time time Customer You minimize It’s about getting your features into your user’s hands as quickly as possible!
- 12. 12 #Dynatrace “Our highestpriority is to satisfy the customer through early and continuous delivery of valuable software.” #1 Principle of the Agile Manifesto Agile Manifesto: Principle #1
- 13. 13 #Dynatrace ...which isat the heart of Continuous Delivery, defined as: “A deployment pipeline is, in essence, an automated implementation of your application’s build, deploy, test and release process.” Jez Humble & Dave Farley in Continuous Delivery Continuous Delivery Deployment Pipeline
- 14. 14 #Dynatrace Continuous DeliveryDeployment Pipeline ✔
- 15. 15 #Dynatrace Continuous DeliveryDeployment Pipeline ✔
- 16. 16 #Dynatrace Continuous DeliveryDeployment Pipeline ✔ ✔
- 17. 17 #Dynatrace Continuous DeliveryDeployment Pipeline ✔ ✔ ✔
- 18. 18 #Dynatrace Continuous DeliveryDeployment Pipeline ✔ ✔ ✔ ✔
- 19. 19 #Dynatrace ✔ ✔ ✔✔ ✔ Continuous Delivery Deployment Pipeline
- 20. 20 #Dynatrace Why? » Createapplication runtime environments on demand » Fast, reliable, repeatable and predictable outcomes » Consistent environments in staging and production » Establish fast feedback loops you can react upon » Makes release days riskless, almost boring Automated Deployments
- 21. 21 #Dynatrace “Use machinesfor what they’re good at, use people for what they’re good at.” Dave Farley at PIPELINE Conference 2014 @vimeo.com/96173993 Solve problems and be creative! Repetitive tasks
- 22. 22 #Dynatrace What? » OperatingSystems, Drivers » Middleware, Databases, etc. » Applications, Dependencies, Data Automated Deployments }+ Configuration
- 23. 23 #Dynatrace How? » Infrastructureas Code! » Keep everything in Version Control » Code » Configuration » Data » Align Development and Operations Automated Deployments Everything that affects application state
- 24. 24 #Dynatrace Align Developmentand Operations OPERATIONS DEVELOPMENT current iteration (e.g. 2 weeks) time
- 25. 25 #Dynatrace Align Developmentand Operations OPERATIONS DEVELOPMENT current iteration (e.g. 2 weeks) time Planning
- 26. 26 #Dynatrace Align Developmentand Operations OPERATIONS DEVELOPMENT current iteration (e.g. 2 weeks) time Planning Implementing and testing
- 27. 27 #Dynatrace Align Developmentand Operations OPERATIONS DEVELOPMENT current iteration (e.g. 2 weeks) time Planning Implementing and testing Working and deployable code
- 28. 28 #Dynatrace “Enable thereconstruction of the business from nothing but a source code repository, an application data backup, and bare metal resources.” Adam Jacob, CTO of Opscode
- 29.
- 30.
- 31.
- 32.
- 33.
- 34.
- 35. 35 #Dynatrace Ansible’s AgentlessArchitecture
- 36. 36 #Dynatrace Ansible’s AgentlessArchitecture
- 37. 37 #Dynatrace Ansible’s AgentlessArchitecture
- 38. 38 #Dynatrace Ansible’s AgentlessArchitecture
- 39. 39 #Dynatrace Ansible isan Orchestration Engine
- 40. 40 #Dynatrace Ansible isan Orchestration Engine
- 41. 41 #Dynatrace Ansible isan Orchestration Engine
- 42. 42 #Dynatrace Ansible isan Orchestration Engine
- 43. 43 #Dynatrace Ansible isan Orchestration Engine
- 44. 44 #Dynatrace Ansible isan Orchestration Engine
- 45. 45 #Dynatrace Ansible isan Orchestration Engine
- 46. 46 #Dynatrace What aboutDemand?
- 47. 47 #Dynatrace Global GoogleTrends: Chef vs. Puppet vs. Ansible Chef Puppet Year #1 Ansible
- 48. 48 #Dynatrace » Named#1 to watch in 2015 by SD Times » Named a Top 10 open source project by Red Hat’s opensource.com » > 1 Million Downloads » > 40 dedicated Ansible meetups (happen regularly) » > 300 customers across all verticals (Ansible Tower) » > 900 contributors on GitHub (one of GitHub’s most active projects) » AnsibleFest conferences in San Francisco, Austin & New York » “Ansible: Up and Running” book preview released by O’Reilly Ansible: Recap of 2014 (first full year of sales)
- 49.
- 50. 50 #Dynatrace » Theyintegrate nicely into your automated processes! » Automated Deployments » Configuration Management » Immutable Infrastructure » Ansible inside the Dynatrace SaaS Orchestration Platform » Whether on-prem or SaaS: automatically tested Dynatrace Automated Deployments. So what? Agents, Collectors, Servers, Clients, etc. with either of Chef, Puppet or Ansible
- 51. 51 #Dynatrace What’s theStatus?
- 52. 52 #Dynatrace Ansible Roles »Dynatrace installations » Client, Server, Collector, Agents » Fix Packs, Plugins, Licenses » Dynatrace Agent injections » Platforms: Linux Windows (soon) » Soon to come: Agent Groups, PWH Connectivity, etc. Automated Deployments: What’s the Status? ✓ ✓ ✓ ✓ ✓ ✓
- 53.
- 54. 54 #Dynatrace Dynatrace GitHubOrganization
- 55. 55 #Dynatrace Chef Cookbook »Customers have provided their own implementions » We will clean them up and open-source them soon Puppet Module » Being developed in-house in our Linz lab Automated Deployments: What’s the Status?
- 56. 56 #Dynatrace Introduction toAnsible Concepts
- 57. 57 #Dynatrace Ansible Concepts:Inventories
- 58. 58 #Dynatrace Specify theenvironment Ansible operates in. » Groups and hosts are defined in inventories » Use inventories for staging and production » Text files expressed in an INI-like format Ansible Concepts: Inventories
- 59. 59 #Dynatrace Ansible Concepts:Inventories
- 60. 60 #Dynatrace Ansible Concepts:Inventories Group Host Numeric Range Alphabetic Range # production [balancers] www.example.com [webservers] www[0-9].example.com [dbservers] db[a:f].example.com [monitoring] dynatrace.example.com
- 61. 61 #Dynatrace Ansible Concepts:Playbooks
- 62. 62 #Dynatrace Defines sequencesof tasks (Plays) to be executed on a group of hosts. » Describes policies machines under management shall enforce » Contains variables, tasks, handlers, files, templates and roles » Expressed in YAML Ansible Concepts: Playbooks
- 63. 63 #Dynatrace --- #webservers.yml - hosts: webservers tasks: - name: Install Apache HTTP Server apt: name=apache2 update_cache=yes - name: Install Apache Modules apache2_module: name={{ item }} state=present with_items: - proxy - proxy_httpd notify: reload apache2 handlers: - name: reload apache2 service: name=apache2 state=reloaded remote_user: deploy sudo: yes Ansible Concepts: Playbooks List of plays Group of hosts Documentation Module Arguments Variable Notify handler Only on state changeDebounced List of tasks Restart service
- 64. 64 #Dynatrace Ansible Concepts:Playbooks
- 65. 65 #Dynatrace --- #playbook.yml - include: dbservers.yml - include: webservers.yml - include: balancers.yml - include: monitoring.yml Ansible Concepts: Playbooks One to rule them all
- 66.
- 67. 67 #Dynatrace The bestway to organize your playbooks. » Structure content into related vars, tasks, files, handlers, etc. » File structure for automated inclusion of role-specific content » Roles can be shared and pulled from Ansible Galaxy, GitHub, etc. Ansible Concepts: Roles
- 68. 68 #Dynatrace Deployment Automationof Dynatrace with Ansible in 3 simple steps
- 69. 69 #Dynatrace Simulated ProductionEnvironment: easyTravel
- 70. 70 #Dynatrace Simulated ProductionEnvironment: easyTravel
- 71. 71 #Dynatrace Deployment ScenarioI: Install Server & Collector
- 72. 72 #Dynatrace Deployment ScenarioII: Inject Agents
- 73. 73 #Dynatrace Deployment Scenario: InstallServer & Collector
- 74. 74 #Dynatrace 1. GatherDependencies
- 75. 75 #Dynatrace Ansible Galaxy:Dynatrace-Server
- 76. 76 #Dynatrace 2. SpecifyEnvironment
- 77.
- 78. 78 #Dynatrace 3. ExecutePlaybook
- 79.
- 80. 80 #Dynatrace 1. GatherDependencies
- 81. 81 #Dynatrace Identify Technologies ApacheHTTP Server Apache Tomcat
- 82. 82 #Dynatrace Ansible Galaxy:Dynatrace-Apache-HTTPServer-Agent
- 83. 83 #Dynatrace Ansible Galaxy:Dynatrace-Tomcat-Agent
- 84. 84 #Dynatrace 2. SpecifyEnvironment
- 85. 85 #Dynatrace Identify Hosts www.easytravel.com frontend.easytravel.com backend.easytravel.com WebServer Application Servers
- 86. 86 #Dynatrace 3. ExecutePlaybook
- 87. 87 #Dynatrace Dynatrace Client:Agent Connection Status 5
- 88. 88 #Dynatrace Dynatrace Client:Transaction Flow
- 89.
- 90. 90 #Dynatrace Blogs » ContinuousDelivery 101: Automated Deployments » How to Automate Enterprise Application Monitoring with Ansible Presentations » Automated Deployments: Hands-On Training » Dynatrace Inside Continuous Delivery Tutorials » Automated Deployments with Dynatrace and Ansible Additional Resources
- 91.
Editor's Notes
- #8 Cycle time is the most relevant metric in the software delivery process. “How long would it take your organization to deploy a change that involves just one single line of code?” Mary Poppendieck
- #9 Cycle time is the most relevant metric in the software delivery process. “How long would it take your organization to deploy a change that involves just one single line of code?” Mary Poppendieck
- #10 Cycle time is the most relevant metric in the software delivery process. “How long would it take your organization to deploy a change that involves just one single line of code?” Mary Poppendieck
- #11 Cycle time is the most relevant metric in the software delivery process. “How long would it take your organization to deploy a change that involves just one single line of code?” Mary Poppendieck
- #12 Cycle time is the most relevant metric in the software delivery process. “How long would it take your organization to deploy a change that involves just one single line of code?” Mary Poppendieck
- #14 Doubtlessly, automation if of high relevance in Continuous Delivery...
- #41 Manage complex multi-tier deployments in a controlled fashion: Deploy the database before deploying web servers and enabling new web server code Configure the database with the web servers IP addresses so they can connect to it Add the web servers to a load balancing pool Add the servers to a pool of monitored hosts
- #42 Manage complex multi-tier deployments in a controlled fashion: Deploy the database before deploying web servers and enabling new web server code Configure the database with the web servers IP addresses so they can connect to it Add the web servers to a load balancing pool Add the servers to a pool of monitored hosts
- #43 Manage complex multi-tier deployments in a controlled fashion: Deploy the database before deploying web servers and enabling new web server code Configure the database with the web servers IP addresses so they can connect to it Add the web servers to a load balancing pool Add the servers to a pool of monitored hosts
- #44 Suppose that later on we want to update our web servers: Take a web server node out of monitoring and load balancing pools Update the web server code, adapt the database schema and run smoke tests Reintegrate
- #45 Suppose that later on we want to update our web servers: Take a web server node out of monitoring and load balancing pools Update the web server code, adapt the database schema and run smoke tests Reintegrate
- #46 Suppose that later on we want to update our web servers: Take a web server node out of monitoring and load balancing pools Update the web server code, adapt the database schema and run smoke tests Reintegrate
- #50 Other prominent customers who leverage Ansible Tower are: GoPro, Electronic Arts, Hughes and the NASA.
- #60 Manage complex multi-tier deployments in a controlled fashion: Deploy the database before deploying web servers and enabling new web server code Configure the database with the web servers IP addresses so they can connect to it Add the web servers to a load balancing pool Add the servers to a pool of monitored hosts
- #65 Manage complex multi-tier deployments in a controlled fashion: Deploy the database before deploying web servers and enabling new web server code Configure the database with the web servers IP addresses so they can connect to it Add the web servers to a load balancing pool Add the servers to a pool of monitored hosts