openstack/openstack-ansible-rabbitmq_server - openstack-ansible-rabbitmq_server - OpenDev: Free Software Needs Free Tools

Now that run_tests.sh handles the tests repo clone, we can
remove the use of the older tests-repo-clone.sh script.
Change-Id: I04b2c0614b3a328b8d805f64f8ed517435bf0ddc

Change-Id: I91bf99fde3f4d6c43024fbf482c443bb32b4d60b

In order to allow the use of the environment variable which informs
Ansible which user executed the playbook, we pass the USER env var
into the environment that tox builds.
Change-Id: I426e3356583a8f9d394e3e7721c8a502a7fe4adb
Implements: blueprint python-build-install-simplification
Signed-off-by: Jesse Pretorius <jesse.pretorius@rackspace.co.uk>

Change-Id: Ic90a9e0149698deda8133c4b8a5c78aa52bcc0de

Change-Id: I0c86095815d5c5d0fc8a9aa66d5682b5a4a5f4de

Change-Id: I4723a34aa0392e7a1f204a28963e610d5558e8c0

For compliance with the Project Testing Interface as described in:
https://governance.openstack.org/tc/reference/project-testing-interface.html
For more detials information, please refer to:
http://lists.openstack.org/pipermail/openstack-dev/2017-December/125710.html
Change-Id: Ide1ffe82a4b49c700a91e271163f73816e08542f

In https://review.openstack.org/547015 we adjusted
the apt installation process to ensure that the cache
update happens after the repository changes, but left
out the explicit instruction not to do it in the task
which changes the repo config.
This patch adds that, but also seperates out the cache
update into its own task so that the package install
task remains more readable.
Partial-Bug: #1750656
Change-Id: Id70ad28caa63267c2bb17d8c56a8fa6e00cf55d4

If apt_repository fails to update the apt cache after updating the
configuration, retries don't register there was a change and so no
attempt is made to update the cache by the module on the second attempt.
This failure can result in a failure to install packages.
This change adds an apt module task to update the cache if the
apt_repository task registers a change. This means updating the cache
will get retried on failure and no longer fail silently.
Change-Id: Id059dbec3466cb1ef3ea567249f52384a8ade515
Partial-Bug: #1750656 

All operating systems supported by the role use systemd and these
conditional checks are no longer needed.
Change-Id: Iffa9a7ed561e5d460a51f7492dde19ad9a8ed59c

Change-Id: Id9137bdedea4b0d7c964d438a223deb6a783e421

Change-Id: Ia9c4eb9657246e6669310b45cd735390e2f7b285

Change-Id: I957251be9dce419a6db8a272986fc5d12bfe3e9b

The meta-play test-setup-host.yml already includes
test-prepare-containers.yml so there's no need to
re-run it.
Change-Id: I91b63aeebc4afe67be160245eb8872c16c2da2ad

The current functional test does a full upgrade process,
but uses the same current role for both the previous
version and the new version.
Ideally we want to test the initial deploy using the
previous series' role, so that we're actually testing
a series upgrade, not just a rabbitmq upgrade.
This patch separates the upgrade test out and makes the
default test just be a deployment. This allows us to
more clearly see where something breaks.
Depends-On: https://review.openstack.org/543245
Change-Id: I43e1e224cd4237ac37b40fde5ce7c279331a012d

Currently a new node joining the cluster is done by using
a try/rescue operation which always fails for a new node,
causing a lot of confusion due to the failed task report.
This patch ensures that the implementation no longer does
that.
In order to prevent lint check failures, each join task
has a 'changed_when: true' added.
Change-Id: Ic1da9f3ad1016831fe37643165880e7ff98ca923

Zuul no longer requires the project-name for in-repo configuration.
Omitting it makes forking or renaming projects easier.
Change-Id: I8158b7bf6fe5321ec97f2cffedb47f6500641250

This patch changes the use of systemctl via the command module
over to the Ansible systemd module.
One conditional check for systemd was removed since all supported
distributions deployed by OSA have systemd.
Change-Id: I926e94d185f4999e13b33f7d035b9dd5cf732f0b

Change-Id: Ia5449927738b8f85cc71c084119b238a38208890

Change-Id: Icf2c47483c029f8fe8ff22fc46b4ef2815656378

