This bug was reported by eandersson in IRC today.

TrivialFix

Change-Id: I3100d2bc567f641894817bd9cf3b2213416085b2

On computers with wi-fi adapters, promiscuous mode on the VirtualBox (or
maybe other hypervisors as well) NICs does not work, which means the
default way of connecting the Neutron external interface to a bridged
adapter, will not allow communication to and from the Nova VMs over
floating IPs with any computer on the external network (except the host
computer) or with the wi-fi router. This means no ability to connect to
the Nova VMs and no internet access inside the Nova VMs.

According to VirtualBox documentation (excerpt): "Bridging to a wireless
interface is done differently from bridging to a wired interface,
because most wireless adapters do not support promiscuous mode. All
traffic has to use the MAC address of the host’s wireless adapter, and
therefore VirtualBox needs to replace the source MAC address in the
Ethernet header of an outgoing packet to make sure the reply will be
sent to the host interface. When VirtualBox sees an incoming packet with
a destination IP address that belongs to one of the virtual machine
adapters it replaces the destination MAC address in the Ethernet header
with the VM adapter’s MAC address and passes it on. VirtualBox examines
ARP and DHCP packets in order to learn the IP addresses of virtual
machines."

To fix this issue, a new flag has been introduced: WIFI. If true, the
default Vagrant public network is not created anymore. Instead, the 3rd
NIC will be connected to a NAT-Network named OSNetwork. The NAT-Network
has a virtual gateway, which will be used to communicate with the
external physical wi-fi router. Since Vagrant does not have a high-level
mechanism to attach an adapter to a NAT-Network, the code uses the
low-level Vagrant construct vm.customize which makes it provider
specific.

Promiscuous mode is now activated by default on the 3rd NIC.

The WIFI flag is false by default.

This commit only addresses VirtualBox, and it is currently unknown if
the problem described and fixed in this commit is present in other
hypervisors.

DocImpact
Closes-Bug: #1558766
Change-Id: I0b4dbbc562d87191b2179f47b634cdd6f6361a5e
Signed-off-by: Andrei-Lucian Șerb <lucian.serb@icloud.com>

the prechecks role should be idempotent and should changed nothing when
running.

TrivialFix

Change-Id: Ib5063d879e0f5f414d607bd9b6493a7499fc5652

pymongo is needed when ceilometer uses mongodb as backend database

Change-Id: Id75dc7bed30cdfa12f95bb66ca6d4cdf7be0261c
Closes-Bug: #1559370
Related-Bug: #1559390

Just like last cycle, I ran all of the requirements and found the
packages that were installed >=10 times throughout our containers. By
combining them in the openstack-base we reduce the size of the images
by ~600MB (10%) and decrease build time by a measurable amount (5-10m
in the case of Centos)

TrivialFix
Change-Id: I582d75644a8e8b936c6f9fc10c6b5821e1e8c5c4

We were specifying the wrong driver in our nova.conf

Change-Id: I37a3d366f2895b9d1281815ef85209feaa37b92d
Closes-Bug: #1559494

Some gates are failing to properly pull all logs out resuling in an
UNSTABLE status.

This resets all logs to 777 perms to ensure readability by jenkins.

TrivialFix

Change-Id: Ib92c5bfea5fa8bcc6380ad8aa6001b13888717ac

While it's possible to edit distro/package unit files installed to
/lib/systemd/system, a cleaner solution exists.  systemd will pick up
'drop-in' unit files located in '/etc/systemd/system/[unit name].d/'.
A drop-in unit file only has to include fields that override those in
the main unit file, and the drop-in unit and main unit file can change
independently.

This change updates the quickstart doc to use drop-in unit files to
configure docker.service instead of editing the main unit file.

See: https://coreos.com/os/docs/latest/using-systemd-drop-in-units.html

Change-Id: Iddbebf658741937e3c4157fc0a021751f10fabd2

Rabbitmq can't work with IPs, so we need to make sure that all
rabbit cluster hosts can resolve each others hostnames. We
should also require that in docs.

DocImpact
Closes-Bug: #1559158

Change-Id: I2418187138988d21da3dc3624e9cdbda891d4894

During multi-node, it is possible for master target node images to
be older then the Ansible master playboks if the repository is
updated.  Add documentation to explain this situation.

Change-Id: I2ccf57004147873e89f23fbb996d01f550e90c3f

This bugfix fixes incorrect swift proxy-server endpoint.

Closes-Bug: #1559207

Change-Id: Idcdbaedbbde4922b0d5e31557aaf5cfcfdff8636

Change variable name ceph_use_cache to ceph_enable_cache

TrivialFix

Change-Id: Ifeabf2a7212a78a81703f3e867c2566652b1aebc

Test results of this patch set are at
http://paste.openstack.org/show/490450/.

Change-Id: I2957cc70fcca34706ec50a630d785f0630c3f5c0
Closes-Bug: #1553203

This matches the current default for nova.conf. Use unmap/discard if
t is enabled on the hypervisor. This option is new for mitaka.

TrivialFix

Change-Id: Id94c05e2ec8a65c75ec82afcd4150390f8b87ee2

The home directory for Ansible already exists and does not
need to be created.  Reorder useradd and mkdir at suggestion
of Jeff Peeler to avoid warning.

The warning looks like this:

INFO:__main__:kolla-toolbox:Step 6 : RUN mkdir -p /etc/ansible /usr/share/ansible /home/ansible     && echo 'localhost ansible_connection=local' > /etc/ansible/hosts     && useradd --user-group ansible --groups kolla     && sed -i 's|  "identity_api_version": "2.0",|  "identity_api_version": "3",|' /usr/lib/python2.7/site-packages/os_client_config/defaults.json
INFO:__main__:kolla-toolbox: ---> Running in ccded9c01fca
INFO:__main__:kolla-toolbox:useradd: warning: the home directory already exists.
INFO:__main__:kolla-toolbox:Not copying any file from skel directory into it.
INFO:__main__:kolla-toolbox:

TrivialFix

Change-Id: I031ade6597f8071f5be1768a7e70b1008dd94e52

This patch adds some explanations for different options available
in /etc/kolla/globals.yml for customizing swift configuration.

Trivial fix

Change-Id: Iaf03f5293804d63c87d8881ac4282909a81b0bfe

This type of per node configuration is required to support things like
availability zones for nova. As always, if this file doesnt exist it
doesnt get used so this change is safe.

TrivialFix

Change-Id: Iff8172af522c2c96e5f2c173b24a5dfd4d522ed2

This now matches the way we copy confis in other services.

TrivialFix

Change-Id: Ia9c6d5f9a633c0b20b4d9a697863bd2753d39443

TrivialFix

Change-Id: I9e7e65d6e5ddfb3c387e147a8cc6f5aae1aab0cd

TrivialFix

Change-Id: Ic946c613e5197d988897bd450040a1ea66a60f77