Change-Id: I324c250e57125910b64fad6c06a4d68acf0600b4

An initial specification of the internal TLS implementation for kolla,
describing https://etherpad.openstack.org/p/kolla-internal-tls and
https://blueprints.launchpad.net/kolla-ansible/+spec/add-ssl-internal-network

Change-Id: I5a42226b724affad2dc12390e345336f375c7a57

This ensures we have version-specific references to other projects [1].
Note that this doesn't mean the URLs are actually valid - we need to do
more work (linkcheck?) here, but it's an improvement nonetheless.

[1] https://docs.openstack.org/openstackdocstheme/latest/#external-link-helper

Change-Id: I118e4d211617c5df66ff04dc04e308a1d2fc67ad

1.Use opendev.org instead of git.openstack.org.
2.Use review.opendev.org instead of review.openstack.org.

You can see the discussion below:
http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003603.html

Change-Id: Ice4509204df788a1a44a06fb89fb44cfe6b54b94

Change-Id: Ib0ef21f23a8b54d43278454bbd6ed6bde419c5f0

Partially-Implements: blueprint cinder-quobyte-backend

Change-Id: I6de535ea4081fe0de52858ae582420617204e914

1. the pymysql is needed for the current release[0]
2. it should use keystone_database_address rather than
keystone_service_ip, because they may different.

[0]: https://github.com/openstack/kolla-ansible/blob/master/ansible/roles/keystone/templates/keystone.conf.j2#L22

Change-Id: I7eb90544bd6be167df157ca352ca01e21ce781bd

Describes the proposed approach to introduce Prometheus monitoring
for Kolla-Ansible deployment.

Partially-Implements: blueprint prometheus
Change-Id: I54616925abb76bda7efa2f2ae962d4e43f097551

Change-Id: Icc4a984e8defe4d068e7f4a78cd5483a0cb9c7b7

Change-Id: I2596ce2ccf45b5750798c03b8f3f7dfc859d457c

fix typo for specs/kubernetes-deployment.rst, tools/ovs-dpdkctl.sh, tools/setup_gate.sh

'managment' -> 'management'
'seperated' -> 'separated'
'occuring' -> 'occurring'
'discribed' -> 'described'
'recomended' -> 'recommended'
'thier' -> 'their'

Change-Id: Ie59c600698c965cebd9a541b951d704eda9301cb

Change-Id: I9d5e99d7412165f288fcd796ee588bfab1f76f4b

TrivialFix

Change-Id: Ifca64d8c4d6e7654d25001022e806f082acfa0b8

Github is just a mirror of the OpenStack git-repo.
Changed from Github to OpenStack git url wherever possible.

Change-Id: I7941ef86967de4efe7f23ff9fb11ec86c793901e

TrivialFix
Change-Id: I92cc2d826f2d418b9575e35dd048c98775c0be5c
Signed-off-by: Mohammed Salih Puthenpurayil <linusali@gmail.com>

related blueprint kolla-kubernetes

Change-Id: Ib1023787fca096d22a21c583c1ef647ccf925f00

We got rid of the kolla-mesos repo:
http://git.openstack.org/cgit/openstack/kolla-mesos/tree/README.rst

So we don't need things in the main kolla tree
related to Mesos/Marathon

Closes-Bug: #1577951
Change-Id: Iafae63914c8a6601dc1b5b04231af8a1d2cc8642

This reverts commit 99761c5c.

Change-Id: Ib40224841f3399c6794b8aa71ca5cd7f0308a722

related blueprint kolla-kubernetes
Co-Authored-By:  <mrostecki@mirantis.com>

Change-Id: I5ef968a0f9b4a1b47b32bb041fbc5d5a3c2e2be7

Change-Id: I454d3ff2226a51b6b98515c1b29f7d3d45351e4f

Change-Id: I27ca0ea75f3d6a4371c91b3cb2c7a999ec90fbc4

Trivial Fix

Change-Id: Ic14778bb4e894490a3b6af9471ba01ab4da94601

This adds a spec for using Heka as Kolla's log processing tool.

Change-Id: Ia786601f3f0b298c120950e2abdd6d1b71e32ba5

Co-Authored-By: Georgy Okrokvertskhov <gokrokvertskhov@mirantis.com>
related blueprint mesos
Change-Id: I0bc2d9e69819079b8cdaf9a47c5363a3017dced9

Change-Id: I50d4d66a507b06e75c9968cf0e0ee1ad9fd55c0a

Change-Id: Ie2f5a3b8e239cae13909cf70f8be44b05b19d431

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

Change-Id: Ia21736dd43a4fe63fbf4567c96dd53b452594677

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

Added cinder and metadata

Change-Id: I42feae68a387dd5a9de97837f785d2672c320419

Added keepalived to HA control container set

Change-Id: Ic209bc6ca55125a52d1974003104238bb9c4caa2

Added a container set for network operations

Change-Id: I625f0f03366b1d68f210a0bf92e58d5ceb6c568d

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