63e5e4d658
When user starts Kolla on system without Docker daemon running huge traceback is generated and then exit. Issue is because KollaWorker raises exception but no one catches it (then only call to it is in run_build() which assumes everything is ok). Change-Id: I68ea3f48c75b51dbbab3accbc531d2f73428c48f |
||
|---|---|---|
| .zuul.d | ||
| contrib/template-override | ||
| doc | ||
| docker | ||
| etc | ||
| kolla | ||
| releasenotes | ||
| roles | ||
| specs | ||
| tests | ||
| tools | ||
| .gitignore | ||
| .gitreview | ||
| .testr.conf | ||
| .yamllint | ||
| bindep.txt | ||
| deliverables.yaml | ||
| HACKING.rst | ||
| LICENSE | ||
| lower-constraints.txt | ||
| README.rst | ||
| requirements.txt | ||
| setup.cfg | ||
| setup.py | ||
| test-requirements.txt | ||
| tox.ini | ||
Team and repository tags
Kolla Overview
The Kolla project is a member of the OpenStack Big Tent Governance.
Kolla's mission statement is:
To provide production-ready containers and deployment tools for operating
OpenStack clouds.Kolla provides Docker containers, Ansible playbooks to deploy OpenStack on baremetal or virtual machine to meet Kolla's mission.
Kolla has out of the box defaults for a working basic deployment, and also implements complete customization. This model permits operators with minimal experience to deploy OpenStack quickly and as the operator's experience grows modify the OpenStack configuration to suit the operator's exact requirements.
Getting Started
Learn about Kolla by reading the documentation online Kolla.
Get started by reading the Kolla Ansible Developer Quickstart.
The Kolla Repository
The Kolla repository is one of three deliverables of the OpenStack Kolla project. The three deliverables that make up the Kolla project are:
| Deliverable | Repository |
|---|---|
| kolla | https://git.openstack.org/cgit/openstack/kolla |
| kolla-ansible | https://git.openstack.org/cgit/openstack/kolla-ansible |
| kolla-cli | https://git.openstack.org/cgit/openstack/kolla-cli |
The Docker images are built by the Kolla project maintainers. A detailed process for contributing to the images can be found in the image building guide.
The Kolla developers build images in the kolla namespace for every tagged release.
You can view the available images on Docker Hub or with the Docker CLI:
$ sudo docker search kollaOpenStack services
Kolla provides images to deploy the following OpenStack projects:
- Almanach
- Aodh
- Barbican
- Bifrost
- Blazar
- Ceilometer
- Cinder
- CloudKitty
- Congress
- Designate
- Dragonflow
- EC2-API
- Freezer
- Glance
- Heat
- Horizon
- Ironic
- Karbor
- Keystone
- Kuryr
- Magnum
- Manila
- Mistral
- Monasca
- Murano
- Neutron
- Nova
- Octavia
- Panko
- Rally
- Sahara
- Searchlight
- Senlin
- Solum
- Swift
- Tacker
- Tempest
- Trove
- Vitrage
- Vmtp
- Watcher
- Zaqar
- Zun
Infrastructure components
Kolla provides images to deploy the following infrastructure components:
- Ceph implementation for Cinder, Glance and Nova
- Certmonger a service to simplify interaction with CAs on networks which use PKI.
- Chrony a versatile implementation of the Network Time Protocol (NTP).
- Collectd, InfluxDB, and Grafana for performance monitoring.
- Elasticsearch and Kibana to search, analyze, and visualize log messages.
- Cron for log rotation.
- Etcd a distributed key value store that provides a reliable way to store data across a cluster of machines.
- 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.
- Kafka a distributed streaming platform.
- 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 back ends for Neutron.
- Linux ptp an implementation of the Precision Time Protocol (PTP) according to IEEE standard 1588 for Linux.
- Percona XtraBackup A tool which provides a method of performing a hot backup of your MySQL data while the system is running.
- Prometheus an open-source systems monitoring and alerting toolkit originally built at SoundCloud.
- Qdrouterd as a direct messaging back end for communication between services.
- RabbitMQ as a broker messaging back end for communication between services.
- Redis Sentinel provides high availability for redis along with collateral tasks such as monitoring, notification and acts as configuration provider for clients.
- Sensu workflow automation for monitoring.
- Telegraf as a plugin-driven server agent for collecting & reporting metrics.
- ZooKeeper as a centralized service for maintaining configuration information, naming, providing distributed synchronization, and providing group services.
Directories
contrib- Contains sample template override files.doc- Contains documentation.docker- Contains jinja2 templates for the Docker build system.etc- Contains a reference etc directory structure which requires configuration of a small number of configuration variables to build docker images.tests- Contains functional testing tools.tools- Contains tools for interacting with the kolla repository.specs- Contains the Kolla 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 is 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.