openstack/kolla.git/ansible/roles/nova/tasks/start.yml, branch master

Remove Ansible from Kolla

2016-11-16T04:34:17+00:00

Change-Id: I5396e4b9927d3e65b6aa4185238a43a4765a996b

Playbook for nova upgrade

2016-02-19T19:58:18+00:00

This creates tree and playbook for nova upgrade. Also other service upgrades will follow standard setup here. Change-Id: Ic31759efaee4986eb87b9ff0968f13189d130d48 Partially-Implements: blueprint upgrade-kolla Implements: blueprint upgrade-nova

Move socket binding to named_volume

2016-02-16T14:42:41+00:00

The extend_start.sh script for rsyslog is removed as it is no longer needed. Docker no longer binds to /dev/log or /run/kolla/log Closes-Bug: #1544545 Change-Id: Ic0a323a26ee4e9e15baf4598285844a8a4955f23

Fix gate for docker 1.10

2016-02-06T06:48:53+00:00

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

Make libvirt reestablish connection with qemu

2016-02-04T12:15:36+00:00

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

Fix permissions to /var/lib/nova/

2016-01-20T16:58:01+00:00

Due to changes with the drop-root work, we lost the ability to write to /var/lib/nova/*. This fixes those permissions and ensures cross container talk works properly between nova_libvirt and nova_compute Additionally, this fixes another issue introduced which saw that nova-compute could not run sudo commands as it did not have a proper sudoers entry Testing from previous deploys means you need a fresh environment. You have to remove all of the named volumes that kolla created in docker. Check these with `docker volume ls` Signed-off-by: Hui Kang Signed-off-by: Artur Zarzycki Co-Authored-By: Sam Yaple Co-Authored-By: Hui Kang Closes-Bug: #1533350 Change-Id: I7f864c448a2414e0b5d89f48337be411b891df35

Convert to named volumes instead of data container

2016-01-03T16:44:44+00:00

This intentionally leaves out rabbitmq from this patchset. It will require additional work to remove its data container UpgradeImpact Partially-Implements: blueprint docker-named-volumes Change-Id: Id68b8e43a3c077ef4f4f4d67ea34d0692e66eef7

Convert Nova to kolla_docker

2015-12-31T16:38:56+00:00

Change-Id: I0c6df8e7b732a37ff3cabff8d588f8b7d15df192 Partially-Implements: blueprint kolla-docker-module

Enable nova fake driver in nova containers

2015-12-29T11:39:35+00:00

- See instructions in doc/nova-fake-driver.rst Implements: blueprint nova-fake-driver Change-Id: I553a40c2df39bdcc391eb1b8b2b8fd5f4ed48c33 Signed-off-by: Hui Kang Signed-off-by: Marcio D. Silva

Add container for nova-compute-ironic

2015-12-25T17:09:00+00:00

Implements blueprint ironic-compute-container Change-Id: I110bf3aa94bdfd33038ed39d78bd40ea30b13e57