The python-nova package now pulls the required dependency on
python-oslo-policy:

https://github.com/openstack-packages/nova/blob/036149e93fc41649d1e827e163180e7d9e6cbec5/openstack-nova.spec#L389

TrivialFix

Change-Id: I472f600710cb743ef6ede01e722a79b1451cf295

The python-neutron package now pulls the required dependency on
python-oslo-reports:

https://github.com/openstack-packages/neutron/blob/774036f7f99cd54bdd1c94f70d28bfe15f47af83/openstack-neutron.spec#L125

TrivialFix

Change-Id: I6cb4d0d9601c910cf631dddcf715a7f4fc9754e3

Sometimes the keyserver has a mirror failure which results in a failed
gate. Add a retry to help prevent that failure.

TrivialFix

Change-Id: I143626dd6d799b4ea0f82f6649d2155c2f45a115

*** Requires Docker 1.10 which is released ***

Documentation will be in the next patch. You must set the following
in your docker.service daemon control file for propogation to work:

    [Service]
    MountFlags=shared

======================================================================

Thanks to mount propagation in Docker 1.10 we can use thin containers
finally! This is extremely useful to operators since now they can
access the network namespaces from the hosts (outside the neutron
container). But additionally it allows us to implement the VPN agent
and other services easier.

Neutron containers and the neutron role are brought into the standards
of the new Kolla. Completely with drop-root and ansible formating
updates.

The ip_wrapper.py script was (thankfully) not needed so it has been
removed from the repo.

Partially-Implements: blueprint upgrade-neutron
Change-Id: Iaf5555283240457e1912459f397a6393d886fba1

Because we use rootwrap in a venv we need to update the exec_dirs.
Without doing this *some* commands will break for various reasons that
I won't get into in this review in detail. But this is required for
neutron-l3-agent in a container + drop-root.

Change-Id: I1a09f7188fdd501b7ce251d9f2fb0e5b10222142
Partially-Implements: blueprint drop-root

Docker 1.10 has broken the gate and this patch will correct that
breakage.

The issue comes with rsyslog. Due to a commit in Docker 1.10 [1] we
must change the way we get the log socket for rsyslog. The /dev/
folder will no longer populate as we used it. So instead we simply
make a new socket in a path we control and share that to the correct
location in the containers.

Additionally, adjust the gate for new Docker daemon.

[1] https://github.com/docker/docker/pull/16639
Partially-Implements: blueprint kolla-upgrade
Change-Id: I881a2ecdf6d7b35991e1d38a3f3e60d022d6577f

Two patches merged that did not have teh correct name for
kolla_toolbox

TrivialFix

Change-Id: I09e230e29cff496247c32bf227715bfb7caa0a95

Remove the '..' in the path like:
/home/jenkins/workspace/gate-kolla-dsvm-deploy-centos-binary/tools/../ansible/inventory/all-in-one

TrivialFix

Change-Id: I80724a9e876ed1826c65e08b55cfa08124d70eb9

Ubuntu-bootstrap.sh script rebooted my server
with message of re-run the script and at re-run
it again do the same thing.

I find this behavior is due to the below check

if [[ $(uname -r) != *"3.19"* ]]

As latest ubuntu kernel version is 4.2.0-27-generic,
so we should update the script for kernel version
4.2.0-27-generic.

This patch fixes the issue.
Closes-Bug: #1541797
Change-Id: I01e98d80df60fe8c5f6ac6e644d42261fdd2921c

Libvirt stores some information in /run at runtime that is needed to
automatically reestablish a connection with the VM when a new
container is created. Without this information a long (and manual)
process is needed to redefine the running vms and reattach to the
running qemu process.

This mountpoint was removed as "unneeded" in the past, but it does
exist in Liberty branch enabling a no-vm-downtime upgrade.

TrivialFix

Change-Id: I2eb31c602d8d17cbd6a8e405daf4123070794843

This change breaks ubuntu

This reverts commit 04992a3d.

Change-Id: I5e38d4c4a37ee90603ad04ab4b9d03298b6b2eb2

The install type is converted in kolla-build, so it will never
fail in dockerfile, move the check to kolla-build just above
the install type converting.

TrivialFix

Co-Authored-By: Jeffrey Zhang <jeffrey.zhang@99cloud.net>
Change-Id: I1500d3b47e909f94ea9f68c5245297733f63a70b

TrivialFix

Change-Id: I1c0a80f7781aa196023795a6381443d6835d534c

TrivialFix

Change-Id: I73f780d72fc30ff3adf3e70ed03361dcb76b451d

Change-Id: I3afb8a29c4ae2369f29e0cc94d75ff8a3c42594b
Implements: blueprint custom-repos

Adding the necessary spaces.
TrivialFix

Change-Id: I3858ed1cb978bcf8aefd4a85f7c802607876b36e

Trivial Fix

Change-Id: Ic14778bb4e894490a3b6af9471ba01ab4da94601

Partially-Implements: blueprint upgrade-kolla
Implements: blueprint upgrade-horizon
Change-Id: I11f11a684becd43cb137fe2c5694ca7e887b38ba

This is a required patch.

Kilo introduced a nova-api database but didn't use it. [1]
Mitaka now uses it and has broken booting instances. [2]

[1] https://wiki.openstack.org/wiki/ReleaseNotes/Kilo#OpenStack_Compute_.28Nova.29
[2] https://github.com/openstack/nova/blob/df0fca62cf5324f5b6eae0fed1f88c6c9ed61c71/releasenotes/notes/request-spec-api-db-b9cc6e0624d563c5.yaml

Change-Id: If0a7f4ba4937fab8d60f5236ca00db06faa768c7
Closes-Bug: #1540579

This change is needed for clarity. We have a kolla-ansible script.
We have a kolla-mesos repo. We plan to have a kolla-ansible repo.
Already we have had far too much confusion about whether we are
talking about the container or the project. Naming this kolla-toolbox
eliminates all of that confusion and its probably a bit more accurate
of a name too.

Closes-Bug: #1541053
Change-Id: I8fd1f49d5a22b36ede5b10f46b9fe02ddda9007e

Change-Id: I5b40de377ac0323d3253f58b49318d57da347d11
Parially-Implements: blueprint enable-manila-containers