diff options
author | Michael Drake <michael.drake@codethink.co.uk> | 2014-09-11 15:50:52 +0100 |
---|---|---|
committer | Michael Drake <michael.drake@codethink.co.uk> | 2014-09-11 15:50:52 +0100 |
commit | bdd6a8d9cd36b215b85cee507bc8919a689e0fe5 (patch) | |
tree | aa37f85086d99610355d2657df463f6ccd75949c /mason/os.conf | |
parent | 6523c60a6e918d982ac378beef48e0d3dfa0603e (diff) | |
download | definitions-bdd6a8d9cd36b215b85cee507bc8919a689e0fe5.tar.gz |
Mason: Provide moving parts needed for testing on OpenStackbaserock/michaeldrake/mason-openstack
Testing currently involves building a Baserock devel system,
deploying it as a VM and testing that that deployed VM can
build Baserock successfully.
Originally Mason used scripts/release-test to do testing on
a kvm host. In this patch the bits needed to do testing on
an OpenStack host are provided.
The new scripts/release-test-os script is based on the old
scripts/release-test, and it uses `nova` to boot/delete/etc
images and instances on OpenStack.
The mason script, `mason.sh` is updated to optionally run
either scripts/release-test-os or scripts/release-test,
depending on whether TEST_INFRA is set to 'openstack' or
'kvmhost' in the Mason's mason.conf.
The `os.conf` file is sourced by `mason.sh`, and should
be updated to contain the relevant credentials and details
for the OpenStack tenancy to be used for test deployments.
When Mason creates a test OpenStack instance, there is
potential for a race condition depending on whether ssh
comes up before the cloud-init has finished resizing the
instance's disc. If morph running on the test instance
tries to build before the disc size is increased, it will
fail complaining of insufficient free space.
To eliminate this race, the cloud init script
`os-init-script` is passed to `nova boot`. This touches
a file after the disc is resized, which Mason checks for
before it runs a `morph build`.
The `os.conf` and `os-init-script` files must both be
placed in the Mason system's `/root/` directory before
the system is deployed. This should happen in the
`mason.configure` configuration extension.
The `mason.configure` configuration extension should also
be updated to handle adding two extra variables to the
`mason.conf` file. These are the aforementioned TEST_INFRA
and OPENSTACK_NET_ID, which is the ID for the configured
OpenStack network that test instances should use.
Diffstat (limited to 'mason/os.conf')
-rw-r--r-- | mason/os.conf | 23 |
1 files changed, 23 insertions, 0 deletions
diff --git a/mason/os.conf b/mason/os.conf new file mode 100644 index 00000000..d9f69fda --- /dev/null +++ b/mason/os.conf @@ -0,0 +1,23 @@ +#!/bin/bash + +# With the addition of Keystone, to use an openstack cloud you should +# authenticate against keystone, which returns a **Token** and **Service +# Catalog**. The catalog contains the endpoint for all services the +# user/tenant has access to - including nova, glance, keystone, swift. +# +# *NOTE*: Using the 2.0 *auth api* does not mean that compute api is 2.0. We +# will use the 1.1 *compute api* +export OS_AUTH_URL=<os-auth-url> + +# With the addition of Keystone we have standardized on the term **tenant** +# as the entity that owns the resources. +export OS_TENANT_ID=<os-tenant-id> +export OS_TENANT_NAME="<os-tenant>" + +# In addition to the owning entity (tenant), openstack stores the entity +# performing the action as the **user**. +export OS_USERNAME="<os-user>" + +# With Keystone you pass the keystone password. +export OS_PASSWORD="<os-pass>" + |