Change-Id: Idd3a8e5688e6c30688a66b8091b0c71c1e548c09

These issues can show up when we'll bump ansible lint to a more
recent version.
Change-Id: Ieaabe67aead19fcc97c118970467602df1a6e0fa

This would allow someone to test its change with an AIO.
Change-Id: Ia16a08d8575995a8b063f1f2010dbf0f0ac4bdf4

Change-Id: I082b3aaf5ff2404b99984a8ab1ab334720d404c2

With addition of pip_install on every node, we don't
need to have pip_install as a meta dependency.
Depends-On: If3412bb888ebb854874bbc43eb76bfcb3e4a7868
Depends-On: I79ff70c438b44753be2a93f004ebbc46de0a963d
Change-Id: I49847c9fe01c0d4fdf420dbc31985edc08650f2c

Change-Id: I36e140347a60d57e65c803248260af23c7d19df1

Currently a new cluster is created by using a try/rescue
operation which always fails for a new cluster, causing
a lot of confusion due to the failed task report.
This patch implements an improvement which tests the
cluster state and creates a new one if it is not ready
without requiring the task to fail.
As the cluster creation is a single task, it's merged
into the rabbitmq_cluster.yml task file.
As the tags are all the same, the tag is set in the
main task file instead of individually on all the tasks.
Change-Id: Iaa8e429cbd1c539d8242453c0490373c758dd9fe

Currently the checking of the cookie content uses
a try/rescue block and for a new install always
results in a failed task. This causes a lot of
confusion due to the failed task report.
This patch improves the process by executing the
stop/start if the cookie file is changed in any
way by the copy task. This is far simpler and
results in no task fails.
As all the tasks related to this were marked
rabbitmq-config the tag implementation is set
in the main tasks file and removed from all the
individual tasks.
Change-Id: Iba959f730f2453bf9a295158749b96ed3a966ef4

With the merge of https://review.openstack.org/520177 in the
tests repo some ansible-lint failures which previously were
not being picked up are now detected.
Change-Id: I8b72bf83996451166fca5b20990c549fc0129306

Release notes are version independent, so remove version/release
values. We've found that projects now require the service package
to be installed in order to build release notes, and this is entirely
due to the current convention of pulling in the version information.
Release notes should not need installation in order to build, so this
unnecessary version setting needs to be removed.
This is needed for new release notes publishing, see
I56909152975f731a9d2c21b2825b972195e48ee8 and the discussion starting
at
http://lists.openstack.org/pipermail/openstack-dev/2017-November/124480.html
.
Change-Id: I467712d9122270788f19d2fc8aa9481b1379bcf0

Change-Id: I34ccb3afa7b32971457318f511ba3f52e25b087f

Initially the intent for adding this was to better test
any patches for roles together before they merge, but it
has had the unintended side-effect of causing patches to
take much longer to merge (because they all get lined up
in a single queue, rather than independent queues) and
a lot more infra resources are used (because a patch
that fails at the top of the queue will result in all
subsequent patches restarting all their tests).
As discussed in the channel, we'd prefer to revert back
to the previous independent queue method of testing. It
has served us well.
Change-Id: I97d4ff7a61dc2c1fd9b8a8455f290d47161cf07a

Currently the linters test is in the project-config
repository, but those are meant to be used for standard
jobs which do not require any repository other than the
one given. Our lint tests use the 'openstack-ansible-tests'
repository, so we should rather use our own job definition.
Change-Id: Id4e64c4f57530bfcd8900dd562845f07761a2d43
Depends-On: I0391ec310c4eede436011a48490e3c524c8ddf4d

This patch implements an initial set of jobs intended to match
the current job execution method. It does not intend to improve
how the jobs are executed - only to replicate what is currently
in openstack-infra/openstack-zuul-jobs and provide the platform
to iterate on.
Change-Id: I7a1c312268b7219cb3e04058e9563a2fe0c469f0

Change-Id: Iae23dfc74bba6a5df9dd5d51d7f08aaa6cadc940

We need to add openstack ansible information in the role
metadata to be able to track role maturity. With it,
we can create a role maturity table and take decisions about
role deprecations.
Change-Id: If60e1fd819709b35e4481f05e3735ccc3c8986de

Use https instead of http for docs links
Change-Id: I37a504d941b54e947f81f2194d18313479f71a00