Ce diaporama a bien été signalé.
Nous utilisons votre profil LinkedIn et vos données d’activité pour vous proposer des publicités personnalisées et pertinentes. Vous pouvez changer vos préférences de publicités à tout moment.
Deploying Services: Automation
with Docker and Ansible
John Zaccone - Software Engineer
http://www.ipponusa.com
About Me
● Worked at Ippon for 1 year
● First project: Allianz Travel Insurance
● Joined the project during some big
archi...
Before
● .NET Application
3
Architectural Decisions: Requirements
● Increase sales
○ modern UI and responsive design
● Move towards Java 8 / Spring se...
Architectural Decisions: Microservices
5
After
6
Architecture Benefits
● Flexible technology choices
● APIs, APIs, APIs
● Change/Deploy Independently
● Stateless for Scala...
What Microservices Means to Us
Team Members: 4-5
Services: 4
Environments: 4
Running Application: 16+
*Each new service ad...
Things that take up my time
● Deploying services
● Installing services on new environments
● Dealing with problems with di...
I Need More Time for Coffee Breaks
Automation- repeatable for all environments
Containerize - environmental dependencies
I...
Docker and Ansible!!!
11
Docker and Ansible
Ansible
Non-environment specific
automation
Declarative
Easy for devs
12
Docker
Fast spin up
Isolated a...
Architecture With Docker Containers
13
Making the Most of Your Servers
14
Decoupling Automation from Environments
15
Decoupling Automation from Environments
16
Demo Time
17
Advanced Tips
● Build and push images with CI tools
● Link containers on the same host with --link
● Use a restart policy ...
We Do Training!
● Training Sessions
● Brown Bags
● romain@ipponusa.com
19
Questions
jzaccone@ipponusa.com
@JohnZaccone
20
Prochain SlideShare
Chargement dans…5
×

Deploying services: automation with docker and ansible

1 071 vues

Publié le

As micro-service architecture scales, the time spent provisioning new environments and deploying multiple services slows down feature development and increases time to market. In this session we will look at some ways to solve these problems- mainly using hot technologies: Docker and Ansible.

Publié dans : Ingénierie
  • Identifiez-vous pour voir les commentaires

Deploying services: automation with docker and ansible

  1. 1. Deploying Services: Automation with Docker and Ansible John Zaccone - Software Engineer http://www.ipponusa.com
  2. 2. About Me ● Worked at Ippon for 1 year ● First project: Allianz Travel Insurance ● Joined the project during some big architecture decisions 2
  3. 3. Before ● .NET Application 3
  4. 4. Architectural Decisions: Requirements ● Increase sales ○ modern UI and responsive design ● Move towards Java 8 / Spring services ● Active-Active ● Standardize on CMS Platform 4
  5. 5. Architectural Decisions: Microservices 5
  6. 6. After 6
  7. 7. Architecture Benefits ● Flexible technology choices ● APIs, APIs, APIs ● Change/Deploy Independently ● Stateless for Scalability 7
  8. 8. What Microservices Means to Us Team Members: 4-5 Services: 4 Environments: 4 Running Application: 16+ *Each new service adds at least 4 more running containers. 8
  9. 9. Things that take up my time ● Deploying services ● Installing services on new environments ● Dealing with problems with differences between environments ● Waiting for new VMs 9
  10. 10. I Need More Time for Coffee Breaks Automation- repeatable for all environments Containerize - environmental dependencies Isolation- run multiple apps on 1 VM Spin up new environments quickly. 10
  11. 11. Docker and Ansible!!! 11
  12. 12. Docker and Ansible Ansible Non-environment specific automation Declarative Easy for devs 12 Docker Fast spin up Isolated applications Immutable infrastructure “Works on my machine” Docker Toolbox
  13. 13. Architecture With Docker Containers 13
  14. 14. Making the Most of Your Servers 14
  15. 15. Decoupling Automation from Environments 15
  16. 16. Decoupling Automation from Environments 16
  17. 17. Demo Time 17
  18. 18. Advanced Tips ● Build and push images with CI tools ● Link containers on the same host with --link ● Use a restart policy on your containers ● Stay on the latest docker version ● Use ELK for centralized logging ○ Alternative: “EFK” (Fluentd in lieu of Logstash)18
  19. 19. We Do Training! ● Training Sessions ● Brown Bags ● romain@ipponusa.com 19
  20. 20. Questions jzaccone@ipponusa.com @JohnZaccone 20

×