Because sahara builds on the compute base layer, it does not need to be
tested in all devstack-gate jobs. Instead create a new job that tests
sahara in a devstack environment as a first step in removing it from the
standard configuration.
Specify that SAHARA should be enabled in the devstack updown job
so that the parts that enable sahara are exercised in devstack.
This is already currently the case, but this updates the job config
so that it will continue to do so later when we remove sahara from
the default config.
Change-Id: Iae4e2439bfdfe7f3fc5f0b75b38583a70d7d78f4
Co-Authored-By: James E. Blair <jeblair@hp.com>
We'd like to check artifacts building in both check and gate
pipelines and when it'll be stabilized to publish them to
tarballs.o.o/sahara
Change-Id: Iee6d3e19900e195ca7b9d988b83debdea27df1de
Create functional test job for python-saharaclient, set as non-voting
until it's working.
Heavily inspired by the similar patches for other clients (nova, neutron,
ceilometer, etc).
This is part of the effort of moving CLI tests to project repositories.
Change-Id: I571cc8a838fb37fb1179963285e68aabf10c224a
It's working not super fast right now, so, we need to increase
timeout for buidling images from defaults 30 minutes.
Change-Id: I485f8095ecd21b4c78a0ed23f2f23a1e072f2e97