TrivialFix

Change-Id: I7ccbecddc55b26d252b92faccec94676315c3eec

Change-Id: I81413ffcaa4efb881d13fef62823d60b676e871d
Implements: blueprint docker-named-volumes

Steve is tired of maintaining a copr for Magnum.  People bug him
all the time to update the rpm for RDO.  The RDO community
has offered to take on the maintainance of the Magnum RPM. As this
RPM won't be in current-passed-ci for some time so it needs
to be pulled from current repo for the foreseeable future,
possibly nearing the release of Mitaka.

Change-Id: I9cfb02ab828251ef5bf40ca236f18b5f0f715e34
Closes-Bug: #1539325

Add bootstrap label to all bootstrap containers to ensure that when
the a new container is launched a difference is seen between it and
the bootstrap container since we cannot rely on ENV variables for
this. This only affects mariadb at this stage, but it is needed to
ensure rabbitmq works when we switch to named volumes.

Change-Id: Ia022af26212d2e5445c06149848831037a508407
Closes-Bug: #1538136

With the switch to named volumes we run into a few situations where
we cannot bootstrap volumes like we used to. This labels param will
fix that as the next patchset shows.

Change-Id: Ia93166dd204c5c0d1a0eb9ffeb6d0aba486e269a
Partially-Implements: blueprint docker-named-volumes

There is no reason to have a hostname-unique pidfile in the container
as we currently have. This posed problems with kolla-mesos reusing
the same script. Since there is no reason for this pidfile to be
configurable in path _at_ _all_, we hardcode the path.

Additionally, we adjust the file perm change to only update the perms
on the folder if it is not already properly set.

This also incorperates a kolla-ansible file in the bootstrap process
which follows our other container techniques of using the idempotent
creation of a volume in the bootstrap process (see nova)

TrivialFix
Related-Bug: #1538136
Change-Id: I2380529fc7146a9603145cdc31e649cb8841f7dd

Change-Id: Ie7a53396b03ce4e472b5e810a02ccdfc9bd8aacd
Partially-Implements: blueprint enable-manila-containers

Since the fetch script fetched _all_ keyrings from the ceph-mon
container, the ceph-mon container must contain all keyrings. This
setup works AIO but was broken on multinode because the ceph-mon
container did not have the radosgw keyring. This issue affects every
multinode install regardless of using the radosgw or not.

TrivialFix

Change-Id: Ie416de1a5275862da6d77ef0dd174e85e499fc0f

Change-Id: I3cfb239e6f99e7079b2781b06550fa627fcb8998
Closes-Bug: #1539064

Swift updates and new deps are needed, here is one

Closes-Bug: #1538377
Change-Id: Ibb890c73e462113c5aa29ab12637a9115bb51240

$(hostname) is Ceph Monitor name in extend_start.sh,
{{ ansibe_hostanme }} is Ceph Monitor name in ceph.conf.
$(hostname) not always equal to ansible_hostname , that
makes ceph_mon container can't start.

Closes-Bug: #1538870
Change-Id: I312bf8d74c855aa4c72f12285e3092df96f60048

Currently the only consumer of ansible find_disks module is Ceph. And
Ceph OSD deployment in kolla uses GPT partition label to detect and
identify disks for Ceph OSD use. This is not always true for all the
deployment.

The change here extended the find_disks module by:
- adding `name` argument to find disk by either partition name or
  filesystem label matching
- `partition_name` argument now becomes an alias to `name`
- adding `match_mode` argument to allow prefix matching. It is used for
  swift disk detection.
- return `fs_label` key / value in result for disk mounting purpose

Change-Id: I9c93400c1826f5148acf09e9fbe555e358dfdfcc
Partially-Implements: blueprint swift-physical-disk

We use tcp connection rather than socket so we can remove the config
options related to it.

Additionally adjust the _extremely_ verbose logging from INFO to
WARNING.

TrivialFix
Change-Id: I88bf660134192f11732d012985df5c4f688419ba

After introduction of pull action and turing every main.yml into
{{action}}.yml we lost ability to perform upgrade.

Change-Id: Id6b5921bd1e3e7b196c4b3223920e51ae5e0b840
Closes-Bug: #1538210

Change-Id: I2b59e7606e3ab4e09e1cc7d56494b1e0ab2da29f

The local_settings file affect django-compress behavior, so
re-generate the compressed javascript and css if it is changed

Closes-Bug: #1537815
Change-Id: I330bfb666e39ffb88a4488793562df697d5572d0

The passed keyfile path is used to decrypt the passwords.yml
which encrypted by the ansible vault.

Partially-Implements: blueprint	encrypt-sensitive-info
DocImpact
Change-Id: Ifaebf464478cde99e896c13b375cfaf9282ee576

And use variables for options.

TrivialFix

Change-Id: I6cf8612b4e15ef263d2f5b2dbacc186ccd16871b

Update Swift config playbook to use correct name of Swift ring
builer file. Those are the names generated if one follows document in
doc/swift-guide.rst

TrivialFix

Change-Id: If1d713e3cccc851ef6f2cc3cb5a736b43fa26957

After introduction of pull action and turing every main.yml into
{{action}}.yml we lost ability to perform upgrade

Change-Id: Ie9fa2cd083b061033abc733fba53d54f9c55e393
Fixes-Bug: #1538210

Part of ELK stack. Includes Dockerfiles for both Centos and Ubuntu.

Change-Id: I1d955a5c51e416cc572eb2c9b4c57982a1d6ab67
Partially-implements: blueprint central-logging-service