Your SlideShare is downloading. ×
 RootConf 2014 Bangalore: Automating the Dev Environment - Introduction to Docker and Chef
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×

Saving this for later?

Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime - even offline.

Text the download link to your phone

Standard text messaging rates apply

RootConf 2014 Bangalore: Automating the Dev Environment - Introduction to Docker and Chef

1,906
views

Published on

Published in: Technology

0 Comments
2 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
1,906
On Slideshare
0
From Embeds
0
Number of Embeds
3
Actions
Shares
0
Downloads
5
Comments
0
Likes
2
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. AUTOMATING DEV ENVIRONMENT INTRODUCTION TO DOCKER & CHEF Kamalika Majumder
  • 2. Nightmares working on local dev env  Too many manual tasks required in setup  Performance issue/machine is too slow  Inconsistency with production environment  My code works fine only on my machine but not in production.
  • 3. How to solve  Environment on Demand  Automated Configuration Management  Faster Deployment cycle  Better performance
  • 4. Introduction to Docker  An open source software used to perform various operations with linux containers.  Helps in creating environment on demand.  Containers are light weight(Typical laptops can run around 10-100 containers)  Simple and easy CLI , makes it easy to script  Using Docker registry makes it easier to share linux containers across the teams.
  • 5. Why Docker
  • 6. • Run docker images • Docker File usage • Docker registry Short Demo
  • 7. Key Notes  100 Docker instances does not mean 100 VMs.  Each docker run command is run as a process on the host machine.  Docker is still under development, so it is not yet recommended for production  Distros : Ubuntu, Centos, Redhat .In order to make it work on mac you need a VM with the above distros.  By default it works on bridge network - docker0 , each containers gets a virtual interface and a specific ip from same range as docker0 .We can also configure specific ip ranges.
  • 8. Chef for Configuration Management  Automated configuration for app deployment  Consistency of configuration across environments  Freedom from repetitive manual software installations.  Easy to integrate with various cloud platforms (ec2,openstack etc).
  • 9. Recipes/CookbooksRolesEnvironment Dev QA Staging Webserver/Appserver Node1 Node2 DB Node3
  • 10. Docker + Chef lxc lxclxclxclxc Dev Environment Environment on demand Autamated software configuration Ready to deploy Application
  • 11. To be continued …..  Reference websites: https://www.docker.io/
  • 12. Questions ?