In order to radically simplify how we prepare the service
venvs, we use a common role to do the wheel builds and the
venv preparation. This makes the process far simpler to
understand, because the role does its own building and
installing. It also reduces the code maintenance burden,
because instead of duplicating the build processes in the
repo_build role and the service role - we only have it all
done in a single place.
We also change the role venv tag var to use the integrated
build's common venv tag so that we can remove the role's
venv tag in group_vars in the integrated build. This reduces
memory consumption and also reduces the duplication.
This is by no means the final stop in the simplification
process, but it is a step forward. The will be work to follow
which:
1. Replaces 'developer mode' with an equivalent mechanism
that uses the common role and is simpler to understand.
We will also simplify the provisioning of pip install
arguments when doing this.
Depends-On: https://review.openstack.org/598957
Change-Id: I97a614422490e7bff3bbe5f651387fbeb092aeda
Implements: blueprint python-build-install-simplification
Signed-off-by: Jesse Pretorius <jesse.pretorius@rackspace.co.uk>
Import the initial verison of the os_searchlight role.
This role currently does the following:
- Installs a jdk, elasticsearch and searchlight
- Starts the searchlight services (api and listener)
- Does an initial DB sync
- Listens for messages from other openstack services
- installs the openstack CLI plugin
Current issues / TODO list:
- linting of Stouts.elasticsearch role
- Setup Apache site properly.
Change-Id: I3ff72c9fbfc96a1f80f5cdd51a91f4d7ef638682
Guilherme Steinmüller