aboutsummaryrefslogtreecommitdiff
path: root/docker/neutron/neutron-server/extend_start.sh
AgeCommit message (Collapse)AuthorFilesLines
2026-07-06Migrate to pyproject.tomlMichal Nasiadka1-34/+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>
2020-09-30Fix Neutron migrations orderRadosław Piliszek1-2/+2
It seems I mixed up the order when commenting/uncommenting. Neutron base has to go first. Change-Id: Ib2bf51d4c6e2a574b98671a699777cd8a9a22768
2020-09-23Restore Neutron migrationsRadosław Piliszek1-12/+10
For details see [1]. Note this will also be amended on the Kolla-Ansible side to squash [2] as well. [1] https://review.opendev.org/750075 [2] https://bugs.launchpad.net/kolla-ansible/+bug/1894380 Change-Id: Id47ea8a5ea5318a69cf6814162db2115b40c7e6f
2020-09-05Emergency fixes to pass CIRadosław Piliszek1-17/+14
1) makes bifrost unbuildable as it evolves rapidly at the moment 2) makes neutron bootstrap/upgrade only the core service [1] 1) will be reverted 2) will be made more flexible [1] https://bugs.launchpad.net/bgpvpn/+bug/1894056 Change-Id: I1eefcfceded985b5f61ee8d796f9d8994c9ee97c
2020-06-18Remove deployment of FWaaSAlfredo Moralejo1-1/+0
FWaaS is being retired upstream [1][2] in V cycle. [1] https://review.opendev.org/#/c/735838/ Change-Id: I45679c8596844780565644e52034bd3de0915ff4
2020-03-18neutron: Remove networking-ovn - part 2Michal Nasiadka1-1/+0
A followup to change [1]. Remove networking-ovn sources from kolla/common/config.py and neutron-db-manage call in neutron-server/extend_start.sh [1]: https://review.opendev.org/712762/ Change-Id: I976d60e5f2bf3e8a55b90485a77584d9e7579d62
2020-01-08Add OVN bits to neutron-baseMichal Nasiadka1-0/+1
Currently neutron-server-ovn container does not run db setup for networking-ovn subproject when bootstrapping - since it uses extend_start from neutron-server (where networking-ovn is not installed). Since OVN is being added as in-tree driver to Neutron and there is no rationale behind supporting separate container images for neutron-server-ovn and neutron-metadata-agent-ovn, hile networking-ovn driver uses around 1-2MB of space - this change adds networking-ovn installation to neutron-base image and deprecates neutron-server-ovn and neutron-metadata-agent-ovn images. Change-Id: Ib2dbdd7e7d34f56985b7a5b2494c3b89034688cb
2019-11-19Neutron: apply db migration for BGP dynamic routing agentViktor Michalek1-0/+1
Change-Id: Id84d5a1b3c70c0260b85ed7c24aa7f1e007c12d6 Closes-Bug: 1848572
2019-06-15Merge "[neutron] Do not migrate all subprojects"Zuul1-1/+1
2019-06-05[neutron] Do not migrate all subprojectsJason1-1/+1
Instead of migrating all Neutron subprojects at bootstrap time, target specifically the neutron, neutron-fwaas, and neutron-vpnaas subprojects speficially. If a subproject is not specified, all subprojects are migrated, which is not the intended behavior. Change-Id: Icb8d572b7f084804e0423a8a3171dd66646b3885
2018-06-21Only run rolling upgrade for neutron, vpnaas, fwaasDuong Ha-Quang1-2/+8
Due to only neutron, vpnass and fwaas have supported for rolling upgrade database migration, this patch set add --subproject argument to limited the upgrade to these. Co-Authored-By: Ha Manh Dong <donghm@vn.fujitsu.com> Change-Id: I007e0068622fd630eb9f2f29b604015376ae7cd3 Implements: blueprint apply-service-upgrade-procedure
2018-03-08Migrate neutron-vpnaas-agent to neutron-l3-agentchenxing1-0/+1
Depends-On: I880ef5dad6723de06da5dd8a424f7158d65b5a35 Depends-On: I52efd29791a230df1ce7e3acde4b7184aec34150 Change-Id: I47cd8ba5a14da3c76d5b1eb0b4c0cf0c729eb2ff Partially-Implements: blueprint restructure-neutron-vpnaas
2017-11-17Typo in neutron-server/extend_start.shsairamp1-1/+1
The variable is defined as "OTPS" and in the rest of the code it is referred as "OPTS" Change-Id: Ic8b2bab64afa4e54e8c69b2cd94a7d6cad361c3a
2017-10-13Upgrade neutron-fwaas db during bootstrapJeffrey Zhang1-1/+3
Closes-Bug: #1719775 Change-Id: I76803f0f81260129a242e31e81f4f956c5a44ef9
2017-06-28Add sfc plugin into neutron-base imageEduardo Gonzalez1-0/+8
Neutron-server and openvswitch-agent images consume sfc plugin code to run sfc services. This change adds db sync for sfc plugin. Also move sfc code into neutron-base so other services can make use of the plugin. Change-Id: I60ba1333231a4ae38a041d41e551f7d74fe15e3b Closes-Bug: #1664493
2017-01-26Apply neutron database migrationDuong Ha-Quang1-0/+14
Apply neutron database migration procedure: http://docs.openstack.org/developer/neutron/devref/upgrade.html#server-upgrade Change-Id: Id03e6cdd822bb8bd3d70ae1a1f70ccd9aba830ff Implements: blueprint apply-service-upgrade-procedure
2016-02-24Remove duplicate code in neutron extend_start.shÉric Lemoine1-7/+0
Change-Id: I74aa68d809e9b38a605093abc4e2b8ca14335dee Partial-Bug: #1546944
2016-02-19Make Heka collect Neutron logsÉric Lemoine1-0/+7
Partially implements: blueprint heka Change-Id: I70e94f4ef7380c6f376a3066d7ddda042c703637
2016-02-06Convert Neutron to thin containersSamYaple1-11/+1
*** Requires Docker 1.10 which is released *** Documentation will be in the next patch. You must set the following in your docker.service daemon control file for propogation to work: [Service] MountFlags=shared ====================================================================== Thanks to mount propagation in Docker 1.10 we can use thin containers finally! This is extremely useful to operators since now they can access the network namespaces from the hosts (outside the neutron container). But additionally it allows us to implement the VPN agent and other services easier. Neutron containers and the neutron role are brought into the standards of the new Kolla. Completely with drop-root and ansible formating updates. The ip_wrapper.py script was (thankfully) not needed so it has been removed from the repo. Partially-Implements: blueprint upgrade-neutron Change-Id: Iaf5555283240457e1912459f397a6393d886fba1
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/+18
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 22:22:23 +0000