Automated environment provisioning and use of virtualization isolate environments is a topic that has become quite important to me – and to many others. From virtual machine technology, such as VMWare, VirtualBox and Oracle VM, to more recently the use of container technology and especially Docker, I am constantly trying to wrap my head around things and find ways of efficiently, smoothly hence automatedly working with environments. Vagrant has been a great tool for me to produce VirtualBox machine images that I use for a host of things including development environments. I have frequently used Puppet in conjunction with Vagrant to do the detailed configuration of the Virtual Machine – including the installation of various software packages.
Docker is of interest for several reasons: Docker containers while isolated share their host operating systems and its physical resources which means that a collection of Docker containers can provide (almost) the same isolation as a series of Virtual Machines but with much smaller overhead – in terms of usages of disk, CPU and memory and in terms of time required for starting up and shutting down. Additionally, the management of Docker containers – from 10Ks of images to start from and a layered mechanism to extend and revert – has a number of attractive options. A Docker container – once configured and runnable – can be distributed fairly easily – using a public or private registry – and can also be deployed to a growing number of enterprise stacks (such as OpenStack cluster) and public cloud providers.
Please click here for complete blog.
No comments:
Post a Comment