openstack/kolla.git/docker/neutron/neutron-server/extend_start.sh, branch master

Migrate to pyproject.toml

2026-07-06T19:59:40+00:00

[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

Fix Neutron migrations order

2020-09-30T16:45:03+00:00

It seems I mixed up the order when commenting/uncommenting. Neutron base has to go first. Change-Id: Ib2bf51d4c6e2a574b98671a699777cd8a9a22768

Restore Neutron migrations

2020-09-23T08:24:29+00:00

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

Emergency fixes to pass CI

2020-09-05T17:42:22+00:00

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

Remove deployment of FWaaS

2020-06-18T22:12:05+00:00

FWaaS is being retired upstream [1][2] in V cycle. [1] https://review.opendev.org/#/c/735838/ Change-Id: I45679c8596844780565644e52034bd3de0915ff4

neutron: Remove networking-ovn - part 2

2020-03-18T08:31:31+00:00

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

Add OVN bits to neutron-base

2020-01-08T08:37:35+00:00

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

Neutron: apply db migration for BGP dynamic routing agent

2019-11-19T21:51:42+00:00

Change-Id: Id84d5a1b3c70c0260b85ed7c24aa7f1e007c12d6 Closes-Bug: 1848572

Merge "[neutron] Do not migrate all subprojects"

2019-06-15T21:11:57+00:00

[neutron] Do not migrate all subprojects

2019-06-05T21:25:05+00:00

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