Previously, a spec did not exist to define how Kolla will support
highly available OpenStack services.
Change-Id: I8fcc60f26d2cb98179be6b520c13abb22a372ecf
This specification outlines some of the design goals and practices to
be used to implement an Ansible multi-node deployment tool. The goals
of this work are simplicity, optimizing deployment time, and Operator
flexibility.
The long term objective is for Kolla to become the de-facto solution
for deploying OpenStack in containers.
Partially Implements: blueprint ansible-multi
Co-Authored-By: Sam Yaple <sam@yaple.net>
Change-Id: I8c5d8b7e69c4ed54624061428e2fbde6af6a1815
The EXPOSE options will create a local docker-proxy. This is
unnecessary with --net=host mode. The docker-proxy adds about
20 microseconds of latency. Add documentation to the specification
to indicate where to find the ports that are exposed by the
services in case someone were to desire to add EXPOSE back to
the Dockerfiles.
Change-Id: I398e922fe096d6022a2d5985bb92498f89a5ea31
Permit different levels of horizontal scalability for API vs engine or
conductor processes. Typically API may need different levels of scale
compared to the engine processes.
.
Change-Id: I2916fed7745bd9b0f67fda0abbb6d148315e5e00
The container spec file had a couple places were nested
lists were used which didn't have the necessary blank
lines before and after. As such, they didn not render
to HTML correctly.
Change-Id: I5d17644facdc25ec30db563c217367672529b8e1
This specification proposes using fig (being renamed to compose
soon) to provide single-node multi-container orchestration. By
using this mechanism, a very simple Ansible Playbook could easily
deploy a single node in to a specific role type - such as a controller
node, a compute node, or a storage node.
This specification further proposes using super-privileged containers
to provide solutions for the upgrade and rollback use cases of an
OpenStack deployment.
Change-Id: I56ff1fdf8b19b47be97778b55ea947ebb43995c1
Steven Dake