gate-{name} will not work for migration, and while gate-{name}-fmt
and gate-{name}-unit technicall will, they're not great options.
Rename these to that they'll migrate better.
Change-Id: Ice90c30c80ce5904847bfeffcf03e52c5ad1def5
"local" implies don't use any cloud provider.
"external" implies use the standalone openstack cloud provider.
Change-Id: I8bc8cc87b421df3809f920d0a27a48fb86f52fd4
Instead of whitelist of services to run, let us disable
ones that we don't need. This will help when new services
get added and avoids job failures.
Change-Id: I2aaf88090c57e4ff8a19d24bc2a152df9b4b1a39
$BASE is not yet defined when the gate hooks are
registered, so we cannot check for the existence
of those files. Instead we check the existence of
files when the hooks are run. Also if the gate
hook is not defined then we do what is usually
done which is to run the devstack-vm-gate.sh script
Change-Id: I8e664f6633289a8514834598d72f82cc403497f4
* Check for existence of files before creating the hooks
(Improvement suggested by sdague in previous review)
* Run a minimum of services to reduce time of job to
start
* Skip tempest and exercises to reduce time
Change-Id: I096a93bf4dfe7df550af780e7828dbac127a783a
k8s-cloud-provider is an external driver for kubernetes. So
so to test code in this repo, we need to stand up a working
devstack environment, run etcd and kubernetes with proper
configuration and run kubernetes with the --cloud-provider
option pointing to our driver. Then we can run a bunch of
e2e tests say for example to test cinder integration. Any
repo that wants to use this job will need to have a devstack
plugin defined and the shell scripts for the hooks need
to be present in their proper location.
Change-Id: I03451816e2db66fbffc57a5de570f1505080bc0d
Monty Taylor