Adapter to read various sources supported by apache-libcloud and submit them to a IDB instance.

• Digital Ocean
• libvirt

To create a pex file just run make pex/idbiaas.pex. This will

1. create a virtual environment and install pex in it
2. use this virtual environment to create a pex which will be dropped to pex/idbiaas.pex

The pex file should be usable on the same os and architecture (e.g. linux and x86_64).

Create a virtualenv and activate it:

virtualenv venv
. venv/bin/activate

Install idbiaas by running pip install

pip install .

After these steps, you should have the idbiaas command installed in your virtualenv.

If you want to install manually on an older distribution, you may get errors while installing the dependencies. Upgrading pip locally in the virtual environment should fix this:

(venv) $ pip install --upgrade pip

Running idbiaas requires a configuration specifing zones to query information for. This configuration could either be loaded from a local file, or remotely from a IDB instance. Remote configuration should be the preferred way.

To use a configuation stored in a IDB, run idbiaas with the --url and --token arguments:

idbiaas --v2-url https://idb.example.org/api/v2 --token idb_api_token

or with API v3:

idbiaas --v3-url https://idb.example.org/api/v3 --token idb_api_token --config-name myconfig

If the IDB instance has a self-signed certificate, you can use the --no-verify switch to disable certificate checks.

To load a local configuration use the --config switch:

idbiaas --config idbiaas_config.json

A idbiaas configuration is stored as JSON. The root object is an object with one field "zones". The value of "zones" is an array consisting of zone objects.

A zone object has thes keys:

• idb: IDB configuration
• driver: Driver configuration

A IDB configuration object has these keys:

• url: URL where the IDB API is reached, eg. https://idb.example.org/api/v2
• version: API version to use, 2 or 3 (integer)
• token: IDB API token(s). Can be a single string or an array of strings if objects of multiple owners should be updated.
• create: set to true to create nonexisting machines in the IDB. This only works with a single token.

The contents of a driver configuration object depend on which backend is used. Currently supported are digital ocean and libvirt.

• name: digitalocean
• token: digital ocean api token
• version: digital ocean api version

Example:

{
	"name":"digitalocean",
	"token":"digitalocean_api_token",
	"version": "v2"
}

• name: libvirt
• hosts: array of hosts to query

Example:

{
	"name": "libvirt",
	"hosts": [
		{
		"name": "libvirt.example.org",
		"user": "libvirt"
		}
	]
}

• name: fqdn or ip of libvirt host
• user: user to connect as

Example:

{
	"name": "libvirt.example.org",
	"user": "libvirt"
}

{
	"zones": [
		{
			"idb": {
				"url": "https://idb.example.org/api/v2",
				"token": "idb_api_token",
				"create": true
			},
			"driver": 	{
				"name":"digitalocean",
				"token":"digitalocean_api_token",
				"version": "v2"
			}
		},
		{
			"idb": {
				"url": "https://idb.example.org/api/v2",
				"token": ["idb_api_token", "idb_api_token_2"],
				"create": false
			},
			"driver": {
				"name": "libvirt",
				"hosts": [
					{
					"name": "libvirt.example.org",
					"user": "libvirt"
					}
				]
			}
		}
	]
}