aboutsummaryrefslogtreecommitdiff
path: root/docker/nova/nova-libvirt/extend_start.sh
AgeCommit message (Collapse)AuthorFilesLines
2026-07-06Migrate to pyproject.tomlMichal Nasiadka1-11/+0
[tool.setuptools.data-files] does not support recursive directory installation. The old setup.cfg [files] worked because PBR's FilesConfig.expand_globs() used os.walk() to expand docker/*, but this hook is not triggered by the pbr.build PEP-517 backend. Move docker/ into kolla/ and use [tool.setuptools.package-data] instead. Update kolla_worker._get_images_dir() to check the kolla package directory first so both editable and regular installs work. Change-Id: I4fc452c03740ef22ebbb4e8d0d86c4f4783e2d09 Signed-off-by: Michal Nasiadka <mnasiadka@gmail.com>
2024-08-19nova: Drop xen remnantsMichal Nasiadka1-5/+0
Xen support in Nova has been dropped cycles ago. Change-Id: Ieb52291529eb0d94206b3f30195c4d2527c9dc52
2020-07-31Remove TODO in libvirt scriptRadosław Piliszek1-8/+0
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
2019-12-06Let nova-libvirt restarting be independent of libvirtd.logyuchengde1-1/+1
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
2017-12-11Revert "nova-libvirt: fix kvm permission issue"Xinliang Liu1-11/+2
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
2017-10-23nova-libvirt: fix kvm permission issueKevin Zhao1-2/+11
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 <kevin.zhao@arm.com>
2017-09-06Revert "nova-libvirt: fix kvm permission issue"Jeffrey Zhang1-1/+1
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-08-15nova-libvirt: fix kvm permission issueZhangfei Gao1-1/+1
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-01-17use static uid/gid in imagesSam Yaple1-1/+1
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
2016-03-29Fixing permission for libvirtd.logSerguei Bezverkhi1-0/+3
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-22Make heka collect libvirtd.log in nova_libvirt containerVikram Hosakote1-0/+7
Test results of this patch set are at: http://paste.openstack.org/show/491382/ Change-Id: I1bc8bdb3180f30dc69af28a35fa057ac801bde0f Closes-Bug: #1560298
2016-02-23Remove duplicate code in nova extend_start.shÉric Lemoine1-7/+0
Change-Id: I37d737509bc7cf3dc74bb13ecb0a6ae68080556e Partial-Bug: #1546944
2016-02-22Multiple hypervisor driver support for novaxionglingfeng1-0/+5
Change-Id: I84a7c817dec17175eb1a5cda64ba9e5056c57e50 Implements: blueprint nova-multiple-drivers
2016-02-19Make Heka collect Nova logsÉric Lemoine1-0/+7
Partially implements: blueprint heka Change-Id: I67dfc5d762d74454e4a852dd61c57fe9cd4b78c8
2015-10-06Common start.shSam Yaple1-0/+9
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
generated by cgit v1.2.3 (git 2.39.1) at 2026-11-05 20:34:20 +0000