Upload
manohar-kumar
View
85
Download
2
Embed Size (px)
Citation preview
Introduction to DevOps
DevOps practices are most powerful when applied in contexts with software delivery and IT change management.
DevOps, by definition, is never a “one size fits all” remedy.
DevOps uses automation techniques to increase collaboration across development and operations, enabling faster, more predictable and more frequent deployments to market.
DevOps is about drilling down your organisation's specific problem and challenges and resolve them.
DevOps isn’t just a set of tools, but a philosophical shift that requires a buy-in from all folks involved for it to truly succeed.
DevOps teams are finding it efficient to configure dev/test environments based on Docker.
Docker for Windows and Mac Public Beta
Docker for Mac does not use VirtualBox, but rather HyperKit, a lightweight OS X virtualization solution built on top of Hypervisor.framework in OS X 10.10 Yosemite and higher.
Installing Docker for Mac does not affect machines you created with Docker Machine.The install offers to copy containers and images from your local default machine (if one exists) to the new Docker for Mac HyperKit VM. If chosen, content from default is copied to the new Docker for Mac HyperKit VM, and your original default machine is kept as is.
The Docker for Mac application does not use docker-machine to provision that VM but rather creates and manages it directly.
At installation time, Docker for Mac provisions a HyperKit VM based on Alpine Linux, running Docker Engine. It exposes docker API on a socket in /var/tmp/docker.sock. Since this is the default location where docker will look if no environment variables are set, you can start using docker and docker-compose without setting any environment variables
Install Docker for windows and docker for Mac
Download docker for windows and docker for mac from below URL
http://www.docker.com/products/overview
After the installation you will see docker running in status bar or process status
Swarm Mode
Combine your engines in swarms of any scale
Self organizing
Self healing
No external data store required
No single point of failure
Infrastructure-agnostic topology
Built-in Routing Mesh
Swarm-wide overlay networking
Container-native load balancing
DNS based service discovery
No separate cluster to setup
Works with your existing load balancers
Rock Solid kernel-only data path with IPVS
Docker Service API
Desired State reconciliation
Scaling
Rolling updates
Advanced Scheduling
Application-specified health checks
Rescheduling on node failure
Whats Next
Docker for AWS and Docker for Azure