The content from the openstack-ansible-py_from_git repository
is no longer needed.
This patch implements the retirement of the py_from_git
repository from gate testing as per [1].
[1] http://docs.openstack.org/infra/manual/drivers.html#retiring-a-project
Depends-On: I1f024d0e81a1245c7181a69b365834dd32d1729b
Change-Id: I1af414d5f1f2290e7bfebb3153ef829c87f0c3f0
Currently all pip install tasks only require the package to be
present. This means that when an environment undergoes a minor
upgrade the package is not upgraded to the same version that
was tested with. This ultimately results in a deployed
environment that does not match the tested environment.
While for the services installed into venvs this is not an
issue, it does affect those which do not use venvs and any
packages which are installed outside of a venv or on top
of a venv.
This patch changes the behaviour to ensure that the install
task will always use the latest available package. In
developer_mode this will mean using the version specified
in upper-constraints, and in an integrated build this will
mean the version which is available in the wheel repo's
folder for the tag.
Change-Id: I1b9ef8cd0e36dcf2cd20b27292741dda2c0efd0f
Paramiko version 2.0 has been released. It now uses the Python library
cryptography. Installing this requires additional system packages. This
commit adds in the appropriate packages required by cryptography based
on its documentation [1].
An alternative approach would have been to constrain the version of
Paramiko however the project describes the 1.x versions as relying on
insecure dependencies [2].
[1] https://cryptography.io/en/latest/installation/
[2] http://www.paramiko.org/installing.html
Change-Id: I6b7606be1293b2e9223de6a87b8a659d9678cc6d
This version of ansible is broken due to the following upstream
Ansible issue:
* https://github.com/ansible/ansible-modules-extras/issues/2042
Change-Id: I0ceabff24d8b6fb4d42425e074f4731b2214737d
Signed-off-by: Kevin Carter <kevin.carter@rackspace.com>
Latest release of ansible-lint 2.4.0 has broken
role linter tasks by introducing a dependency on
openstack-ansible-plugins for all linting
While we may choose to adapt the linter tox env
in the future, for now we want to return to previous
linter behavior.
Change-Id: I7be860d4a21cb6e59d69b586b4050376b254dfc0
This patch updates the tox.ini the same bashate exceptions as are
currently in the OpenStack-Ansible playbook repo.
It also ensures that the linters and all lint targets work
appropriately and normalises the tox.ini configuration to use
uniform formatting.
The use of ansible.cfg is removed as there is no way of being
certain which paths can be used without reverting to an ugly
sed hack in the commands. This is why it is preferred to make
use of environment variables which make use of tox's default
substitutions instead. It's a more reliable way of achieving
the goal for the purpose of gating and testing.
The switch to using a git clone instead of ansible-galaxy to
download the plugins is due to the path spec not being able to
work in Ansible 2.x. [1]
[1] https://github.com/ansible/ansible/issues/13563
Change-Id: I7574d35cca6c6691ba3daff9cb6f19f982f1591b
OpenStack-Infra has requested that lint tests be pipelined into the 'linters'
tox target in order to make more efficient use of nodepool resources.
This patch:
- Ensures that a complete set of lints tests is available in individual
tox targets.
- Adds a 'linters' target which executes all the other lints tests.
Change-Id: I46c7875699a753f131aa8121acd49d61f6e7c37f
This brings our tox.ini files inline with other OpenStack projects.
Change-Id: I898934560f7fa6d0904944d3cede5b5928fb857a
Depends-On: I376e51824c46f9b5eb4a4cff01aaa176632087dd
Signed-off-by: Paul Belanger <pabelanger@redhat.com>
Instead of launching two separate build jobs in our CI infrastructure,
one for bashate and one for pep8, launch a single one. While the jobs
are short, the setup of the images takes a long time, so this is
friendlier to our CI infrastructure.
Use the pep8 environment as common lint target and merge the bashate job
into it.
This patch also renamed dev-requirements to test-requirements to bring it
into line with all other OpenStack projects.
Change-Id: I5963dfe6a6972fa7db8e22a06f880f03024e69d9
This patch updates the run_tests convenience script to make it
execute all test environments using tox, but also ensures that
all the correct pre-requisites are in place before doing so.
Change-Id: I3014f2bf941eccd72b8c184cd0800ca1fd01dec5
This change updates a few things that were missed when the role
was cut over.
Change-Id: I95316576f3b128bce51b776a8ef3c2c4d995d1bc
Signed-off-by: Kevin Carter <kevin.carter@rackspace.com>
There are 2 ways to realize the privilege escalation
needed for the gate jobs.
1) Editing the playbooks (and hope to not forget
to write the sudo/become lines for every role)
2) Editing the inventory and set the variable there.
I'm taking the second approach with the minimum set
of variables (become_method is sudo by default and
become_user is root by default).
Change-Id: I3f7523ec25a1c35e4b22eb76ec32e33d6a359956
Signed-off-by: Kevin Carter <kevin.carter@rackspace.com>
The change moves the role out from the main repo py_from_git
repository and into its own standalone repository.
Items within this change:
* The role has been updated to ensure it runs standalone.
* Tests added to the role within tox.
* Functional tests added to the role that can either be run
via the run_tests.sh script or using tox.
* dev requirements have been updated for testing usecases.
* Docs added to both the README.rst file as well as the docs
folder.
Signed-off-by: Kevin Carter <kevin.carter@rackspace.com>