Commit Graph

7 Commits

Author SHA1 Message Date
Emilien Macchi 1a41c298cf Remove tripleoclient container from Kolla
This container was never needed or useful so far; let's remove it from
Kolla.

Depends-On: https://review.opendev.org/725349
Change-Id: I2c80080a5b2203c6b22c361f2b6126d65c0c50dc
2020-05-29 10:08:57 +02:00
Marcin Juszkiewicz 53443c5c71 Remove support for CentOS 7
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-04-15 09:32:06 +00:00
Christian Berendt 861f55fbfd Add block labels to all Dockerfiles
Change-Id: I9692dda817ef134d647247431565e1b58cf9da41
2020-03-01 17:25:58 +00:00
Alex Schultz 3e5d8e2653 Add python3 packages for RHEL systems
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-03-12 17:48:18 +00:00
Alex Schultz ae1322ec10 Use base_package_type
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
2019-01-17 08:23:41 -07:00
Bogdan Dobrelya 531d3dc0cd Use the base OS image for tripleoclient base
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>
2018-11-30 16:03:20 +01:00
Dan Prince e1b37f5444 Add a tripleoclient container
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
2018-09-06 09:33:57 -04:00