https://jira.opendaylight.org This file is an XML representation of an issue en-us 8.20.10 820010 22-06-2022 https://jira.opendaylight.org/browse/COE-56 coe <p><del><a href="https://jira.opendaylight.org/browse/COE-30" title="Make CNI container image available on the Quay.io container registry" class="issue-link" data-issue-key="COE-30"><del>COE-30</del></a></del> laid the technical ground work to make CNI container image available on the Quay.io container registry, and that is now done and "works" - but here is what is left to "productise" it for real use:</p> <p>1. <a href="https://quay.io/repository/opendaylight/" class="external-link" target="_blank" rel="nofollow noopener">https://quay.io/repository/opendaylight/</a> organization access should be granted to the other CoE committers and the Linux Foundation? I'm happy to add anyone who would like to be added - just email me your ID on Quay.io ...</p> <p>2. Some... Jenkins Job needs to trigger the webhook on Quay ... see comment in <del><a href="https://jira.opendaylight.org/browse/COE-30" title="Make CNI container image available on the Quay.io container registry" class="issue-link" data-issue-key="COE-30"><del>COE-30</del></a></del>. An easier alternative do this could be if instead of pointing it to <a href="https://git.opendaylight.org/gerrit/coe.git" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/coe.git</a> we pointed it to <a href="https://github.com/opendaylight/coe" class="external-link" target="_blank" rel="nofollow noopener">https://github.com/opendaylight/coe</a> and <a href="https://github.com/orgs/opendaylight/people" class="external-link" target="_blank" rel="nofollow noopener">https://github.com/orgs/opendaylight/people</a> would accept the built-in one-click Web Hook that it can set up which just works out of the box. Do note <a href="https://docs.quay.io/guides/github-read-only.html" class="external-link" target="_blank" rel="nofollow noopener">https://docs.quay.io/guides/github-read-only.html</a></p> <p>3. I'm not yet crystal clear how we'll publish different versions. Probably just tags matching ODL major release branches?</p> COE-56

COE Container builds automated on DockerHub

