| Age | Commit message (Collapse) | Author | Files | Lines |
|
Python changes:
- limit pip to 20.x as this is last version working on both Python 2 and 3.
- cap 'setuptools' to be older than 58 to have use_2to3 functionality
(fixes 'anyjson' installation)
- upgrade pip in 'elasticsearch-curator' image to get it built on CentOS 7
Unbuildable images:
- 'bifrost-base' under CentOS 8
(Error: Cannot find a valid baseurl for repo: epel)
- 'monasca-grafana' under CentOS 7/8
- 'sensu-client' under CentOS 7
(aws-eventstream requires Ruby version >= 2.3)
- dropped *-upgrade CI jobs as Stein is EOL
- pin 'qpid-proton-c' package for CentOS 7 to not install EPEL one
(cinder-volume, openstack-base and tripleoclient)
- bump 'libvirt-python' in 'masakari-monitors' to 7.10.0
(newer branches install package from distribution but CentOS 7 lacks
it)
- pin 'unf_ext' gem in Sensu images as CentOS 7 lacks Ruby 2.2+
(fixed sensu-server)
- install 'ca-certificates' for newer Let's Encrypt certificates support
(so we can fetch upper-constraints)
- make Zuul fetch openstack/requirements project files
(make 'openstack-base' pass) (like 2nd fix)
Co-Authored-by: Pierre Riteau <pierre@stackhpc.com>
Closes-Bug: #1943617
Depends-On: https://review.opendev.org/c/openstack/kolla-ansible/+/826464
Change-Id: I8ee32e53cda581493b2a4bb73ca72ab05014b9d4
|
|
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
|
|
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
|
|
Building from openstack-base brings a lot of unneeded overhead into the
end container. We only need a minimal setup, so let's rely on
dependencies of the python-tripleo package instead of explicitly
pulling in world from openstack-base. That saves space, and reduces
potential attacks vectors and CVEs to maintain for the tripleoclient
container.
Related: blueprint zero-footprint
Change-Id: If70351aac67bf62274a068cb4ebfe9c5270da5ae
Signed-off-by: Bogdan Dobrelya <bdobreli@redhat.com>
|
|
We'd like to use this container both interactively (for
ad-hoc commands) and also to be able to generate
Ansible (via the undercloud/all-in-one installers) for TripleO.
Partially-implements: https://blueprints.launchpad.net/tripleo/+spec/zero-footprint
Change-Id: Ia4d7fdcb9c96d76e191dcc1a46be095b37189b3e
|