Change-Id: I4f6f38b2a202b41a9dec839fa0222585b49fc06c
Partially-Implements: blueprint kolla-ansible-script

Change-Id: Idc0c118ed0153c549990166931bcdb6cf250abbb
Closes-Bug: #1480438

Change-Id: I14beadf8ae0b4f117623331dca71eff3d45b51f1
Closes-Bug: #1480439

This is not possible when running multihost ansible.
Essentially this should've been part of #1476293.

Change-Id: I53baccf5f89e71ce1313524815f928ea04908a05
Partitially-Implements: blueprint ansible-service

With Vagrant it becomes real easy to create a dev environment to
test and checkout $code. The focus is specifically on setting up
an environment to play around in, developing Kolla and showing
what it is capable of in a clean virtualised environment. When
done, the environment can be destroy and re-created at will when
needed.

Change-Id: I440d004e76c337f298cad2397cf4c13f2cc35ddb
Implements: blueprint vagrant-devenv

If user specifies registry a full image name is constructed by
concatenation of the registry, namespace and image. Currently
concatenation does not include '/' if registry is non-empty but
it should. If registry is empty '/' is not required.
This fix covers both use cases with help of Ansible filter.

Change-Id: I0588dd0da55d777e6caa7eb47d51b2435d38d5e0
Closes-Bug: #1479013

Closes-bug: #1480174

Change-Id: I1ef695e910405f41045ffa1c8a13afa1a443c39e

Change-Id: I0a68dc9024954942e2a94a5cd0a1d383a4887a39
Partially-implements: blueprint install-from-source

Change-Id: Id122002b946f803e4618488a553138942f624fa3
Partially-implements: blueprint install-from-source

Currently with the active development for blueprint [1]
the nova image cannot be build from source.
Need to revert back to master once the
nova master is stable with the changes in [1]

[1]https://blueprints.launchpad.net/nova/+spec/consolidate-libvirt-fs-volume-drivers

Change-Id: I85509608df1f096438357ff1e7e52d75622c9cff
Closes-Bug: #1480077

Known bugs/TODOs at this time of this patch update:

https://bugs.launchpad.net/kolla/+bug/1477990
https://bugs.launchpad.net/kolla/+bug/1477993



Implements: Blueprint swift-container
Closes-bug: #1477992
Co-Authored-By: Paul Bourke <paul.bourke@oracle.com>
Change-Id: I031f88a7cd1867104fef12df6ab3ffcc06cb65d6

Change-Id: Iaaa993ca0b37bb42a221caeab1b5319e1daca6f2
Partially-implements: blueprint install-from-source

Change-Id: I643b2add0bb10c8271972b804c27d5a61b7ba6f8
Partially-implements: blueprint install-from-source

Change-Id: Ibc7617a1d096918ced8534095ef8bdc8f79299db
Partially-implements: blueprint install-from-source

Cinder is unique in that interaction with the volumes
must occur in the container as opposed to from the host.
This doc will lay out a guide for Cinder and useful
debugging tips.

Change-Id: I5cdff42ba3a40c1a20a11570649ac42a1c3aa837

Do not use aufs to build images for Ubuntu systems

Change-Id: Ia14eaada3ec034a6ae340192dc69460df8885045

Additionally, make each service optional witha config option allowing
for extreme flexibility should the deployer want to replace a service
with a non-kolla one (the database for example).

Change-Id: I7b644da7cfa7e8e6b6878eb1b1aa97db830504ae
Closes-Bug: #1478509

The original purpose for having an abstract like 'database' rather than
the service name of 'mariadb' has been change. Our direction is different
and this patch reflects consistent naming throughout

Change-Id: I704896191cc5243f9dab2a4cca9120e9dc2ceb2c
Closes-Bug: #1478328