openstack/kolla-ansible
Code Issues Proposed changes
Ansible deployment of the Kolla containers
3,148 Commits 7 Branches 100 Tags 172 MiB
Jinja 45.9%
Python 40.4%
Shell 13.5%
Ruby 0.2%
34c2cb8e64
Go to file
Dave McCowan 34c2cb8e64 Implement Option for Two VIPs to separate API traffic 
To improve security, operators have asked for two VIPs for
their cloud.

VIP 1 is the internal VIP that can reach internal and admin endpoints.
In addition, the internal VIP can also reach other internal services,
such as the database and message services.
VIP 2 is the external VIP that can only reach public endpoints.

With one VIP only, all services are reached at the same address.

To add a second VIP, this patch adds two new configuration parameters.

kolla_external_vip_address: is an IPv4 address to use for created VIP
kolla_external_vip_interface: is the network interface to use for VIP
In this scenario, the first VIP (the internal VIP), is defined by
the original parameters (kolla_internal address and network_interface).

When using two VIPs, the existing kolla_external_address parameter
should be/point to/resolve to the kolla_external_vip_address.

Closes-bug: 1535333

Change-Id: I5bfcefaf7899298455cdade8209c34324aebfecb
2016-02-24 09:18:06 -05:00
ansible Implement Option for Two VIPs to separate API traffic 2016-02-24 09:18:06 -05:00
demos Extension .md is changed to .rst 2015-08-24 22:14:22 +05:30
dev Fix vagrant bootstrapping for ubuntu 2016-02-23 08:10:54 +01:00
doc Minor update add prechecks into workflow path 2016-02-22 11:36:39 -08:00
docker Merge "Pin Mesos to 0.27.1 version" 2016-02-23 17:34:37 +00:00
etc Implement Option for Two VIPs to separate API traffic 2016-02-24 09:18:06 -05:00
kolla Remove Rsyslog entirely 2016-02-23 01:45:23 -08:00
specs Merge "Logging with Heka spec" 2016-02-17 11:14:44 +00:00
tests Merge "Separate exclusion list for source and binary types" 2016-01-26 05:52:06 +00:00
tools Remove Rsyslog entirely 2016-02-23 01:45:23 -08:00
.gitignore Standardize bashate and add linters 2016-01-13 17:33:28 +00:00
.gitreview Update .gitreview for project rename 2015-09-11 20:57:54 +00:00
.testr.conf Merge "Revert "Capture the log in default"" 2016-01-19 15:36:52 +00:00
LICENSE Add ASL license 2014-09-20 17:29:35 -07:00
loc Fix up loc with change to devenv 2015-10-12 09:02:30 -07:00
README.rst Tidy up README.rst 2016-02-17 17:21:00 -07:00
requirements.txt Updated from global requirements 2016-02-17 19:19:46 +00:00
setup.cfg Remove unexisting data_files in setup.cfg 2016-02-02 17:46:17 +01:00
setup.py Updated from global requirements 2015-11-13 17:11:37 +00:00
test-requirements.txt Updated from global requirements 2016-01-19 13:48:15 +00:00
tox.ini Make pep8 *the* linting interface 2016-02-11 09:55:28 +00:00

README.rst

Kolla Overview

The Kolla project is a member of the OpenStack Big Tent Governance. Kolla's mission statement is:

Kolla provides production-ready containers and deployment tools for
operating OpenStack clouds.

Kolla provides Docker containers and Ansible playbooks to meet Kolla's mission. 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 by reading the documentation online docs.openstack.org.

Get started by reading the Developer Quickstart.

Kolla provides images to deploy the following OpenStack projects:

As well as these infrastructure components:

  • Ceph implementation for Cinder, Glance and Nova
  • Openvswitch and Linuxbridge backends for Neutron
  • MongoDB as a database backend for Ceilometer and Gnocchi
  • RabbitMQ as a messaging backend for communication between services.
  • HAProxy and Keepalived for high availability of services and their endpoints.
  • MariaDB and Galera for highly available MySQL databases

Docker Images

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 kollaglue namespace for every tagged release and implement an Ansible deployment for many but not all of them.

You can view the available images on Docker Hub or with the Docker CLI:

$ sudo docker search kollaglue

Directories

  • ansible - Contains Ansible playbooks to deploy Kolla in Docker containers.
  • demos - Contains a few demos to use with Kolla.
  • dev/heat - Contains an OpenStack-Heat based development environment.
  • dev/vagrant - Contains a vagrant VirtualBox/Libvirt based development environment.
  • 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.
  • docker - Contains jinja2 templates for the docker build system.
  • tools - Contains tools for interacting with Kolla.
  • specs - Contains the Kolla communities key arguments about architectural shifts in the code base.
  • tests - Contains functional testing tools.

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