This file is included in the documentation so its
comments should serve as useful documentation for the reader.
Change-Id: I7403655ee8f39d576e8a3374ae593632ef5493e1
This patch adds a var used by the repo_build process to determine
which host group to check for members of before building the pip
packages required by this role. This provides the ability to
optimise the repo build process to only building the packages
that are required for an environment.
Depends-On: Idda16b4f382eee57c7469af898859d6d81d4eb30
Change-Id: Iedb4c0c91daa291f881a9fc00c5b8c40bb312ce3
The current method of installing the distribution packages required is
set in the tasks and cannot be changed by a deployer.
Currently the apt task always installs the latest package. This results
in unexpected binary changes when a deployer may simply be trying to
execute a configuration change.
This patch adds the ability for a deployer to change the desired state
so that the results are predictable.
Change-Id: I96f436aa64e65089af345d17af70291e30cc8cc6
All rabbitmq connection vars are now namespaced. Namespace support
was previously inconsistent which limited deployer override options.
Change-Id: I2593239e98aa3ebd578d030206299d4868d036ca
Implements: blueprint multi-rabbitmq-clusters
Remove all tasks and variables related to toggling between installation
of designate inside or outside of a Python virtual environment.
Installing within a venv is now the only supported deployment.
Additionally, a few changes have been made to make the creation of the
venv more resistant to interruptions during a run of the role.
* unarchiving a pre-built venv will now also occur when the venv
directory is created, not only after being downloaded
* virtualenv-tools is run against both pre-built and non pre-built venvs
to account for interruptions during or prior to unarchiving
Change-Id: If3f0cb96d0ac670f6c53243283d6726067cba011
Implements: blueprint only-install-venvs
Update documentation, default variables, tasks, and environment
inventory to include installation of the designate-zone-manager service.
Change-Id: I1a72cad13e88d962a1e38793a1a3b5b35c0ba8b7
* The default apt packages have been moved into a var file
that is only loaded when the detected OS is matched.
* The Install task file has had the apt specific tasks moved
into a named install task file.
Change-Id: I0b31d5d76d3aaedf3b87550165d0e670b314bebd
This patch implements a bunch of changes for easier debugging and to
make the deployment more functional.
- All passwords are removed from defaults. The role must fail to
complete all tasks if no password is provided.
- The Designate Pool Configuration uuid's are provided with
defaults and the vars are added to the user_secrets.yml file
for easy implementation in OpenStack-Ansible.
- The designate.conf template has been re-organised to closely
match the sample file provided in the master branch of the
OpenStack Designate repository. This makes it easier to compare
for changes.
- The PyMySQL driver is used for all MySQL connectivity, as is now
the general standard for OpenStack Services.
- The designate_pool_manager database is now setup.
- The test playbook has the RabbitMQ & DB setup pre_tasks removed
for now. These can move out again once functional testing is
working.
- The test playbook's LXC dhcp range is reduced to 50 hosts in
order to ensure no conflicts with the test containers and also
provide room for growth.
- Add human readable logging callback plugin to functional test.
- Restructure testing to make it easier to work with.
This patch adds the rootwrap templates, filters, etc in order to
ensure that the designate service is capable of executing commands
against bind9 when it needs to.
This patch removes unnecessary whitespace and converts Windows
CR's to Unix LF's.
It also makes a small change to the default description for
Designate in the Keystone service catalogue to ensure that it
is more consistent with other services in OpenStack-Ansible.
This patch implements:
- A fix to the keystone_authtoken section to ensure that the
correct URL is used to interact with the Keystone admin service.
- The updated messaging configuration due to the oslo_config
deprecation of 'notification_topics'.
- The updated keystone_authtoken configuration due to the
deprecation of 'auth_plugin'.
- A conditional to include the Ceilometer notification driver
only if the boolean 'designate_ceilometer_enabled' evaluates
to True.
This commit adds the ability to install glance without requiring an
OpenStack-Ansible pip wheel repository.
In 'developer mode' the git source is cloned directly and the services
are installed directly from the git clone with its requirements being
installed from pypi. The OpenStack upper-constraints file is also used
to ensure that the install is executed using the appropriately tested
set of pypi packages.
The following variables are added:
- designate_developer_mode: A boolean switch to enable/disable developer
mode.
- designate_git_repo: The git repository to clone Designate from.
- designate_git_install_branch: The branch, tag or SHA to checkout once
the designate repository has been cloned.
- designate_requirements_git_repo: The git repository to clone in order
to retrieve the upper-constraints file.
- designate_requirements_git_install_branch: The branch, tag or SHA to
checkout once the requirements repository has been cloned.
The testing playbook overrides the *_install_branch variables to fixed
SHA's in order to fix points in time at which updates are made. This
reduces the effect of upstream development changes on the
OpenStack-Ansible development cycle.