openstack/kolla.git/docker/nova/nova-libvirt/extend_start.sh, branch zed-eol

Remove TODO in libvirt script

2020-07-31T09:06:28+00:00

This is no longer required when Kolla-Ansible is patched. Note this is *not* safe to backport as it requires the user to have Kolla-Ansible patched, i.e. would normally break most. Change-Id: Ic5b9a58d212711a4d6c13822548c92013a6bae50 Related-Bug: #1681461 Depends-On: https://review.opendev.org/735441

Let nova-libvirt restarting be independent of libvirtd.log

2019-12-06T01:49:06+00:00

Modify nova-libvirt extend_start.sh for preventing docker boot fail if there is no libvirtd.log file in libvirt folder. Change-Id: If1df41fb07b90b6020a60e3f987d51f5a9792bca Closes-Bug: 1855253

Revert "nova-libvirt: fix kvm permission issue"

2017-12-11T09:43:24+00:00

This is not needed. If we make sure qemu use nova user. Because nova user in group qemu. See comment #7 of bug #1715356: The root cause for this issue is that qemu not run with nova user on debian. If we set qemu running with nova user with this patch: https://review.openstack.org/#/c/525891/ Then we need to revert commit f1b98a4925826333cf22dafe15ef755066c51d48. This reverts commit f1b98a4925826333cf22dafe15ef755066c51d48. Closes-bug: #1715356 Depends-on: I36720af0c7d3dd7c69d2404843f54c0991aea1bb Change-Id: I62fbcf9e4ee5c3170c96576698f4ae8b66db1b74

nova-libvirt: fix kvm permission issue

2017-10-23T10:01:27+00:00

When deploy in AArch64, will meet kvm permission issue. Fix it with Arch specified. Closes-bug: #1715356 Change-Id: I09dc27693a83dc77704773a25547725de480dbe8 Signed-off-by: Kevin Zhao

Revert "nova-libvirt: fix kvm permission issue"

2017-09-06T10:05:31+00:00

This reverts commit 43650d5837372449294a7a22e9c9167a92744e96. This fix do not work with CentOS x86_64. Since I haven't arm64 env, and we have fix this soon before pike is release. Just revert this and fix in the future. Change-Id: Id9eb531de7d05051f38e3ed13b64ae7abf552767 Partial-Bug: #1715356

nova-libvirt: fix kvm permission issue

2017-08-15T01:43:48+00:00

When deploying on arm64, permission denied reported: Terminating instance: libvirtError: internal error: process exited while connecting to monitor: Could not access KVM kernel module: Permission denied Fix the issue via "chown root:kvm /dev/kvm" Change-Id: Ib963741918b47d924ca0716643ac14a3fc3cfab2 Signed-off-by: Kevin Zhao Signed-off-by: Zhangfei Gao

use static uid/gid in images

2017-01-17T12:02:21+00:00

This centralizes all user and group creation into a single source. This will fix any current and furture uid/gid mismatches (such as with nova-libvirt). In the process, we also unify users between the distros in a standard way. The users in the following containers change from thier defaults: Ubuntu: _chrony user is now chrony Ubuntu: memcache user is now memcached All: qemu user is used for ownership and socket permissions All uid and gid numbers are customizable via kolla-build.conf Co-Authored-By: Kris Lindgren Change-Id: I120f26ab0683dc87d69727c3df8d4707e52a4543 Partially-Implements: blueprint static-uid-gid

Fixing permission for libvirtd.log

2016-03-29T17:52:52+00:00

Fixing permissions so all users could access libvirtd.log Change-Id: I6f63a847ba9c5591a87922d3b117b101100b2fad Closes-Bug: 1563430 Co-Authored-By: Steven Dake

Make heka collect libvirtd.log in nova_libvirt container

2016-03-22T03:23:41+00:00

Test results of this patch set are at: http://paste.openstack.org/show/491382/ Change-Id: I1bc8bdb3180f30dc69af28a35fa057ac801bde0f Closes-Bug: #1560298

Remove duplicate code in nova extend_start.sh

2016-02-23T07:58:46+00:00

Change-Id: I37d737509bc7cf3dc74bb13ecb0a6ae68080556e Partial-Bug: #1546944