473a5e0ca7
The admin-openrc.sh should copy to where the python-openstackclient was installed. whatever multinode and all-in-one, the place where python-openstackclient was installed is localhost, So admin-openrc.sh should copy to localhost. The purpose of "connection: local" in ansible playbook is that make sure this script can copy to localhost.In all-in-one, Writting as this is ok, it will copy to localhost, but in multinode, this will make a bug, add ansible_connection=ssh in inventory file the admin-openrc.sh will not copy to the localhost,the "connection:local" in post-deploy.yml will be covered by "ansible_connection=ssh" in inventory file, then the script will be copied to target node. So we should modify the hosts to localhost to avoid this bug. Change-Id: I054717cc2b4adc600808282034a10a58c1184a38 Closes-Bug: #1666808
Team and repository tags
Kolla-Ansible Overview
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 docs.openstack.org.
Get started by reading the Developer Quickstart.
OpenStack services
Kolla-Ansible deploys containers for the following OpenStack projects:
- Aodh
- Barbican
- Bifrost
- Ceilometer
- Cinder
- CloudKitty
- Congress
- Designate
- Freezer
- Glance
- Gnocchi
- Heat
- Horizon
- Ironic
- Karbor
- Keystone
- Kuryr
- Magnum
- Manila
- Mistral
- Murano
- Neutron
- Nova
- Octavia
- Panko
- Rally
- Sahara
- Searchlight
- Senlin
- Solum
- Swift
- Tacker
- Tempest
- Trove
- Vmtp
- Watcher
- Zaqar
- Zun
Infrastructure components
Kolla-Ansible deploys containers for the following infrastructure components:
- Ceph implementation for Cinder, Glance and Nova
- collectd, InfluxDB, and Grafana for performance monitoring.
- Elasticsearch and
-
Kibana to search, analyze, and visualize log messages.
- Fluentd <https://http://www.fluentd.org/>__ as an open source data collector for unified logging layer.
- HAProxy and Keepalived for high availability of services and their endpoints.
- Kafka A distributed streaming platform.
- MariaDB and Galera Cluster for highly available MySQL databases
- MongoDB as a database backend for Ceilometer and Gnocchi
- Open vSwitch and Linuxbridge backends for Neutron
- RabbitMQ as a messaging backend for communication between services.
Directories
ansible- Contains Ansible playbooks to deploy OpenStack services and infrastructure components in Docker containers.contrib- Contains demos scenarios for Heat and Murano 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.tests- Contains functional testing tools.tools- Contains tools for interacting with Kolla-Ansible.specs- Contains the Kolla-Ansible communities key arguments about architectural shifts in the code base.
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.