Specs need be to able to pivot on different openstack-origin values.
Currently, there is no mechanism to run staging or proposed cloud archive pockets in the mojo spec tests.
In non-spec UOSCI automation, there are already environment variables set and consumed, which are parsed into corresponding target names in the deployer bundle files.
Specs need be to able to pivot on different openstack-origin values.
Currently, there is no mechanism to run staging or proposed cloud archive pockets in the mojo spec tests.
In non-spec 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: origin: cloud:trusty- liberty liberty liberty- proposed: origin: cloud:trusty- liberty/ proposed liberty/ proposed liberty- staging: origin: ppa:ubuntu- cloud-archive/ liberty- staging cloud-archive/ liberty- staging
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_ RELEASE} -${OPENSTACK_ RELEASE} when != default.
Common values to handle would be:
default
staging
proposed