Snippets Groups Projects

"...kolla-ansible.git" did not exist on "56ae2db7ac694d7c651623aa7d2e23b3386bd2b2"

Performance: Run common role in a separate play

Mark Goddard authored 4 years ago

The common role was previously added as a dependency to all other roles.
It would set a fact after running on a host to avoid running twice. This
had the nice effect that deploying any service would automatically pull
in the common services for that host. When using tags, any services with
matching tags would also run the common role. This could be both
surprising and sometimes useful.

When using Ansible at large scale, there is a penalty associated with
executing a task against a large number of hosts, even if it is skipped.
The common role introduces some overhead, just in determining that it
has already run.

This change extracts the common role into a separate play, and removes
the dependency on it from all other roles. New groups have been added
for cron, fluentd, and kolla-toolbox, similar to other services. This
changes the behaviour in the following ways:

* The common role is now run for all hosts at the beginning, rather than
  prior to their first enabled service
* Hosts must be in the necessary group for each of the common services
  in order to have that service deployed. This is mostly to avoid
  deploying on localhost or the deployment host
* If tags are specified for another service e.g. nova, the common role
  will *not* automatically run for matching hosts. The common tag must
  be specified explicitly

The last of these is probably the largest behaviour change. While it
would be possible to determine which hosts should automatically run the
common role, it would be quite complex, and would introduce some
overhead that would probably negate the benefit of splitting out the
common role.

Partially-Implements: blueprint performance-improvements

Change-Id: I6a4676bf6efeebc61383ec7a406db07c7a868b2a

56ae2db7

56ae2db7 4 years ago

Name	Last commit	Last update
ansible
contrib
deploy-guide/source
doc
etc/kolla
kolla_ansible
releasenotes
roles
specs
tests
tools
zuul.d
.ansible-lint
.gitignore
.gitreview
.stestr.conf
.yamllint
CONTRIBUTING.rst
LICENSE
README.rst
bindep.txt
lower-constraints.txt
requirements.txt
setup.cfg
setup.py
test-requirements.txt
tox.ini

Kolla-Ansible

The Kolla-Ansible is a deliverable project separated from Kolla project.

Kolla-Ansible deploys OpenStack services and infrastructure components in Docker containers.

Kolla's mission statement is:

To provide production-ready containers and deployment tools for operating
OpenStack clouds.

Kolla is highly opinionated out of the box, but allows for complete customization. This permits operators with little experience to deploy OpenStack quickly and as experience grows modify the OpenStack configuration to suit the operator's exact requirements.

Getting Started

Learn about Kolla-Ansible by reading the documentation online Kolla-Ansible.

Get started by reading the Developer Quickstart.

OpenStack services

Kolla-Ansible deploys containers for the following OpenStack projects:

Infrastructure components

Kolla-Ansible deploys containers for the following infrastructure components:

Collectd, Telegraf, InfluxDB, Prometheus, and Grafana for performance monitoring.
Elasticsearch and Kibana to search, analyze, and visualize log messages.
Etcd a distributed reliable key-value store.
Fluentd as an open source data collector for unified logging layer.
Gnocchi A time-series storage database.
HAProxy and Keepalived for high availability of services and their endpoints.
MariaDB and Galera Cluster for highly available MySQL databases.
Memcached a distributed memory object caching system.
Open vSwitch and Linuxbridge backends for Neutron.
RabbitMQ as a messaging backend for communication between services.
Redis an in-memory data structure store.
Zookeeper an open-source server which enables highly reliable distributed coordination.

Directories

ansible - Contains Ansible playbooks to deploy OpenStack services and infrastructure components in Docker containers.
contrib - Contains demos scenarios for Heat, Magnum and Tacker and a development environment for Vagrant
doc - Contains documentation.
etc - Contains a reference etc directory structure which requires configuration of a small number of configuration variables to achieve a working All-in-One (AIO) deployment.
kolla_ansible - Contains password generation script.
releasenotes - Contains releasenote of all features added in Kolla-Ansible.
specs - Contains the Kolla-Ansible communities key arguments about architectural shifts in the code base.
tests - Contains functional testing tools.
tools - Contains tools for interacting with Kolla-Ansible.
zuul.d - Contains project gate job definitions.

Getting Involved

Need a feature? Find a bug? Let us know! Contributions are much appreciated and should follow the standard Gerrit workflow.

We communicate using the #openstack-kolla irc channel.
File bugs, blueprints, track releases, etc on Launchpad.
Attend weekly meetings.
Contribute code.

Contributors

Check out who's contributing code and contributing reviews.

Notices

Docker and the Docker logo are trademarks or registered trademarks of Docker, Inc. in the United States and/or other countries. Docker, Inc. and other parties may also have trademark rights in other terms used herein.