All the images follow the same naming schema where the container
name is part of the ansible variable name.  Currently, the
kolla_toolbox container is named ansible_image_full.  Change
this to match what the container name is.

Could impact operators who are specifying ansible_image_full
in globals.yml.

TrivialFix

Change-Id: I9f0cbe4bd69ce17489310a1f5734a254e6ebe27b

Change-Id: Iec777d9218f871908386704697e840a3c88821c9

Change-Id: Ic5d4a3dbd5efcd1337bafae0e2b0bf67d90cd1e5
Closes-Bug: #1574008

Closes-Bug: #1580884
Change-Id: Ief5917d48dbf6abe4a5861e73b24d534b889bd52

this is a wordround fix for the rabbitmq failed when deploy on CentOS in
the CI gate. the ideal fix should set the hostname in setup_gate.sh
script. But it do not work as expect with unknown reason

Partial-Bug: #1581301
Change-Id: Ia692794aadf11d3ebe75e4e2bf6b42d9a5f3996f

Change-Id: I19642054ca18d447ef154fee3338c29d472ea87a

In order for the ansible configuration to be consumable,
we need to be able to generate it without deploying anything.

Change-Id: I2bbdd74d62d00f509a4fa5e4100906ed658d3974
Implements: blueprint generate-config

Kolla should have a doc with an overview of security within
the project.

Partially implements: blueprint documentation-rework

Change-Id: I0a8b902fe1b9adf6617779646bf0bbaee1a36c4f

* sudo is not needed as script already runs as root, using sudo would
  require http_* env vars to be carried through.

* Add a systemd unit file to configure docker proxy support

* Update /etc/bashrc if available proxy

TrivialFix

Change-Id: If2571389ec3dc5bce9e819acf962d202b3166b97

Files affected:
- ansible/roles/ceph/tasks/bootstrap_mons.yml
- ansible/roles/neutron/tasks/deploy.yml
- ansible/roles/neutron/tasks/start.yml

TrivialFix
Change-Id: Ic4b624cfe0ae4d73b49e616319e9db2229931249

Change-Id: Ib017711de749d72f277b614b735fd2d63cbe5c3a

* enable the openstack logging debug in the gate
* copy the /etc/kolla files out
* copy the /var/log files out

TrivialFix

Change-Id: I9cf5fa773ec5f41c6ea93325076a64dd24ce22da

Since Mitaka, Neutron does the right job to calculate and advertise
correct MTU to instances, out of the box [1].

[1] https://review.openstack.org/#/c/302165/

TrivialFix
Change-Id: I71a6dc5b56c2c1fb9db757df77a56feababdc039

Trivial-Fix

Change-Id: I0d9f0e0f661c2dfe350c38485436288f9c1a4a3c

Because of the consideration of security and performance, ceph community
recommend the use of two separate network public networks and cluster
networks. refer:
http://docs.ceph.com/docs/master/rados/configuration/network-config-ref/

DocImpact
Closes-Bug: #1582095
Change-Id: I8cb0e14f86c859820fbbb8af8f94ac8155338e13

partially-implements: blueprint documentation-rework
Change-Id: I1b10f0bf0b40182bacbc8e8b6ee085cd338de6fa

Restructured the documenation to

1. Add reference at the top
2. Updated the title formatting
3. Updated the heading formatting
4. Updated the links formatting

Change-Id: Ie3786e92fee674da1fa39cf07f1bf0a3badd5b92

centos-release-openstack-mitaka 1.3 is now available via the
delorean-mitaka-testing repo. We need to install this directly instead
of the 1.2 version as otherwise the subsequent 'yum update' tries to
install it and fails on the centos-release dependency which is
incompatible with the oraclelinux base.

Closes-Bug: 1576238

Change-Id: I51cb372424b27b32e95f9e81c5dddbe8e49a6131

CentOS shipped with an older version of docker-py named docker-python before.
But currently CentOS also shipped with a new rpm named python-docker-py-1.7.2
which obsoletes docker-python and also fulfill kolla need according to its
version(kolla needs docker-py >= 1.6.0).

Change-Id: I684a6a4e6b6baa9589e9b2afd3cfcc195d2a5e21
Signed-off-by: Zhijiang Hu <hu.zhijiang@zte.com.cn>

Our quickstart guide is way too complex.  We need to simplify
the quickstart guide by pulling out the overwhelming amount of
information and splitting it into other docs.

Change-Id: Iec175ee7f60bfd11ce06b22c861e51e180c188a9
Partially-implements: blueprint documentation-rework

Change-Id: Ib41fc2453cd85fa4937218b37cf80db82f63b20c

Trying to use ConfigMap's in Kubernetes leads to an interesting
problem. We use the file name as the key and the contents of the
file as the text value. The ConfigMap is mounted on the container
as a volume and the key is then used as the name of the file. The
problem is that kubernetes has a limitation on the name of the
key

https://github.com/kubernetes/kubernetes/blob/release-1.2/docs/design/identifiers.md

Which means we cannot use '_' in the name of the file.

Closes-Bug: #1581162
Change-Id: I2d9ec80f989c30893b019954fe18b3623d27a076