aboutsummaryrefslogtreecommitdiff
path: root/docker/heat/heat-api/extend_start.sh
AgeCommit message (Collapse)AuthorFilesLines
2026-07-06Migrate to pyproject.tomlMichal Nasiadka1-17/+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>
2026-04-28Remove httpd_setup calls from api containersMichal Nasiadka1-2/+0
We have dropped mod_wsgi support from services in [1]. [1]: https://review.opendev.org/c/openstack/kolla-ansible/+/982414 Change-Id: Ie5da8427706dfb74bad4e174c990355a6870114c Signed-off-by: Michal Nasiadka <mnasiadka@gmail.com>
2020-10-04Checks for heat_user_domain explicitlyFabian Bermel1-2/+4
The script should check for heat_user_domain explicitly instead of matching on "heat" Closes-Bug: #1839824 Change-Id: Iac83444487d2aa96a0f90086029f43922d1e7856
2019-12-11Refactor Apache httpd setupMark Goddard1-0/+2
All Apache httpd setup has been moved to a new helper script, kolla_httpd_setup. This includes the existing clean of /run/httpd, /var/run/httpd, /tmp/httpd etc. Horizon has an additional bit of Apache config for Debian/binary, which has been kept in extend_start.sh for horizon. Change-Id: Ia2af74b69c151db0bd7e452460b0babcee50b282 Related: blueprint centos-rhel-8
2016-09-19Create the heat_stack_user/owner role in the heat roleChristian Berendt1-2/+0
Change-Id: I78ce0071474fc693aa2a05397b2a9b5974266cd9 Partial-bug: #1609814
2016-08-11Add --user-domain when adding heat role adminDave Walker (Daviey)1-1/+1
The --user-domain parameter is required when adding the role for Heat. Without it, the command fails and the bootstrap container exits early with the error message: "No user with a name or ID of 'heat_domain_admin' exists." Change-Id: I6f813edde3f437bca3ef521a43454146082bc5f5 Closes-bug: #1611768 Signed-off-by: Dave Walker (Daviey) <email@daviey.com>
2016-04-12Make Heat bootstrapping idempotentSteven Dake1-1/+1
Change-Id: I155707ec6c1973d2a36606a0c73e57bda58ed037 Closes-Bug: #1569696
2016-03-24Change heat domain to heat_user_domainSamYaple1-3/+3
heat_user_domain is what is in the docs, but more importantly it is what we have in Liberty and will be a requirement to doing upgrades properly. Change-Id: I9cf53d43b4faaa5d1b0156cc50192722d2739602 Closes-Bug: #1553565
2016-03-09Upgrade HeatSteven Dake1-5/+9
This could possibly use gold plating in how bootstrapping operates to use shade rather than the shell in the container. It is unclear why stack create failed prior to this patch, but that fact hasn't changed. I think the heat domains are not setup properly in the configuration files, meaning that the domain ID must be created outside of Heat and registered in the configuration file. This is covered in Bug #1553565. Change-Id: I490d4dd68a101f388c0ecb4acab54d5eaa6e314e Partially-Implements: blueprint kolla-upgrade Implements: blueprint upgrade-heat
2016-02-24Remove duplicate code in heat extend_start.shÉric Lemoine1-7/+0
Change-Id: I8970d02ccbed1dfc221683e273edc2680207056b Partial-Bug: #1546944
2016-02-19Make Heka collect Heat logsÉric Lemoine1-0/+7
Partially implements: blueprint heka Change-Id: Ie22c4326c6ec2a3426b0c3b8fda4554b1b2541b0
2016-01-28Use trusts in heat.confMichal Rostecki1-3/+5
Change-Id: Ie91b3498e9f9d0d74a502ba6945db531ef967516 Closes-Bug: #1492736
2015-11-11Drop root for heatSteven Dake1-1/+1
Drop root user for heat containers. Change-Id: Ib07c0193f97bb18cc6154b4015b4056fd983f6c1 Partially-Implements: blueprint drop-root
2015-10-13Fix issue with su and bad kernelsSam Yaple1-1/+1
Long story short, some kernels before 3.15 had an issue with using su in a container when the network namespace was --net=host. The gate has a 3.10 and a 3.13 kernel and has a problem with this. This changes everything to use sudo backport: liberty Partially-Implements: blueprint functional-testing-gate Change-Id: I4d79ccaa1cddffcc8393f64e7e1be2538efe33e5
2015-10-06Common start.shSam Yaple1-0/+11
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 21:48:15 +0000