9 Commits

Author SHA1 Message Date
Jeffrey Zhang
e9929dae60 Revert "nova-libvirt: fix kvm permission issue"
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
2017-09-06 18:05:31 +08:00
Zhangfei Gao
43650d5837 nova-libvirt: fix kvm permission issue
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 <kevin.zhao@linaro.org>
Signed-off-by: Zhangfei Gao <zhangfei.gao@linaro.org>
2017-08-15 09:43:48 +08:00
Sam Yaple
58eee09c15 use static uid/gid in images
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 <klindgren@godaddy.com>
Change-Id: I120f26ab0683dc87d69727c3df8d4707e52a4543
Partially-Implements: blueprint static-uid-gid
2017-01-17 09:02:21 -03:00
Serguei Bezverkhi
584690a9f2 Fixing permission for libvirtd.log
Fixing permissions so all users could access libvirtd.log

Change-Id: I6f63a847ba9c5591a87922d3b117b101100b2fad
Closes-Bug: 1563430
Co-Authored-By: Steven Dake <stdake@cisco.com>
2016-03-29 13:52:52 -04:00
Vikram Hosakote
7af0ab9ba9 Make heka collect libvirtd.log in nova_libvirt container
Test results of this patch set are at:
http://paste.openstack.org/show/491382/

Change-Id: I1bc8bdb3180f30dc69af28a35fa057ac801bde0f
Closes-Bug: #1560298
2016-03-22 03:23:41 +00:00
Éric Lemoine
ede53b1dcb Remove duplicate code in nova extend_start.sh
Change-Id: I37d737509bc7cf3dc74bb13ecb0a6ae68080556e
Partial-Bug: #1546944
2016-02-23 08:58:46 +01:00
xionglingfeng
35660e0e10 Multiple hypervisor driver support for nova
Change-Id: I84a7c817dec17175eb1a5cda64ba9e5056c57e50
Implements: blueprint nova-multiple-drivers
2016-02-22 23:27:00 +00:00
Éric Lemoine
511a758982 Make Heka collect Nova logs
Partially implements: blueprint heka
Change-Id: I67dfc5d762d74454e4a852dd61c57fe9cd4b78c8
2016-02-19 21:49:18 +00:00
Sam Yaple
cb4e875ae1 Common start.sh
The majority of the start.sh code is identical. This removes that
duplicate code while still maintaining the ability to call code in a
specific container.

The start.sh is moved into /usr/local/bin/kolla_start in the container

The extend_start.sh script is called by the kolla_start script at the
location /usr/local/bin/kolla_extend_start . It always exists because
we create a noop kolla_extend_start in the base directory. We override
it with extend_start.sh in a specific image should we need to.

Of note, the neutron-agents container is exempt from this new
structure due to it being a fat container.

Additionally, we fix the inconsistent permissions throughout. 644 for
repo files and the scripts are set to 755 via a Docker RUN command to
ensure someones local perm change won't break upstream containers.

Change-Id: I7da8d19965463ad30ee522a71183e3f092e0d6ad
Closes-Bug: #1501295
2015-10-06 03:30:26 +00:00