openstack/kolla.git - Unnamed repository; edit this file 'description' to name the repository.

Age	Commit message (Collapse)	Author	Files	Lines
2020-05-29	Remove tripleoclient container from Kolla	Emilien Macchi	2	-58/+0
	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-04-15	Remove support for CentOS 7	Marcin Juszkiewicz	1	-13/+2
	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-01	Add block labels to all Dockerfiles	Christian Berendt	1	-0/+2
	Change-Id: I9692dda817ef134d647247431565e1b58cf9da41
2019-03-12	Add python3 packages for RHEL systems	Alex Schultz	1	-8/+17
	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-01-17	Use base_package_type	Alex Schultz	1	-1/+1
	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-11-30	Use the base OS image for tripleoclient base	Bogdan Dobrelya	1	-1/+1
	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-09-06	Add a tripleoclient container	Dan Prince	2	-0/+58
	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