Improvement Medium Resolved Done Michael Vorburger Michael Vorburger Fri, 18 Jan 2019 22:54:24 +0000 Thu, 24 Jan 2019 18:55:56 +0000 Thu, 24 Jan 2019 18:50:59 +0000 Neon 0 2 <p>Dunno who can do this work... not me, but may be .. <a href="https://jira.opendaylight.org/secure/ViewProfile.jspa?name=ecelgp" class="user-hover" rel="ecelgp">ecelgp</a> or <a href="https://jira.opendaylight.org/secure/ViewProfile.jspa?name=dfarrell07" class="user-hover" rel="dfarrell07">dfarrell07</a> or <a href="https://jira.opendaylight.org/secure/ViewProfile.jspa?name=zxiiro" class="user-hover" rel="zxiiro">zxiiro</a> or <a href="https://jira.opendaylight.org/secure/ViewProfile.jspa?name=agrimberg" class="user-hover" rel="agrimberg">agrimberg</a> ? I'll raise an "official" ticket..</p> <p>FYI <a href="https://jira.opendaylight.org/secure/ViewProfile.jspa?name=shague" class="user-hover" rel="shague">shague</a> <a href="https://jira.opendaylight.org/secure/ViewProfile.jspa?name=k.faseela" class="user-hover" rel="k.faseela">k.faseela</a> <a href="https://jira.opendaylight.org/secure/ViewProfile.jspa?name=prem.sankar.g%40ericsson.com" class="user-hover" rel="prem.sankar.g@ericsson.com">prem.sankar.g@ericsson.com</a> <a href="https://jira.opendaylight.org/secure/ViewProfile.jspa?name=fkautz" class="user-hover" rel="fkautz">fkautz</a> ...</p> <p><span class="nobr"><a href="mailto:helpdesk@opendaylight.org" class="external-link" target="_blank" rel="nofollow noopener">helpdesk@opendaylight.org^{<img class="rendericon" src="https://jira.opendaylight.org/images/icons/mail_small.gif" height="12" width="13" align="absmiddle" alt="" border="0"/>}</a></span> ticket <a href="#67339" target="_blank" rel="noopener">opendaylight.org #67339</a></p> <p><a href="https://jira.opendaylight.org/secure/ViewProfile.jspa?name=vorburger" class="user-hover" rel="vorburger">vorburger</a> I'm not familiar with quay.io how is it different than Docker Hub?</p> <p>ODL currently pushes some things to Docker Hub if I recall. Is it possible to integrate with that rather than adding yet another platform?</p> <p><a href="https://jira.opendaylight.org/secure/ViewProfile.jspa?name=zxiiro" class="user-hover" rel="zxiiro">zxiiro</a> Quay.io is just another container registry. Contrary to Docker Hub, it (the registry itself, not just the container runtime itself) is also open source! Quay.io is the public instance of Quay, which Red Hat also bundles in FLOSS OKD and supported OpenShift. All hail Quay! We prefer it.</p> <p>But if this really blocks progress on this issue, I'm happy if you can instead set up a build in the same way as what I descirbed in <del><a href="https://jira.opendaylight.org/browse/COE-30" title="Make CNI container image available on the Quay.io container registry" class="issue-link" data-issue-key="COE-30"><del>COE-30</del></a></del> on DockerHub...I don't think I can myself, unless you want to add me to the <a href="https://hub.docker.com/u/opendaylight" class="external-link" target="_blank" rel="nofollow noopener">https://hub.docker.com/u/opendaylight</a> org? Looks dead BTW, all last updated a year ago.</p> <p>What's your docker hub ID? I can look into adding you tomorrow.</p> <p>The reason I'm more inclined to use Docker Hub is because several projects at LF are already using Docker Hub. From a support perspective we'd rather have a smaller list of registries being managed as otherwise there is an unlimited amount of services out there that LF will be expected to manage and maintain which at some point just gets out of hand if every project wants to use a different registry service. If we can make it work with Docker Hub let's try that route. If Docker Hub really doesn't work for us then we can discuss quay.io further.</p> <p>My understanding of container registries though are they should work similarly so I hope it doesn't matter which one is used.</p> <p>I pinged <a href="https://jira.opendaylight.org/secure/ViewProfile.jspa?name=vorburger" class="user-hover" rel="vorburger">vorburger</a> on IRC and granted him full administrative permissions on the new Docker Hub COE repo (<a href="https://cloud.docker.com/u/opendaylight/repository/docker/opendaylight/coe)." class="external-link" target="_blank" rel="nofollow noopener">https://cloud.docker.com/u/opendaylight/repository/docker/opendaylight/coe).</a></p> <p>Next step is to figure out the best way to hook CI into the repo. We could probably use the GitHub mirror to trigger builds as <a href="https://jira.opendaylight.org/secure/ViewProfile.jspa?name=vorburger" class="user-hover" rel="vorburger">vorburger</a> mentioned similarly for quay.io. This assumes COE doesn't need to run a Jenkins job to trigger the COE build. Is this a good assumption? Is it sufficient that Docker Hub does all the build work based on a Dockerfile in the project repo or is there more to this that we need to consider?</p> <p>&gt; What's your docker hub ID? I can look into adding you tomorrow.</p> <p>I'm <a href="https://hub.docker.com/u/vorburger" class="external-link" target="_blank" rel="nofollow noopener">https://hub.docker.com/u/vorburger</a></p> <p>Thanks for having created and given me access to <a href="https://cloud.docker.com/u/opendaylight/repository/docker/opendaylight/coe." class="external-link" target="_blank" rel="nofollow noopener">https://cloud.docker.com/u/opendaylight/repository/docker/opendaylight/coe.</a> But the COE project will be publishing several different containers (probably 3), could you therefore instead create coe-cni/ and coe-watcher/ and coe-odl/ ?</p> <p>&gt; This assumes COE doesn't need to run a Jenkins job to trigger the COE build. Is this a good assumption? Is it sufficient that Docker Hub does all the build work based on a Dockerfile in the project repo or is there more to this that we need to consider?</p> <p>Yup, that seems simplest and best to me as well, and is how I had managed to set it up for <a href="https://jira.opendaylight.org/browse/COE-30" title="Make CNI container image available on the Quay.io container registry" class="issue-link" data-issue-key="COE-30"><del>COE-30</del></a>, see the last comment, that should tell you how to... note coe.git/odlCNIPlugin/odlovs-cni/Dockerfile! I'm guessing that you can set up something very similar on Docker Hub? Coming to think of it, if you set up Docker Hub Linked Accounts on cloud.docker.com/u/opendaylight for github.com/opendaylight then we probably/perhaps don't even need to do anything else, as Docker Hub's set up wizard will probably magically install a Web Hook on GitHub!</p> <p>Though one thing to consider is how it will work for master vs stable branches - in an ideal world, hopefully Docker Hub can build per branch and tag the container images accordingly correctly all by itself.</p> <p><a href="https://jira.opendaylight.org/secure/ViewProfile.jspa?name=zxiiro" class="user-hover" rel="zxiiro">zxiiro</a> gave me the required permissions to help set this up, and we now have <a href="https://hub.docker.com/r/opendaylight/coe-cni" class="external-link" target="_blank" rel="nofollow noopener">https://hub.docker.com/r/opendaylight/coe-cni</a> (public) and <a href="https://cloud.docker.com/u/opendaylight/repository/docker/opendaylight/coe-cni" class="external-link" target="_blank" rel="nofollow noopener">https://cloud.docker.com/u/opendaylight/repository/docker/opendaylight/coe-cni</a> (private to configure the aforementioned).</p> <p>Done.</p> Blocks COE-10 COE-30 Development Epic Link COE-10 Rank 0|i03m7b: