8 Commits

Author SHA1 Message Date
Ian Wienand
b08153e79d Switch nova-docker-f20 job to centos7
F20 nodes are having issues at the moment, and F20 is getting a bit
old anyway.  Move this to centos7 which is a better choice for
long-term testing.

Change-Id: Ifa742ba5bdae0b796b8b92336e41234fd8b7939e
2015-03-25 10:13:02 +11:00
Davanum Srinivas
93204bdc4e Copy over pre/post test hooks to check-tempest-dsvm-f20-docker
The trusty based check-tempest-dsvm-docker job is working fine
now. Let's copy the hooks to the fedora based job as well.

Change-Id: I2a561565aa0e963e9fc6797d44baba22d190b4e2
2014-12-19 12:18:31 -05:00
Davanum Srinivas
dd4ce21d6c Oops! - Remove extra braces in nova-docker pre/post hook
Change-Id: If9d85c64497beaaec526b5bcf2c78e67453179a2
2014-12-18 19:30:49 -05:00
Davanum Srinivas
f17433fa30 Support pre/post test hooks for nova-docker jobs
Change-Id: I48944176d5c0c1a044e12bf771bfa5a1c997580b
2014-12-18 15:35:47 -05:00
Clark Boylan
fc9e6ce561 Use devstack-logs macro in docker jobs
The docker jobs were explicitly running SCP to copy their job logs but
did so poorly by unsetting the keep hierarchy option. Switch these jobs
to the devstack-logs macro so that they are always up to date and
correct.

Change-Id: Ib311b23aa12e788918bda1f39d64728a384f5017
2014-12-04 14:43:15 -08:00
Davanum Srinivas
a7a832213a remove non-standard-reqs flag from check-tempest-dsvm-f20-docker
Introduced a flag in I1fb4d58a36c9a12f87527f4fb551f4b664c386bd, this
does not work when we set it from here. So this review removes the
NON_STANDARD_REQS flag. The reason it does not work is that
devstack runs stack.sh with sudo and the environment variable is not
passed down into the process.

Change-Id: I379a5e6c566e8ac207c70089f3251eff6afe3379
2014-10-17 09:39:45 -04:00
Davanum Srinivas
25bb27f6ff Allow non standard docker-py in check-tempest-dsvm-f20-docker
We are investigating the use of docker-py to get rid of a custom
http client and switch to a standard library docker-maintained
by docker folks. So we need these dsvm jobs at the very least
to see what works and what doesn't and how much regression we have

There are 2 dsvm jobs for nova-docker, we are making the change
of switching on NON_STANDARD_REQS only for the f20 one. As we
just need data points to make sure we are not regressing the
nova-docker driver as compared to existing functionality in the
review mentioned below. Best case scenario, switching on the
flag works as advertised and the requirements check will not
fail the dsvm job at the point it is failing now. Worst case
scenario the flag has no effect and we can delete the line
flag at that point.

Review against nova-docker:
I3e17924b8319720ceb7cee480a81e953b809d0ee

Review for docker-py in global requirements:
I3100ad32a1cb414033a3aee495ddd6b82e6af268

Change-Id: I1fb4d58a36c9a12f87527f4fb551f4b664c386bd
2014-10-16 19:35:43 -04:00
Anita Kuno
1d21cd635f Reorganizes project-config
This repo was created from filter branching the openstack-infra/
config repo. This process brought a lot of cruft with it in the
form of directories that we no longer need. This patch removes
that cruft so we begin with a tidier repo.

Change-Id: Ibffad1b11c0c5f84eedfb0365369f60c4961a0f3
2014-09-25 11:41:04 -04:00