Hey Matthias, I think the existing images should be renamed to have "molecule" in their name. Since that is their entire purpose.
-Mike On Fri, May 15, 2020 at 3:03 AM Matthias Dellweg <mdell...@redhat.com> wrote: > Thank you for bringing this up. > With ci-base-image i mean images used (currently) in all travis pipelines, > including testing and releasing machinery. They are not meant for direct > user consumption. > The difference between this base image and the user-consumable > single-container image is however only a pip installation of pulp-packages > and copying of webserver config snippets. > > So do you think, those molecule images should be included in the naming > convention? Or should we just try not to produce collisions? > > On Thu, May 14, 2020 at 9:02 PM Mike DePaulo <mikedep...@redhat.com> > wrote: > >> >> >> On Thu, May 14, 2020 at 12:54 PM Matthias Dellweg <mdell...@redhat.com> >> wrote: >> >>> We have recently started a new repository calles pulp-oci-images that >>> should emit according to its name OCI compatible images with pulp >>> installed. >>> In the first go, this includes the single-container promoted though >>> this blog post [0]. >>> Soon to be added is the base container image that shall speed up our CI >>> [1]. >>> In the future, i envision a similar single-container solution based on >>> centos instead of fedora, >>> as well as ci base images based on centos having python3.6 installed. >>> Does anyone think, we even need different ci-images for pulp release >>> branches? >>> >> >> When you say "ci images", you mean images meant for user consumption? Or >> images only used in CI testing? >> >>> >>> The big question now is: How are we going to name and tag those images? >>> >>> The one from [0] is called "pulp/pulp-fedora31:latest". >>> We could go with that and add names like: >>> - "pulp/pulp-centos8:3.2" >>> installation of core version 3.2 with all compatible plugins on centos8 >>> - "pulp/pulp-ci-fedora32:latest" >>> - "pulp/pulp-ci-centos8:latest" >>> >> >> Remember that our current images like " >> https://quay.io/repository/pulp/pulp-ci-f31"; are only used for CI >> testing of upgrades. The description states: >> "Images of Pulp on Fedora 31, for CI testing of ansible-pulp performing >> upgrades." >> In fact, they are built via ansible molecule. >> >> -Mike >> >>> >>> BTW, the ci-base images can be built by using the same Conteinerfile >>> interrupted early. >>> (with --target in a multistage build) >>> >>> What do you think? >>> >>> [0] https://pulpproject.org/2020/03/15/pulp-fedora31-single-container/ >>> [1] >>> https://github.com/pulp/pulpcore/blob/master/.travis/Containerfile.ci_base >>> >>> _______________________________________________ >>> Pulp-dev mailing list >>> Pulp-dev@redhat.com >>> https://www.redhat.com/mailman/listinfo/pulp-dev >>> >>> >> >> -- >> >> Mike DePaulo >> >> He / Him / His >> >> Service Reliability Engineer, Pulp >> >> Red Hat <https://www.redhat.com/> >> >> IM: mikedep333 >> >> GPG: 51745404 >> <https://www.redhat.com/> >> > -- Mike DePaulo He / Him / His Service Reliability Engineer, Pulp Red Hat <https://www.redhat.com/> IM: mikedep333 GPG: 51745404 <https://www.redhat.com/>
_______________________________________________ Pulp-dev mailing list Pulp-dev@redhat.com https://www.redhat.com/mailman/listinfo/pulp-dev
