<div dir="ltr"><div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Mar 21, 2019 at 11:19 AM Javier Pena <<a href="mailto:jpena@redhat.com">jpena@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><br>
<br>
----- Original Message -----<br>
> Hi all,<br>
> <br>
> Over the last few weeks, mjturek and baha have been busy working on a set of<br>
> periodic jobs to build TripleO images for the ppc64le arch [1].<br>
> <br>
> The current missing step is publishing those images, and they are proposing<br>
> to push those to the RDO Registry instance at <a href="http://registry.rdoproject.org" rel="noreferrer" target="_blank">registry.rdoproject.org</a>, just<br>
> like we do with our TripleO images. I have tried to understand the<br>
> requirements, and would like to get input on the following topics:<br>
> <br>
> - Which namespace would these images use? Based on some logs [2] it looks<br>
> like they use tripleomaster-ppc64le, will they also push the images to that<br>
> namespace?<br></blockquote><div><br></div><div>I've been warning my folks this was coming.</div><div>If the PPC folks are using  tripleomaster-ppc64le, I would propose we update the x86_64 containers to be tripleo$release-x86_64</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
> - Could this create any conflicts with our current promotion pipeline?<br></blockquote><div><br></div><div>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</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
> - Is registry.rdo the right place for those images? I'm not familiar with the<br>
> next steps for ppc64le images after that (will it then go through a<br>
> promotion pipeline?), so that might affect.<br></blockquote><div><br></div><div>I think it's the right place to upload container images.</div><div>Overcloud images should be uploaded to <a href="https://images.rdoproject.org/master">https://images.rdoproject.org/master</a> , but we're going to have to account for arch type there too.  Increase space etc..</div><div><br></div><div>Finally they should build periodic jobs to build containers, overcloud images and test jobs that trigger off of <a href="https://trunk.rdoproject.org/centos7-master/tripleo-ci-testing/">https://trunk.rdoproject.org/centos7-master/tripleo-ci-testing/</a> and report results to the dlrn_api.</div><div><br></div><div>If things proceed well and everyone has access to debug info and logs I could see us adding ppc as promotion criteria.</div><div><br></div><div>Thanks for the update Javier!</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
> <br>
> If we decide to upload the images to images.rdo, we'll need to do the<br>
<br>
Correction: this should read "registry.rdo"<br>
<br>
> following:<br>
> <br>
> - Create the tripleomaster-ppc64le namespace in registry.rdo, following a<br>
> similar pattern to [3].<br>
> - Schedule a short registry downtime to increase its disk space, since it is<br>
> currently near its limit.<br>
> - Update the job at ci.centos to include the REGISTRY_PASSWORD environment<br>
> variable with the right token (see [4]). This is missing today, and causing<br>
> the job failure.<br>
> <br>
> Once we get input from all interested parties, we will decide on the next<br>
> steps.<br>
> <br>
> Thanks,<br>
> Javier<br>
> <br>
> <br>
> [1] -<br>
> <a href="https://ci.centos.org/job/tripleo-upstream-containers-build-master-ppc64le/" rel="noreferrer" target="_blank">https://ci.centos.org/job/tripleo-upstream-containers-build-master-ppc64le/</a><br>
> [2] -<br>
> <a href="https://centos.logs.rdoproject.org/tripleo-upstream-containers-build-master-ppc64le/422/logs/logs/000_FAILED_tripleoclient.log" rel="noreferrer" target="_blank">https://centos.logs.rdoproject.org/tripleo-upstream-containers-build-master-ppc64le/422/logs/logs/000_FAILED_tripleoclient.log</a><br>
> [3] - <a href="https://review.rdoproject.org/r/19063" rel="noreferrer" target="_blank">https://review.rdoproject.org/r/19063</a><br>
> [4] -<br>
> <a href="https://github.com/rdo-infra/review.rdoproject.org-config/blob/master/playbooks/tripleo-ci-periodic-base/containers-build.yaml#L12-L20" rel="noreferrer" target="_blank">https://github.com/rdo-infra/review.rdoproject.org-config/blob/master/playbooks/tripleo-ci-periodic-base/containers-build.yaml#L12-L20</a><br>
> _______________________________________________<br>
> dev mailing list<br>
> <a href="mailto:dev@lists.rdoproject.org" target="_blank">dev@lists.rdoproject.org</a><br>
> <a href="http://lists.rdoproject.org/mailman/listinfo/dev" rel="noreferrer" target="_blank">http://lists.rdoproject.org/mailman/listinfo/dev</a><br>
> <br>
> To unsubscribe: <a href="mailto:dev-unsubscribe@lists.rdoproject.org" target="_blank">dev-unsubscribe@lists.rdoproject.org</a><br>
> <br>
_______________________________________________<br>
dev mailing list<br>
<a href="mailto:dev@lists.rdoproject.org" target="_blank">dev@lists.rdoproject.org</a><br>
<a href="http://lists.rdoproject.org/mailman/listinfo/dev" rel="noreferrer" target="_blank">http://lists.rdoproject.org/mailman/listinfo/dev</a><br>
<br>
To unsubscribe: <a href="mailto:dev-unsubscribe@lists.rdoproject.org" target="_blank">dev-unsubscribe@lists.rdoproject.org</a><br>
</blockquote></div></div></div>