| Age | Commit message (Collapse) | Author | Files | Lines |
|
Backport this until Train.
CentOS 8.3 renamed system repos. [1]
This caused failures when disabling and enabling.
More details in the referenced bug report.
Notice CentOS 8.2 and below will no longer work.
Train backport also includes some fixes for the
fallout from the new pip resolver.
* cap bandit<1.6.3, since bandit no longer supports
Python 2.
* mark kuryr-libnetwork unbuildable for source
images.
* mark almanach-base & dragonflow-base unbuildable
for Debian & Ubuntu source images.
* Don't install networking-hyperv in source
neutron-server images. pip complains of a conflict.
(https://bugs.launchpad.net/kolla/+bug/1907826)
[1] https://wiki.centos.org/Manuals/ReleaseNotes/CentOS8.2011#Yum_repo_file_and_repoid_changes
Change-Id: I2d67b3ed7b7c521bc755ec9a87365c9962a9eeff
Closes-Bug: #1907213
Closes-Bug: #1907826
Co-Authored-By: Radosław Piliszek <radoslaw.piliszek@gmail.com>
Depends-On: https://review.opendev.org/766211
Depends-On: https://review.opendev.org/767157
|
|
Change-Id: Id84d5a1b3c70c0260b85ed7c24aa7f1e007c12d6
Closes-Bug: 1848572
(cherry picked from commit 89372f0c5f312c222fe769a2aab8d1fce445dd84)
|
|
|
|
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
|
|
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
|
|
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
|
|
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
|
|
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
|
|
Change-Id: I75c460bda4c85016446f6a8df14e53806f8ef414
|
|
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
|
|
|
|
|
|
Depends-On: I880ef5dad6723de06da5dd8a424f7158d65b5a35
Depends-On: I52efd29791a230df1ce7e3acde4b7184aec34150
Change-Id: I47cd8ba5a14da3c76d5b1eb0b4c0cf0c729eb2ff
Partially-Implements: blueprint restructure-neutron-vpnaas
|
|
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
|
|
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
|
|
|
|
The variable is defined as "OTPS" and in the rest of the code
it is referred as "OPTS"
Change-Id: Ic8b2bab64afa4e54e8c69b2cd94a7d6cad361c3a
|
|
Closes-Bug: #1730629
Change-Id: Iae9ab6f3bba8185cf1bf53c3a5748e801404aeb7
Signed-off-by: Michal Nasiadka <michal.nasiadka@pl.ibm.com>
|
|
Closes-Bug: #1719775
Change-Id: I76803f0f81260129a242e31e81f4f956c5a44ef9
|
|
Change-Id: I56b9ef9ceb449d3fe6f2aa4cf856d6d1d7af7ee9
|
|
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
|
|
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
|
|
|
|
|
|
python-oslo-vmware was transitional package name
Change-Id: Ieb355e30fe7162c035f342fd5b0fb2573365f428
|
|
Change-Id: I31dd5054ea9bf341323f6d093c0667b98491cc2b
|
|
The plugin mechanism is meant to be for source install type only.
Change-Id: I1371a253236b09dc62ea91dce6d652e1c5603015
Closes-Bug: #1681345
|
|
centos based images have wrong label info,
these changes fix own image's name and build-date.
Change-Id: I1d13f8f386c8db12b5fbe5f8ecbbf9e3fbb4ba1c
Closes-Bug: #1680341
|
|
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
|
|
|
|
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>
|
|
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
|
|
|
|
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
|
|
include_header and include_footer parameter is already removed, remove
them in all Dockerfiles.
Add missing footer block.
Change-Id: I90da03eb9f95a3827361d5f5ede65fde7d6be2b3
|
|
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
|
|
Closes-bug: #1616387
Change-Id: Id97f88b9baa3d48d33ce120962450a374282d044
|
|
1. Install the missing vpnaas python module in neutron-server Dockerfile
2. Remove duplicated neutron-lbaas-common package from neutron-server,
since it is installed in neutron-base
3. Fix service plugin config, it's not vpn`ass` ;)) 'vpnass' ->
'neutron_vpnaas.services.vpn.plugin.VPNDriverPlugin' [1]
[1]:
https://github.com/openstack/neutron-vpnaas/blob/stable/newton/devstack/settings#L8
Change-Id: I5250b6875d96ef5df9cf39bce10ce072982aa80d
Closes-bug: #1625020
|
|
Change needed to add header blocks to all Dockerfiles, similar to the
base.
Use case is to easily run something before packages are installed, e.g.
to COPY a local rpm in that can be added to the package list.
Change-Id: I1bbfdf0b762da0a392aa8bf47781315b45377bee
Closes-Bug: 1618969
|
|
Change-Id: I5dbb030943abfa7eccc424859b694a508358c123
Partially-implements: blueprint third-party-plugin-support
Co-Authored-By: Michal (inc0) Jastrzebski <inc007@gmail.com>
Co-Authored-By: Paul Bourke <paul.bourke@oracle.com>
|
|
Previously, kolla did not support neutron lbaas functionality.
Only Lbaasv2 is supported in Mitaka. Additional information can
be found here:
http://docs.openstack.org/mitaka/networking-guide/adv-config-lbaas.html
Magnum uses Neutron Lbaas to provide high availability to COE API
and Etcd endpoints within a bay. Therefore, Neutron Lbaas is required
for Kolla to support Magnum.
Co-Authored-By: Serguei Bezverkhi <sbezverk@cisco.com>
Partial-Bug: #1551992
Change-Id: I05360b7c447c601fcb3c2b6b2a913ef5cc0f3a1b
|
|
Change-Id: I74aa68d809e9b38a605093abc4e2b8ca14335dee
Partial-Bug: #1546944
|
|
Partially implements: blueprint heka
Change-Id: I70e94f4ef7380c6f376a3066d7ddda042c703637
|
|
*** 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
|
|
Change-Id: I368f5b89fbfded0f173b97058061a03783ce1829
Closes-Bug: #1531883
|
|
There were some inconsistencies with pip install instructions
thoughout Kolla. We fix those here.
Additionally, we fix the virtualenv to properly use the site-packages
on the host if a library is not available in the venv.
Change-Id: Ib84d48e8826bb96060338b3fa0782620c98794a8
Related-Bug: #1524684
Closes-Bug: #1529434
|
|
Implements: blueprint neutron-third-party-plugins
Change-Id: I56c56bacd2f06c120b14b00c0b97dd4e39c0afc0
|
|
Added new option in kolla-build.conf
Change-Id: I45fe51966bcb59ea19d112281ba3d5a1ba091a56
Closes-Bug:#1514304
|
|
And fix the fallout.
Change-Id: Iccad3f4fdb0a6a7c14246df3408cae0425b833a5
|
|
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
|