specs and amulet tests need be to able to exercise staging and proposed cloud archive pockets
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Charm Testing |
New
|
Undecided
|
Unassigned | ||
Openstack Mojo Testing |
New
|
Undecided
|
Unassigned |
Bug Description
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_
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-
source: cloud:trusty-
trusty-
inherits: trusty-liberty
overrides:
openstack-
source: cloud:trusty-
trusty-
inherits: trusty-liberty
overrides:
openstack-
source: ppa:ubuntu-
...
INSTALLATION_SOURCE is the existing env var.
The value is added to ${UBUNTU_
Common values to handle would be:
default
staging
proposed
description: | updated |
summary: |
- specs and amulet tests need be to able to pivot on different openstack- - origin values + specs and amulet tests need be to able to exercise staging and proposed + cloud archive pockets |
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/