![]() Then you can add commands which are run when the machine starts up, e.g. Then when you create an image for a specific Java application, you start with your base Java image and add the rest to it. For example, these commands could be apt get. A docker file is a sequence of commands which specify the base image and then shell commands (usually bash/Linux sh). There is a public repository with base images for you to use. Because all of it is incremental, it is pretty light weight, the base images are still big but the app-specific images are pretty light weight. The disk space which gets taken up is just the delta plus the base image (which is less than having to keep two full base images). Whereas docker images are super-light-weight, because you start with a base image and then your build a new image by adding stuff to it. If you are building an AMI you are usually talking abuot gigabytes on disk, which inherently is slow. Good for security (less software, less problems). This will in the future be used to host docker. Currently these machines are based on Ubuntu, in the future it will be CoreOS. One participant would like to use juju with openstack.Ī participant uses vagrant/openstack to launch virtual machines running on physical hardware. Juju uses charms to deploy virtual machines with services and log you with the graphical interface to connect to them. ![]() For example if you are building a Java application you can test it on a VirtualBox which is installed from vagrant, and then intelliJ can test the java application on the VM. So if you need a particular instance of MySQL and RabbitMQ for your team, you can create a vagrant project and you colleagues just need to type vagrant up in the project folder and a few minutes later they'll have a virtual machine up and running. You can also use vagrant to launch and configure an EC2 instance. Then you have a VM running that is configured according to your needs. Vagrant can start up the VM and configure it (e.g. Vagrant is really for launching and configuring one or more virtual machines. You can also create an instance which when it starts up gets and installs your application. Netflix used something similar to packer, which they may have open-sourced, and their AMIs had the application aready installed as a war file. ![]() ![]() The packer-built image has your application already installed. packer can work with chef for automation.Īt high level vagrant and packer are very similar the output of vagrant are one or more running virtual machines whereas the purpose of packer is to build an AMI.Īfter you have built an AMI you cannot really do anything with it, as you still need to run startup scripts before you can actually use it (like configuring IP, finding cluster members) so packer may save you a bit of time, but not much more.Ĭhris uses packer to create a golden master image, any specific configuration gets parsed in as user data. Standard AWS vanilla API with a default Linux, then use packer to install whatever you need onto that vanilla image. You can for example start out with a DigitalOcean Packer is a tool for the automated building of AMIs ( Amazon Machine Images), but it can also build vmware images and VirtualBox images. In this session, Chris presented packer, vagrant and docker.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |