aboutsummaryrefslogtreecommitdiff
path: root/docker/neutron/neutron-server
AgeCommit message (Collapse)AuthorFilesLines
2026-07-06Migrate to pyproject.tomlMichal Nasiadka2-67/+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-06-24kolla-build: fix build-date LABEL invalidating Docker layer cacheMichal Nasiadka1-1/+1
The build-date label was rendered into a LABEL instruction on line 3 of every Dockerfile template, immediately after FROM. Because Docker invalidates the cache for a changed instruction and all subsequent layers, a date change caused a full rebuild of every image on each new calendar day, even when nothing else had changed. Fix this by removing build-date from the Dockerfile templates and applying it as a --label argument at build time via image.labels. Labels passed on the build command line are not part of the Dockerfile cache key, so the date is still recorded in the image metadata without affecting layer caching. Change-Id: I8ef0d85bab1a999a4d09f7cbf0c088ca00fdcf77 Signed-off-by: Michal Nasiadka <mnasiadka@gmail.com>
2024-11-15Add mechanism for patching files in containersMichal Arbet1-0/+2
This patch adds a way to patch files in a Docker image built by Kolla. This is very useful for several reasons, specifically: - Custom modifications - The stable branch of some library has a fix but no pip package has been released - Eliminates the need to package your own pip packages - Eliminates the need to invent your own versioning to prevent upstream versioning - Eliminates the need to manage a pip server - In other words, it eliminates the need to get a wheel into the image and install it manually using any method not previously mentioned It is also highly desirable because, although Kolla can replace the source for a service with a custom URL for a tarball or its own Git repo, it cannot do this for dependencies pulled from pip. I would also like to point out that this is a feature with its own code path and works only if the user "inserts" a patch into the folder patches/docker-image/something.patch and creates an analogous series file for patch source code. Simply said, this code will never interfere with the upstream build process since this feature is not intended for use in upstream. It is rather meant for downstream users who know what they are doing. Now they just have an option to patch their images. Everything works on all layers of the Docker image and stores a report of applied patches which can then be seen in /etc. This mechanism is similar as debian patch quilt. Change-Id: I61d0790c5d4d070b7ea9e8c99c0a76ff5d22bf9d
2022-04-22adjust permissions on _extend_start files (part II)Marcin Juszkiewicz1-1/+1
Tim Shearer started it in 1d96a2bbe1b536b7d7f4cdbf55c6dabae6d058ae. Since all extend_start files are sourced rather than executed, the executable bits are now cleared throughout the project. Change-Id: Ia1797c32fc6a35f9f077c673abf4d8e16e51a760
2022-04-21flatten images a bitMarcin Juszkiewicz1-4/+5
As we have one type of images now some RUN calls could be merged so we will have less layers in resulting images. Change-Id: I5178c58fbd8c65efe825dc249c0f1368ef0fe8e0
2022-04-09docker: drop binary partsMarcin Juszkiewicz1-29/+6
Big patch drops all mentions of binary images support. Suggestions are welcome how to split it into parts or handle better. Change-Id: I5d5a46c6ce7734ceb8b844e17b43e359d7cac6e3
2021-08-12ironic-neutron-agent: enable for Debuntu binaryMark Goddard1-0/+1
Packages are available for focal and bullseye. Change-Id: I61623748d1149adb1b096adf2fffb5a902df3181
2021-03-01neutron-server: make it build againMarcin Juszkiewicz1-1/+1
1. stop pinning networking-hyperv Pike release was long time ago so maybe it is time to unpin it? commit 6dc8e978462fd08122133e273ae956721997d3af Author: Dan Ardelean <dardelean@cloudbasesolutions.com> Date: Mon Aug 28 12:56:25 2017 +0300 Change networking-hyperv version for Pike 2. stop install vmware-nsxlib as a plugin vmware-nsx is a plugin and we install it already vmware-nsxlib can be fetched from Pypi Solves: INFO:kolla.common.utils.neutron-server:The conflict is caused by: INFO:kolla.common.utils.neutron-server: The user requested vmware-nsxlib 15.0.8.dev129 (from /plugins/vmware-nsxlib-15.0.8.dev129) INFO:kolla.common.utils.neutron-server: vmware-nsx 15.0.1.dev424 depends on vmware-nsxlib>=17.0.0 Change-Id: I6ef344d463333e5cdc3a0850c8e068218779fdbd
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-04-15Remove support for CentOS 7Marcin Juszkiewicz1-9/+0
With the move to RHEL/CentOS 8 we no longer have Python 2 in our images so there is no need for checking which Python version (2.x or 3.x) is used inside of containers. We also no longer have to support yum as a value for distro_package_manager. Partially-Implements: blueprint centos-rhel-8 Change-Id: Ie45cf3465fedddbde7856961527421883ba3d5c9
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-03-01Add block labels to all DockerfilesChristian Berendt1-0/+2
Change-Id: I9692dda817ef134d647247431565e1b58cf9da41
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-07Remove Neutron LBaaS supportCarlos Goncalves1-2/+0
The project has been retired and there will be no Train release [1]. This patch removes Neutron LBaaS support in Kolla. [1] https://review.opendev.org/#/c/658494/ Depends-On: https://review.opendev.org/#/c/663875/ Change-Id: I99484c48ed09f7e015e134bdff1f298c359c6905
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
2019-03-12Add python3 packages for RHEL systemsAlex Schultz1-2/+10
RDO is currently working on python3 support for the next version of CentOS/RHEL based systems. This package uses the distro_python3 flag that was added as part of I4028991bad92c0e8e21066cc4173c06ce5eba393 to use the python3 specific package names. This change only adds python3 package names for RHEL systems. Conflicts-With: https://review.openstack.org/#/c/636457/ Change-Id: Iad6b70b433a0dd1b0f8ae6790fd280594517661a Related-Blueprint: python3-support
2019-02-28debian/ubuntu: make use of Python3 based packagesMarcin Juszkiewicz1-3/+3
Both Ubuntu Stein UCA and Debian 'buster' migrated their OpenStack packages to Python 3. Note that Debian 'buster' is not released yet and contains Rocky packages. Stein ones will be available later. Co-Authored-By: Lee Yarwood <lyarwood@redhat.com> Co-Authored-By: Eduardo Gonzalez <dabarren@gmail.com> Change-Id: I160f79cc57f54ec3eac857c5babd1a6e2656d228
2019-01-17Use base_package_typeAlex Schultz1-2/+2
This change updates the docker files to use base_package_type instead of doing specific distro checks for the rhel/deb generic cases. The base_distro is still available and is used when a specific distro needs a customization but if the differences are purely rpm vs deb, then the base_package_type can be used. Change-Id: I8d720bb185df65a0178061ccf20b1ab2265da2c5
2018-08-16Add networking-generic-switch to neutron-serverWill Miller1-1/+2
Change-Id: I75c460bda4c85016446f6a8df14e53806f8ef414
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-19Merge "Remove the unnecessary "openstack-neutron-lbaas" from neutron-server"Zuul1-1/+0
2018-03-13Merge "Remove customizable for plugins_pip_packages"Zuul1-1/+1
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
2018-01-23Remove customizable for plugins_pip_packagesMartin André1-1/+1
The pip packages are normally already configurable with the <image_name>_pip_packages variable. It doesn't make much sense to make the list of packages installed with the plugins mechanism configurable via the <image_name>_plugins_pip_packages variable too. And even if we wanted to, the parameter to the `customizable()` function should be 'plugins_pip_packages' and not 'pip_packages'. This commit removes the customizable bits from the plugins install macro, at least until we get a good use case for it. Change-Id: I90dd28b8c5d981e6028af353e34645712ef09b0b
2018-01-16Remove the unnecessary "openstack-neutron-lbaas" from neutron-servercaoyuan1-1/+0
since openstack-neutron-lbaas has beed installed in neutron-base image, it's no need to install it again install neutron-server. Change-Id: I5219b1d37a408dfeb61fa54133e36751af1ee389
2017-11-29Merge "Typo in neutron-server/extend_start.sh"Zuul1-1/+1
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-11-08Fix missing bgp library in neutron-serverMichal Nasiadka1-0/+1
Closes-Bug: #1730629 Change-Id: Iae9ab6f3bba8185cf1bf53c3a5748e801404aeb7 Signed-off-by: Michal Nasiadka <michal.nasiadka@pl.ibm.com>
2017-10-13Upgrade neutron-fwaas db during bootstrapJeffrey Zhang1-1/+3
Closes-Bug: #1719775 Change-Id: I76803f0f81260129a242e31e81f4f956c5a44ef9
2017-08-28Change networking-hyperv version for PikeDan Ardelean1-1/+1
Change-Id: I56b9ef9ceb449d3fe6f2aa4cf856d6d1d7af7ee9
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-06-12Support VMware DVSjimmygc1-5/+2
Move vmware_nsx and oslo.vmware to neutron_base image to support this change: I6d1629e93f0efeddd2a9000f66cc6f714bebb07c Change-Id: I4655086a3f058ec769d3d37ec6a19565b5ea0841 Partially-implements: blueprint kolla-ansible-support-vsphere
2017-06-04Merge "Add networking-hyperv driver when building neutron-server image"Jenkins1-1/+2
2017-06-02Merge "Only copy plugin-archive into image for source builds"Jenkins1-10/+9
2017-05-24use proper package name for python-oslo.vmwareMarcin Juszkiewicz1-1/+1
python-oslo-vmware was transitional package name Change-Id: Ieb355e30fe7162c035f342fd5b0fb2573365f428
2017-05-18Add networking-hyperv driver when building neutron-server imageDan Ardelean1-1/+2
Change-Id: I31dd5054ea9bf341323f6d093c0667b98491cc2b
2017-05-10Only copy plugin-archive into image for source buildsMartin André1-10/+9
The plugin mechanism is meant to be for source install type only. Change-Id: I1371a253236b09dc62ea91dce6d652e1c5603015 Closes-Bug: #1681345
2017-05-03Override image's meta info.Jawon Choo1-1/+1
centos based images have wrong label info, these changes fix own image's name and build-date. Change-Id: I1d13f8f386c8db12b5fbe5f8ecbbf9e3fbb4ba1c Closes-Bug: #1680341
2017-04-20Use LABEL instead of MAINTAINER (deprecated) in all Dockerfile.j2Chen1-1/+1
Use LABEL instruction instead of MAINTAINER (deprecated) instruc- tion as suggested by Docker's official dockerfile guide. docs.docker.com/engine/reference/builder/#maintainer-deprecated Closes-Bug: #1683652 Change-Id: Ie87a1ddf31aefcd0b623fd2837d78de420e76898
2017-04-06Merge "debian: enable all images enabled for Ubuntu"Jenkins1-1/+1
2017-04-05Add vSphere Supportjimmygc1-1/+12
Add oslo.vmware and vmware_nsx packages into kolla. Change-Id: I2a1ed314b970a4832f7f8256c1929921f36069f2 Implements: blueprint kolla-support-vsphere Co-Authored-By: shaofeng cheng <chengsf@winhong.com>
2017-04-04debian: enable all images enabled for UbuntuMarcin Juszkiewicz1-1/+1
Debian support is not maintained in Kolla so it got a bit behind Ubuntu one. This changeset enables Debian for all images. Jessie (even with backports) may be too old for some images though. Also unify distro check to ['debian', 'ubuntu'] to keep alphabetical order like it is done for RPM distributions. Partially-Implements: blueprint multiarch-and-arm64-containers Change-Id: I056233fbfa277e0e2360c07c3f80d9558c554357
2017-02-24Merge "Apply neutron database migration"Jenkins1-0/+14
2017-02-17Use install-pip macro in most source imagesChao Guo1-1/+6
1. Enable customization of pip packages in source branch of most images 2. All pip packages install uniformly through install-pip macro, user can easily customize his own pip command (For example using a mirror) Co-Authored-By: Mauricio Lima <mauriciolimab@gmail.com> Change-Id: If09582039f690fa4136e8f33200d5da15e092da7
2017-02-05Remove include_header and include_footer in all DockerfilesJeffrey Zhang1-1/+0
include_header and include_footer parameter is already removed, remove them in all Dockerfiles. Add missing footer block. Change-Id: I90da03eb9f95a3827361d5f5ede65fde7d6be2b3
generated by cgit v1.2.3 (git 2.39.1) at 2026-11-05 20:38:48 +0000