b7e7d25308
This PS is created to : - roll back apache-airflow back to 1.10.5 - change default chart values from bionic to ubuntu_focal - save freshly generated config and policy files samples - in focal Dockerfile postgres client version is pubped up to v15 - change airflow docker image requirements from limited to fully frozen for shipyard-airflow project - adjusted requirements-direct.txt for shipyard_airflow - adjusted requirements-direct.txt for shipyard_client - regenerated requirements-frozen for both projects - fixed unit tests after upgrading click module - gen_all tox profile processing has been moved over to py8 gate because it requires focal zuul node to run - upgraded airskiff gate playbook to include latest treasuremap patchset with updated airskiff site admada manifests Change-Id: I47e44f5cfa19b2649697e7cc5a31557a6f4fcfea
3.4 KiB
Multiple Distro Support
This project builds images for Shipyard and Airflow components. Currently, it supports building images for ubuntu and opensuse ( leap 15.1 as base image).
By default, Ubuntu images are built and are published to public registry server. Recently support for publishing opensuse image has also been added.
If you need to build opensuse images locally, the following parameters can be passed to the make command in shipyard repository's root directory with images as target:
DISTRO: opensuse_15
DISTRO_BASE_IMAGE: "opensuse/leap:15.1"
DOCKER_REGISTRY: { your_docker_registry }
IMAGE_TAG: latest
IMAGE_NAME: airflow
PUSH_IMAGE: falseFollowing is an example in command format to build and publish images locally. Command is run in shipyard repository's root directory.
DISTRO=opensuse_15 DOCKER_REGISTRY={ your_docker_registry } IMAGE_NAME=airflow IMAGE_TAG=latest PUSH_IMAGE=true make images
Following parameters need to be passed as environment/shell variable to make command:
- DISTRO
-
parameter to identify distro specific Dockerfile, ubuntu_focal (Default)
- DISTRO_BASE_IMAGE
-
parameter to use different base image other than what's used in DISTRO specific Dockerfile (optional)
- DOCKER_REGISTRY
-
parameter to specify local/internal docker registry if need to publish image (optional), quay.io (Default)
- IMAGE_TAG
-
tag to be used for image built, untagged (Default)
- PUSH_IMAGE
-
flag to indicate if images needs to be pushed to a docker registry, false (Default)
This work is done as per approved spec multi_distro_support. Currently only image building logic is enhanced to support multiple distro.
Adding New Distro Support
To add support for building images for a new distro, following steps can be followed.
- Shipyard uses images for shipyard and airflow. So to build images for those components, two Dockerfiles are required, one for each component.
- Add distro specific Dockerfile for each component which will have steps to include necessary packages and run environment configuration. Use existing Dockerfile as sample to identify needed packages and environment information.
- New dockerfile can be named as Dockefile.{DISTRO} where DISTRO is expected to be distro identifier which is passed to makefile.
- Respective dockerfile should be placed in {shipyard_root}/images/airflow and {shipyard_root}/images/shipyard
- Add check, gate, and post jobs for building, testing and publishing images. These entries need to be added in {shipyard_root}/.zuul.yaml file. Please refer to existing zuul file for better existing opensuse support.
- Add any relevant information to this document.