Vagrant.require_plugin 'vagrant-digitalocean'Ĭonfig.vm.provider :digital_ocean do |provider, override| The main difference between this Vagrant file and the AWS Vagrant file is that the provider block is different. Also have a look at their getting getting started guide if you're new to Digital Ocean.
If you don't already have a Digital Ocean account you can sign up for here. Java HotSpot(TM) 64-Bit Server VM (build 24.51-b03, mixed mode)Īnother cloud provider which has been gaining a lot of attention lately is Digital Ocean. Java(TM) SE Runtime Environment (build 1.7.0_51-b13) Your output should look similar to this: java -version Once your Chef run has completed you will have a new instance in Amazon running your specified version of Java. The only difference this time in running Vagrant is that you need to pass a provider argument, so your command should look like this: vagrant up -provider=aws You should replace the above bold/italics options with your own settings. _key_path = "path/to/your/awskey.pem"Ĭonfig.vm.provision :chef_client do |chef|Ĭhef.validation_key_path = '././.chef/logentries-validator.pem'Ĭhef.validation_client_name = 'logentries-validator' The reason for this is that we are going to point our Vagrant file to use an Amazon AMI instead. Again we will create a Vagrant file similar to what was done in my last blog post DevOps: Vagrant with Chef-Server, however, this time we will omit a few things like config.vm.box and config.vm.boxurl.
Vagrant aws download#
Click Download Credentials, and store the keys in a secure location.Access key ID example: ABCDEF0123456789ABCD.Your keys will look something like this:.Click User Actions, and then click Manage Access Keys.Once signed up you will need to generate an account access and secret key, to do this follow the instruction below:
If you don't already have an account I suggest you sign up for one here, and have a quick read of their EC2_GetStarted docs. The first cloud provider we will look at is Amazon AWS. More information on the plugins can be found here: Running Vagrant plugin list should give you the following output: vagrant-aws (0.4.1)
Vagrant aws install#
Vagrant plugin install vagrant-digitalocean To install the Vagrant plugins, run the following commands: vagrant plugin install vagrant-aws The omnibus is used for installing a specified version of Chef on your servers. The AWS and Digital Ocean plugins allow us to utilize both our Chef-server and the public infrastructure provided by both Amazon and Digital Ocean. We're going to focus on 3 plugins in specific: vagrant-aws, vagrant-digitalocean and vagrant-omnibus.
Vagrant has a wide range of plugins, from handling Chef and Puppet to provisioning servers on many different cloud providers. This is where Vagrant and many of its plugins shine. Dealing with the different APIs and scripts can become cumbersome and confusing when your main focus is a fault tolerant, scalable system. There are many cloud providers out there, most who provide some sort of APIs. Last updated at Sat, 11:08:40 GMT The Benefits of Vagrant Pluginsįollowing on from my recent DevOps blog posts, The DevOps Tools We Use & How We Use Them and Vagrant with Chef-Server, we will take another step forward and look into provisioning our servers in the cloud.
0 kommentar(er)
