vagrant-digitalocean
is a provider plugin for Vagrant that supports the
management of Digital Ocean droplets
(instances).
NOTE: The Chef provisioner is no longer supported by default (as of 0.2.0).
Please use the vagrant-omnibus
plugin to install Chef on Vagrant-managed
machines. This plugin provides control over the specific version of Chef
to install.
Current features include:
- create and destroy droplets
- power on and off droplets
- rebuild a droplet
- provision a droplet with the shell or Chef provisioners
- setup a SSH public key for authentication
- create a new user account during droplet creation
The provider has been tested with Vagrant 1.1.5+ using Ubuntu 12.04 and CentOS 6.3 guest operating systems.
Installation of the provider requires two steps:
-
Install the provider plugin using the Vagrant command-line interface:
$ vagrant plugin install vagrant-digitalocean
NOTE: If you are using a Mac, you may need to install a CA bundle to enable SSL communication with the Digital Ocean API. It is recommended to first install Homebrew. With Homebrew installed, run the following command to install the bundle:
$ brew install curl-ca-bundle
Once the bundle is installed, add the following environment variable to your
.bash_profile
script and source
it:
export SSL_CERT_FILE=/usr/local/opt/curl-ca-bundle/share/ca-bundle.crt
Once the provider has been installed, you will need to configure your project
to use it. The most basic Vagrantfile
to create a droplet on Digital Ocean
is shown below:
Vagrant.configure('2') do |config|
config.vm.provider :digital_ocean do |provider, override|
override.ssh.private_key_path = '~/.ssh/id_rsa'
override.vm.box = 'digital_ocean'
override.vm.box_url = "https://github.com/smdahlen/vagrant-digitalocean/raw/master/box/digital_ocean.box"
provider.client_id = 'YOUR CLIENT ID'
provider.api_key = 'YOUR API KEY'
end
end
Please note the following:
- You must specify the
override.ssh.private_key_path
to enable authentication with the droplet. The provider will create a new Digital Ocean SSH key using your public key which is assumed to be theprivate_key_path
with a .pub extension. - You must specify your Digital Ocean Client and API keys. These may be found on the control panel within the My Settings > API Access section.
Supported Configuration Attributes
The following attributes are available to further configure the provider:
provider.image
- A string representing the image to use when creating a new droplet (e.g.Debian 6.0 x64
). The available options may be found on Digital Ocean's new droplet form. It defaults toUbuntu 12.04.3 x64
.provider.region
- A string representing the region to create the new droplet in. It defaults toNew York 2
.provider.size
- A string representing the size to use when creating a new droplet (e.g.1GB
). It defaults to512MB
.provider.private_networking
- A boolean flag indicating whether to enable a private network interface (if the region supports private networking). It defaults tofalse
.provider.backups_enabled
- A boolean flag indicating whether to enable backups for the droplet. It defaults tofalse
.provider.ssh_key_name
- A string representing the name to use when creating a Digital Ocean SSH key for droplet authentication. It defaults toVagrant
.provider.setup
- A boolean flag indicating whether to setup a new user account and modify sudo to disable tty requirement. It defaults totrue
. If you are using a tool like packer to create reusable snapshots with user accounts already provisioned, set tofalse
.
The provider will create a new user account with the specified SSH key for
authorization if config.ssh.username
is set and the provider.setup
attribute is true
.
After creating your project's Vagrantfile
with the required configuration
attributes described above, you may create a new droplet with the following
command:
$ vagrant up --provider=digital_ocean
This command will create a new droplet, setup your SSH key for authentication, create a new user account, and run the provisioners you have configured.
Supported Commands
The provider supports the following Vagrant sub-commands:
vagrant destroy
- Destroys the droplet instance.vagrant ssh
- Logs into the droplet instance using the configured user account.vagrant halt
- Powers off the droplet instance.vagrant provision
- Runs the configured provisioners and rsyncs any specifiedconfig.vm.synced_folder
.vagrant reload
- Reboots the droplet instance.vagrant rebuild
- Destroys the droplet instance and recreates it with the same IP address is was assigned to previously.vagrant status
- Outputs the status (active, off, not created) for the droplet instance.
To contribute, clone the repository, and use Bundler to install dependencies:
$ bundle
To run the provider's tests:
$ bundle exec rake test
You can now make modifications. Running vagrant
within the Bundler
environment will ensure that plugins installed in your Vagrant
environment are not loaded.