Buildah and Podman will replace Docker.
This patch will be used by tripleoclient when running:
$ openstack overcloud container image build --use-buildah
When using Buildah, the kolla_builder will, in that order:
1) Generate container templates but not actually build the images.
The directories are generated by kolla-build and containers files
like Dockerfiles and such.
2) Generate container dependencies and build a dictionary, later used by
the new BuildahBuilder.
In this patch, we introduce a Class for builders. For now, we only have
BuildahBuilder but later we will refactor kolla_builder.
The BuildahBuilder has in charge of:
1) Build containers using "buildah bud". This command is used because
Kolla uses Dockerfiles to build images. Each image build is logged in
the directory that contains the Dockerfile.
During the build, logging displays the container that is being built
and also the buildah command that is used.
The image layers that don't have childs are multi-threaded to
accelerate the build. We don't go over 8 builds at the same time
otherwise Buildah struggles with the locks too hard.
We also setup a timeout of 30 minutes for the workers to report back.
For example:
base
└─openstack-base
├─nova-base
│ ├─nova-api
│ └─nova-conductor
└─neutron-base
└─neutron-dhcp
└─multipathd
└─crond
The builder will first build "base" then:
- build openstack-base, multipathd and crond in same time.
- build nova-base and neutron-base in same time
- build nova-api, nova-conductor in same time
- etc
2) Push containers to a Docker registry. We'll support more than Docker
registries, but later.
Note: All commands are executed using processutils from oslo_concurrency
which is pretty and rock solid.
Note2: kolla_builder will be refactored to use the new Builder class.
This patch is an initial support for Buildah, improvements will come
later.
Co-Authored-By: Alex Schultz <aschultz@redhat.com>
Co-Authored-By: Christophe Fontaine <cfontain@redhat.com>
blueprint podman-support
Change-Id: Ieff41a5f84456530b4621218b01f3b546cd867bf