This will solve the following issue when running the
kolla-ansible cleanup command:

[WARNING]: Consider using file module with state=absent rather
than running rm

Closes-bug: #1586406
Change-Id: I366b6f27e697b24c6c54882c08afe4048803b4e8

Change-Id: If4be00b937e14ec93443dcb7249cf17099d57cbe
Closes-Bug: #1569417

At the moment the title of the index page of the developer documentation is
"Kolla’s Mission". Other projects use "Welcome to X’s developer documentation!".

Change-Id: Iadddc7fbe3d1eeafe5ed1926a3e090b5de70e7ee

Small sphinx syntax fixes, better wording, removed pronouns, and
anything else we can think of.

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

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

Remove information about build time on specific hardware and reasons
for not pushing images per commit that are not relevant for
a quickstart guide.

Link to detailed instruction about image building from the quickstart
guide and update the image building guide to use `kolla-build` command
by default instead of `tools/build.py`.

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

DocImpact

Change-Id: I3cdfbf84919de80f535c030bd146787ecda40dec
partial-Implements: blueprint ansible2

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

An operator may want to specify the location of custom config
files so that kolla can detect their location and merge
them with the default configs generated.

Partially implements: blueprint multi-project-config

Change-Id: Ibfb38d07a36dfa7fe25381adc34cc1d3cbe7d1e1

Give outside projects the ability to consume kolla-ansible as a
config generation mechanism by allowing for the developer to define
a directory structure within /etc/kolla that fits a project's needs.

For example, kolla-kubernetes does not define configuration in terms
of serivces, but in terms of pods (groups of services).

Partially implements: blueprint multi-project-config

Change-Id: If08443aefcaf5fa5604b243b39a6a2d54e431cff

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

partially implements blueprint multiple-clouds

Change-Id: I676c4245e6f058ffbed345970ee78d1750dd0f2f

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

Change-Id: Iacea37d84a57d1543f6332a8b600d431dc2c6270
Partial-Bug:#1569417