specs and amulet tests need be to able to exercise staging and proposed cloud archive pockets

[Ryan Beisner]

OpenStack Test Specs and Amulet Tests need to be to able to pivot on different openstack-origin values.

These env vars are already set on every run in UOSCI, an could be leveraged:

  INSTALLATION_SOURCE = default|staging|proposed (not ppa: or cloud:)

  UBUNTU_RELEASE

  OPENSTACK_RELEASE

Currently, there is no mechanism to run staging or proposed cloud archive pockets in the mojo spec tests or in amulet tests.

In non-spec and non-amulet UOSCI automation, there are already environment variables set and consumed, which are parsed into corresponding target names in the deployer bundle files.

ex:

...

trusty-liberty:
  inherits: openstack-icehouse
  series: trusty
  overrides:
    openstack-origin: cloud:trusty-liberty
    source: cloud:trusty-liberty
trusty-liberty-proposed:
  inherits: trusty-liberty
  overrides:
    openstack-origin: cloud:trusty-liberty/proposed
    source: cloud:trusty-liberty/proposed
trusty-liberty-staging:
  inherits: trusty-liberty
  overrides:
    openstack-origin: ppa:ubuntu-cloud-archive/liberty-staging
    source: ppa:ubuntu-cloud-archive/liberty-staging
...

INSTALLATION_SOURCE is the existing env var.

The value is added to ${UBUNTU_RELEASE}-${OPENSTACK_RELEASE} when != default.

Common values to handle would be:
  default
  staging
  proposed

[Ryan Beisner (1chb1n)]

Helpers for OpenStack amulet tests currently do not allow passing /staging or /proposed via source or openstack-origin, due to a hard-coded version table.

http://paste.ubuntu.com/13868904/