The variables blazar_developer_mode and blazar_venv_download
no longer carry any meaning. This review changes blazar to
do the equivalent of what developer_mode was all the time,
meaning that it always builds the venv and never requires
the repo server, but it will use a repo server when available.
As part of this, we move the source build out of its own file
because it's now a single task to include the venv build role.
This is just to make it easier to follow the code.
It looks like the project now needs authentication for the root
of the host so we'll test for that instead of 204.
Change-Id: Id1dc8d378cb57d6ab2b59da76468a4a0859466b1
The connection plugin no longer falls back on using the
inventory_hostname as the container_name. Set container_name as a host
var for each container in the test inventory.
Change-Id: Ic3975acc1d7fa608d67b3e2171b0d862fb2b28fd
The functional test check the responsiveness of the Blazar API. A
return of 204 code from the API verifies the success.
Rest of the changes ensure compliance with all the standards required
to make the linter and docs tests pass.
Change-Id: I640877817ad1ae312436932af87ad15094616f12
It would appear that blazar does not make use of rabbitmq,
so we remove the vhost/user setup and vars.
Change-Id: I3aa2a7e38fcd78212b4b88aa2b7bb28d598eaf7f
In order to reduce the packages required to pip install on to the hosts,
we allow the service setup to be delegated to a specific host, defaulting
to the deploy host. We also switch as many tasks as possible to using the
built-in Ansible modules which make use of the shade library.
The 'virtualenv' package is now installed appropriately by the openstack_hosts
role, so there's no need to install it any more. The 'httplib2' package is a
legacy Ansible requirement for the get_url/get_uri module which is no longer
needed. The keystone client library is not required any more now that we're
using the upstream modules. As there are no required packages left, the task
to install them is also removed.
With the dependent patches, the openstack_openrc role is now executed once
on the designated host, so it is no longer required as a meta-dependency for
the role.
Change-Id: Ib41f12b837f73ea534c6a0f926a70f7a82d7a194
Using tox for requirements management requires in-repo
requirements files for all our repositories. Rather than
do that, we make use of the tests repo to capture our
common requirements and use this to install them.
This reduces our review requirement rate and simplifies
maintenance for us for the tox config. It also makes it
usable with 'Depends-On', which is marvellous!
The tox requirements definitions for docs/releasenotes
builds are left in-place as those are standard entries
across the community. If that changes at some point, we
can re-assess those entries too.
Some old test cruft is also removed.
Depends-On: https://review.openstack.org/579208
Change-Id: Iee798c2660f69afe7c40cd3d2e9b801434944eff
There is no record for why we implement the database creation outside
of the role in the playbook, when we could do it inside the role.
Implementing it inside the role allows us to reduce the quantity of
group_vars duplicated from the role, and allows us to better document
the required variables in the role. The delegation can still be done
as it is done in the playbook too.
In this patch we implement a new variable called 'blazar_db_setup_host'
which is used in the role to allow delegation of the database setup
task to any host, but defaults to the first member of the galera_all
host group. We also document the variable blazar_galera_address which
has been used for a long time, but never documented. A bunch of unused
variables have also been removed.
Change-Id: Id500e2b2a5b981609becc883edd3d166f70103f4
This introduces the most basic jobs for blazar, and makes
sure blazar passes lint tests.
This reverts commit a5b35ebf11,
effectively re-enabling zuul jobs, and adapts the role
to our latest standards (The lint tests were failing, as
the passwords were logged while setting up Blazar server)
Functional testing starts with -nv only. However, in this
commit we added the necessary `rabbitmq_all` group to
the infra1 group, to help further functional testing.
Co-Authored-By: Taseer Ahmed <taseer94@gmail.com>
Change-Id: Ic2560b53aebf69e4784ce56db6929fe010e6b11e
Dmitriy Rabotyagov