Since Rally has virtualenv in requirements, and is using contraints - it's
trying to downgrade virtualenv from inside a virtualenv.
Let's try to install proper version of packages in openstack-base.
Closes-Bug: #1900419
Change-Id: I2a1e2b6661fd4b62648756416e6147b604dda686
(cherry picked from commit b1709a87ed)
'messaging-rabbitmq' and 'opstools' are enabled by RDO
delorean-deps.repo file
'influxdb' was also enabled
Depends-On: https://review.opendev.org/728687
Change-Id: Ibb0a7edc9e5632c1b89a7d52601f55a223b49dfb
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
INFO:kolla.common.utils.openstack-base: File "setup.py", line 159, in run
INFO:kolla.common.utils.openstack-base: raise Exception("ERROR: The 'make' utility is missing from PATH")
INFO:kolla.common.utils.openstack-base: Exception: ERROR: The 'make' utility is missing from PATH
INFO:kolla.common.utils.openstack-base: ----------------------------------------
INFO:kolla.common.utils.openstack-base:
INFO:kolla.common.utils.openstack-base: ERROR: Failed building wheel for PyNaCl
Change-Id: Id8be6cc8f98207bc9ebf546c55d34cf9c6360cd7
pyScss used by Horizon fails to work with setuptools > 46 version.
It's last release was in 2016 so probably no one fix it.
Let make sure that we get older version of setuptools.
Broken due to https://bugs.launchpad.net/kolla/+bug/1866961
Change-Id: I2a3fa657a3e1a9b8b0acb0b50bd4f3e98078f4ff
The disable_extra_repos macro accepts a list as its only argument. We
were calling it like this to disable EPEL:
disable_extra_repos('epel')
The macro interpreted this as a request to disable three repos, e, p, l.
Thanks Python! Type validation to be improved separately.
Additionally, on CentOS 8 the EPEL repository was not included in the
repository mapping file, repos.yaml. There is also another EPEL
repository on CentOS 8, epel-modular, which is enabled by default after
installing epel-release.
This change adds mappings for epel and epel-modular repos to repos.yaml,
and fixes the disabling of epel in the base image, as well as disabling
epel-modular.
There are some cases where EPEL is still used (it seemed a bit too
easy...), and the repository has been enabled for these images:
* bifrost-base (nginx)
* ironic-conductor (C7 only, shellinabox)
* freezer-base (C7 only, trickle)
* gnocchi-base (C8 binary only, python3-boto3)
* mariadb (pv)
* mongodb (C7 only, mongodb)
* nova-spicehtml5proxy (C7 only, spice-html5)
* telegraf (C7 only, python2-pip)
A few other things were changed:
* ironic-conductor does not require the ceph repo
* python3-pika is no longer installed in the openstack-base image
Related: blueprint remove-epel
Change-Id: I3761825239dfc462072383cde6276c4fb3e1bf12
Adds support to the base and openstack-base images for CentOS 8.
These images have been removed from the list of unbuildable images, and
replaced with all dependent images.
Change-Id: I18fba8a5c2f99b700990cbf41c76077a1ec2408a
Partially-Implements: blueprint centos-rhel-8
This partially reverts commit 73f9b5e47c.
It was fixed in RDO on the packaging side:
https://review.rdoproject.org/r/#/c/22745/
Ubuntu packages do not have a dependency on python3-pyngus, so that
package has been left in place.
Change-Id: Iea8fd1ac30400c67f76aec6d37ee7614f9c51770
sqlalchemy-collectd was added in
I2bcaa44c184bb24e5caeeb8d204dda627de59c91, however it also must
be installed alongside anywhere that python-sqlalchemy is installed
since it provides an in-process plugin that transmits metrics
to a remote collectd daemon.
Also adds the python3 version of the package to the py3 version of
the collecd/Dockerfile.j2.
Note this is currently an *RPM only* package, and as of this
commit is not yet availble for other packaging systems.
Change-Id: If598da717653a383a2d3b3373c56517f8bca832f
backport: Stein
During the switch to Stein UCA, we did not switch all packages to python
3 for Debian/Ubuntu binary images. This change switches some more of
those packages.
Change-Id: I0bff21384d88ea678608392de2db1ba418c96665
Co-Authored-By: Marcin Juszkiewicz <marcin.juszkiewicz@linaro.org>
Commit 43b74ccc15 enabled use of Python 3
based packages but not switched to use Python 3.
Some of images still contain Python 2. There are two reasons:
- Ceph (ceph-common depends on Py2)
- python3-ldappool on Ubuntu 18.04
In Ceph situation Py3 packages were added. For second one we can not do
anything - Py2 dependency got dropped in Ubuntu 18.10 version.
Removed neutron-server-plugin-networking-infoblox due to being not
maintained. Once https://review.opendev.org/#/c/657578/ get merged
someone may revert that part.
Implements: blueprint debian-ubuntu-python3
Depends-on: Ie2a1077f7def0743f1403341985e2109aa490026
Change-Id: Ibfe0c2b8be98db56c61f74fb0247488ab3749ef4
Providing tools like "ps", "pgrep" and related is interesting since
it helps debugging a container in some cases.
It is also useful for healthchecks in case we want to fetch running
service PID and use it in another command, like "lsof".
Change-Id: I91b1c407caa6b03ae522e649592300f9eddfc07e
- python*-oslo-upgradecheck was being installed in a number of different *-base containers that I checked
Change-Id: Iddd8a191e5523ec048dff324993abadcfc020132
Buster is at freeze phase so safe to update and use. Will give us
Python 3 based OpenStack packages (usually release delayed).
Change-Id: I48c2d252a834716f1bcf10b18f2d32fe541e8137
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
RHEL7 derived distros use Python 2.7
RHEL8 uses Python 3.6
Ubuntu 18.04 uses Python 3.6, but we haven't enabled it yet.
Debian:buster uses Python 3.7, but we haven't enabled it yet.
We have several places in code where "/lib/pythonX.Y/site-packages"
is used so we need to know value of X.Y rather than py2/py3 switch.
How to check for Python 2:
{% if distro_python_version == '2.7' %}
Breaks: Iad6b70b433a0dd1b0f8ae6790fd280594517661a
Change-Id: Ie24f109af19ae0438c21e0d43cb3cc947812b4ce
Last release of pika-pool was in 2015 and targetted pika 0.10 release:
INFO:kolla.common.utils.openstack-base:pika-pool 0.1.3 has requirement pika<0.11,>=0.9, but you'll have pika 0.13.0 which is incompatible.
None of our images requires pika-pool (tested by dropping it and then
building all images).
Change-Id: I7204aab66a252e0fdc3c0eebf5232903340a7e5d
these are containers, we should not have X11 display libraries
installed in base containers. If they are being pulled in via
packages those chains of dependencies should be looked at closely
and pruned as they have no real use on container images.
Change-Id: I19000564445254ba4d168f24deef6a901391d2e2
Remove the packages that are already pulled implicitly as a dependency.
A shorter package list should make it more manageable.
Change-Id: I690de645436065eee298a455221be8a6a0ae8083
according to https://pypi.org/project/msgpack-python/ it's
deprecated and should use msgpack.
and this is supported by looking at a build source container
image and noting that pip lists
msgpack 0.6.0
msgpack-python 0.5.6
also msgpack is pulled in via dependency of oslo.serialization
We should be able to rely on it coming in via that dependency
automaticly
Change-Id: Id2706b3b38e57daf1166f98a59dc3ecd30fd4fa7
Now with Ubuntu 'bionic' being used we can drop
libmysqlclient-compat-dev package use and just go with mariadb packages
directly.
Also move to OpenSSL 1.1 for both distributions.
Change-Id: I147385a3da15878121c0a436b5c26ba100e9802d
pycrypto has mostly replaced by python2-cryptography
In patch I77b5210cd6e63aa3b01aa2b5b3372dd50009b9ad
the source entries were all flipped to prefer cryptography instead
of pycrypto, let's drop python2-crypto and let any remaining packages
that do need it pull it in explicitly
Change-Id: Ie0f426fbe396ed9b5a3b86406c64e12e87dd81a7
this package is a WSGI helper for caching, not in openstack
requirements, and only referenced in refstack and airship.
If it's used by any packages that I missed it should be implicitly
installed where used/needed instead of in openstack-base and not used
Change-Id: Iafd6678846e7c495cc96a6d3a7681d70a4bf8171
these containers should not need unittest support packages
in general, tempest may need one of these but that should be
installed as needed not for all container images.
- testtools - introduced in
- unittest2 - introduced in Ia3a9756c58f0ead3b20e435f1d1546408f4a8b36
- zake - introduced in Ie05ba975bc2f88cd9ee896aafc60171d6ca8d10b
- fixtures - introduced in Ia3a9756c58f0ead3b20e435f1d1546408f4a8b36
Change-Id: Ic2325afc6ce3ee9f8a8c03ad19050809255df2f5
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
Mysql-python is a deprecated package and fails to build currently.
Make use of mysqlclient as is a fork of mysql-python with many bug
fixes a python3 support.
percona xtrabackup doenst work with mariadb 10.3,
replaces to use mariadb-backup tool.
https://jira.mariadb.org/browse/MDEV-15774
Change-Id: Icefe3a77fb12d57c869521000d458e3f58435374
These are some of the obvious candidates that were installed 10 times
or more in the different images.
Change-Id: I3ca2a3855689ffa64aef7ee46e58dc4b0dac77d3
These packages produce a warning during the installation, we should
switch to their new names, usually to be specific about their use of
python2.
Change-Id: I0a80e822f64222d9a32aabd1fd834bcf794d6320
python2-msgpack is python2 only, is from EPEL, and is ancient.
Use a propery tested and validated version of msgpack.
Closes-Bug: #1704894
Co-Authored-By: Jeffrey Zhang <jeffrey.zhang@99cloud.net>
Change-Id: I3b33f7a9ad48e2a06ede1f79426231d720b851ae
For rhel/centos/oraclelinux there were 2 yum install
sections, collapse/folded the 3 packages from that section
into the other blocks in sorted order
Change-Id: I8a3d212314891635509aeeb346998ace713feefa
openstack-base image includes a list of dependencies to be
installed in the image. However some of the packages in this
list seems not to be used by any or very few OpenStack services
according to the info found in codesearch.
This patch removes some python packages from this list as we
are in the process of cleaning dependencies in RDO.
Change-Id: I209b16cfd7dff6ce20bc2417a6079fb8597f6774
Closes-Bug: #1766493
RDO packaged mariadb recieves far more testing and qualification
than any other mariadb package on CentOS. Lets use that instead
of a hard-pinned old version of mariadb from mariadb.org.
This patch also upgrade MariaDB from 10.0 to 10.1.20 for
RHEL/CentOS/Oracle Linux.
Depends-On: I8374ac2219ad7880970cd789727d01af7cac1077
Depends-On: Ia2acb09e877a586243fc1acb49d8d140cf27d7b5
Co-Authored-By: Xinliang Liu <xinliang.liu@linaro.org>
Change-Id: I071362fc1b8d60199a77e2fe0475d2b4c3b5341b
Note that latest version of python-cffi is provided
from CentOS base and is python-cffi instead of python2-cffi.
According to CentOS/RDO packaging rules, all python2-XXX
packages has a provides on python-XXX, so when installing
it, python-XXX should always be used as it will install the
right package.
Change-Id: Ie30901c64993a6031278812e5072046a50371b3d
Closes-Bug: #1728915
OpenSSL 1.1 is not fully source compatible with 1.0.x so
python-qpid-proton fails to build for Debian (which uses OpenSSL 1.1 as
default).
Installing development package for 1.0.2 gets it back to buildable
state.
Python-qpid-proton is fixed upstream but no release was made yet.
Closes-Bug: #1714218
Change-Id: I731fe92410f340105e1a53372d33fdbb4798eaa3