Snippets Groups Projects

"...kolla-ansible.git" did not exist on "f425c0678f9c90c019805edb0b233d89f61f7ca8"

Standardize use and construction of endpoint URLs

Rafael Weingärtner authored 4 years ago

The goal for this push request is to normalize the construction and use
of internal, external, and admin URLs. While extending Kolla-ansible
to enable a more flexible method to manage external URLs, we noticed
that the same URL was constructed multiple times in different parts
of the code. This can make it difficult for people that want to work
with these URLs and create inconsistencies in a large code base with
time. Therefore, we are proposing here the use of
"single Kolla-ansible variable" per endpoint URL, which facilitates
for people that are interested in overriding/extending these URLs.

As an example, we extended Kolla-ansible to facilitate the "override"
of public (external) URLs with the following standard
"<component/serviceName>.<companyBaseUrl>".
Therefore, the "NAT/redirect" in the SSL termination system (HAproxy,
HTTPD or some other) is done via the service name, and not by the port.
This allows operators to easily and automatically create more friendly
URL names. To develop this feature, we first applied this patch that
we are sending now to the community. We did that to reduce the surface
of changes in Kolla-ansible.

Another example is the integration of Kolla-ansible and Consul, which
we also implemented internally, and also requires URLs changes.
Therefore, this PR is essential to reduce code duplicity, and to
facility users/developers to work/customize the services URLs.

Change-Id: I73d483e01476e779a5155b2e18dd5ea25f514e93
Signed-off-by: Rafael Weingärtner <rafael@apache.org>

f425c067

f425c067 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.