628c27ce9e
In kolla ansible we typically configure services to communicate via IP addresses rather than hostnames. One accidental exception to this was live migration, which used the hostname of the destination even when not required (i.e. TLS not being used for libvirt). To make such hostnames work, k-a adds entries to /etc/hosts in the bootstrap-servers command. Alternatively users may provide DNS. One problem with using /etc/hosts is that, if a new compute host is added to the cloud, or an IP address is changed, that will not be reflected in the /etc/hosts file of other hosts. This would cause live migration to the new host from an old host to fail, as the name cannot be resolved. The workaround for this was to update the /etc/hosts file (perhaps via bootstrap-servers) on all hosts after adding new compute hosts. Then the nova_libvirt container had to be restarted to pick up the change. Similarly, if user has overridden the migration_interface, the used hostname could point to a wrong address on which libvirt would not listen. This change adds the live_migration_inbound_addr option to nova.conf. If TLS is not in use for libvirt, this will be set to the IP address of the host on the migration network. If TLS is enabled for libvirt, live_migration_inbound_addr will be set to migration_hostname, since certificates will typically reference the hostname rather than the host's IP. With libvirt TLS enabled, DNS is recommended to avoid the /etc/hosts issue which is likely the case in production deployments. Change-Id: I0201b46a9fbab21433a9f53685131aeb461543a8 Closes-Bug: #1729566
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:
- Aodh
- Barbican
- Bifrost
- Blazar
- Ceilometer
- Cinder
- CloudKitty
- Congress
- Cyborg
- Designate
- Freezer
- Glance
- Heat
- Horizon
- Ironic
- Karbor
- Keystone
- Kuryr
- Magnum
- Manila
- Masakari
- Mistral
- Monasca
- Murano
- Neutron
- Nova
- Octavia
- Panko
- Qinling
- Rally
- Sahara
- Searchlight
- Senlin
- Solum
- Swift
- Tacker
- Tempest
- Trove
- Vitrage
- Vmtp
- Watcher
- Zun
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.
- MongoDB as a database back end for Panko.
- 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 Vagrantdoc- 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.