This directory contains docs explaining any peculiarities or details of a particular hypervisor's implementation.
If you don't see a file here for a hypervisor, then it's either not yet documented (feel free to help us out here!), or it should conform to our normal hypervisor assumptions.
Beaker uses credentials from a .fog file for authentication. This file came from using the fog cloud services library. Beaker now only uses fog functionality in the openstack hypervisor, but we still use the .fog file for a credentials store.
By default, the file is located under the user's home directory. This helps to keep the credentials confidential. The path of .fog file can be changed by setting the dot_fog global beaker option.
The .fog file is written in YAML. The keys are particular to the service that they correspond to, and each hypervisor's documentation should include the keys that are needed for it. An example .fog file is below:
default:
vsphere_server: 'vsphere.example.com'
vsphere_username: 'joe'
vsphere_password: 'MyP@$$w0rd'
vmpooler_token: 'randomtokentext'Note: keys can be specified as either Strings or as Ruby Symbols (e.g. :vsphere_server). For interoprability with other systems, however, it is prudent to use Strings.
The credentials file supports multiple sections. Hypervisors currently do not specify a section, and the normal behavior is to fall back to using the default section. You can override the section by specifying an environment variable, as documented on the fog website. Set ENV['FOG_CREDENTIAL'] to specify an alternative provider section and Beaker::Shared::FogFileParser.parse_fog_file() will attempt to load that section, no matter what other section the hypervisor specifies.
Puppet and its community have made several gems that support different hypervisors with beaker, the reason for this is that we're looking to decrease Beaker's dependency footprint, and hypervisors are one of the places where we can often increase the load across all Beaker uses to benefit a small group that uses a particular hypervisor.
In order to offset this, we've made a listing of gems and community-supported forks that support other external hypervisors. Please check them out if you'd like to use those hypervisors, hopefully it'll save you from spending time trying to support a new hypervisor yourself.
| Hypervisor | Fork |
|---|---|
| Vmpooler | beaker-vmpooler |
| Vcloud | beaker-vcloud |
| AWS | beaker-aws |
| Vagrant | beaker-vagrant |
| VMware/Vsphere | beaker-vmware |
| Docker | beaker-docker |
| Openstack | beaker-openstack |
| Google Compute | beaker-google |
There is another hypervisor made and used internally by puppet, beaker-abs, but it isn't included in beaker 3.x. If you'd like to use beaker-abs, you'll have to include it yourself.
You do that by requiring beaker-abs in your Gemfile as a sibling to beaker itself and then using abs as your hypervisor value in your hosts file. Please check the beaker-abs README for more information.
| Hypervisor | Fork |
|---|---|
| LXC | Obmondo |
| DigitalOcean | beaker-digitalocean |