[rdo-dev] [infra][tripleoci] ppc64le container images in registry.rdoproject.org

[Wesley Hayutin]

On Thu, Mar 21, 2019 at 11:19 AM Javier Pena <jpena at redhat.com> wrote:

>
>
> ----- Original Message -----
> > Hi all,
> >
> > Over the last few weeks, mjturek and baha have been busy working on a
> set of
> > periodic jobs to build TripleO images for the ppc64le arch [1].
> >
> > The current missing step is publishing those images, and they are
> proposing
> > to push those to the RDO Registry instance at registry.rdoproject.org,
> just
> > like we do with our TripleO images. I have tried to understand the
> > requirements, and would like to get input on the following topics:
> >
> > - Which namespace would these images use? Based on some logs [2] it looks
> > like they use tripleomaster-ppc64le, will they also push the images to
> that
> > namespace?
>

I've been warning my folks this was coming.
If the PPC folks are using  tripleomaster-ppc64le, I would propose we
update the x86_64 containers to be tripleo$release-x86_64


> > - Could this create any conflicts with our current promotion pipeline?
>

Only if we start to overload the rdo registry, which has happened in the
past. I don't see how the two would conflict otherwise


> > - Is registry.rdo the right place for those images? I'm not familiar
> with the
> > next steps for ppc64le images after that (will it then go through a
> > promotion pipeline?), so that might affect.
>

I think it's the right place to upload container images.
Overcloud images should be uploaded to https://images.rdoproject.org/master ,
but we're going to have to account for arch type there too.  Increase space
etc..

Finally they should build periodic jobs to build containers, overcloud
images and test jobs that trigger off of
https://trunk.rdoproject.org/centos7-master/tripleo-ci-testing/ and report
results to the dlrn_api.

If things proceed well and everyone has access to debug info and logs I
could see us adding ppc as promotion criteria.

Thanks for the update Javier!


> >
> > If we decide to upload the images to images.rdo, we'll need to do the
>
> Correction: this should read "registry.rdo"
>
> > following:
> >
> > - Create the tripleomaster-ppc64le namespace in registry.rdo, following a
> > similar pattern to [3].
> > - Schedule a short registry downtime to increase its disk space, since
> it is
> > currently near its limit.
> > - Update the job at ci.centos to include the REGISTRY_PASSWORD
> environment
> > variable with the right token (see [4]). This is missing today, and
> causing
> > the job failure.
> >
> > Once we get input from all interested parties, we will decide on the next
> > steps.
> >
> > Thanks,
> > Javier
> >
> >
> > [1] -
> >
> https://ci.centos.org/job/tripleo-upstream-containers-build-master-ppc64le/
> > [2] -
> >
> https://centos.logs.rdoproject.org/tripleo-upstream-containers-build-master-ppc64le/422/logs/logs/000_FAILED_tripleoclient.log
> > [3] - https://review.rdoproject.org/r/19063
> > [4] -
> >
> https://github.com/rdo-infra/review.rdoproject.org-config/blob/master/playbooks/tripleo-ci-periodic-base/containers-build.yaml#L12-L20
> > _______________________________________________
> > dev mailing list
> > dev at lists.rdoproject.org
> > http://lists.rdoproject.org/mailman/listinfo/dev
> >
> > To unsubscribe: dev-unsubscribe at lists.rdoproject.org
> >
> _______________________________________________
> dev mailing list
> dev at lists.rdoproject.org
> http://lists.rdoproject.org/mailman/listinfo/dev
>
> To unsubscribe: dev-unsubscribe at lists.rdoproject.org
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rdoproject.org/pipermail/dev/attachments/20190321/e7db86b4/attachment-0001.html>