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-30 coe <p>Once we have a way to "manually" build the CNI container in <a href="https://jira.opendaylight.org/browse/COE-22" title="Create CNI docker image and odlcni Yaml file to facilitate the deployment " class="issue-link" data-issue-key="COE-22"><del>COE-22</del></a>, let the goal of this separate new issue be to build the CNI container image on Jenkins build and push it to a registry such as Docker Hub and/or <a href="https://quay.io" class="external-link" target="_blank" rel="nofollow noopener">https://quay.io</a> ...</p> COE-30

Make CNI container image available on the Quay.io container registry

Story Medium Resolved Done Michael Vorburger Michael Vorburger Thu, 29 Nov 2018 22:31:35 +0000 Thu, 24 Jan 2019 18:58:14 +0000 Fri, 18 Jan 2019 22:58:57 +0000 Neon 0 3 <p>Back in March there was an email thread "COE builds using docker system" about this which never went anywhere AFAIK...</p> <p><a href="https://git.opendaylight.org/gerrit/#/c/68911/" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/#/c/68911/</a> (not saying we'll use that, just for reference)</p> <p>In last week's TSC, <a href="https://jira.opendaylight.org/secure/ViewProfile.jspa?name=zxiiro" class="user-hover" rel="zxiiro">zxiiro</a> said that whenever we (CoE folks) were ready and really wanted this, to open a helpdesk ticket and he/someone would assist from the infra side. </p> <p><a href="https://jira.opendaylight.org/secure/ViewProfile.jspa?name=dfarrell07" class="user-hover" rel="dfarrell07">dfarrell07</a> in today's #opendaylight-integration IRC weekly meeting expressed interested in helping with this and/or <a href="https://jira.opendaylight.org/browse/COE-33" title="ODL with CoE containerized" class="issue-link" data-issue-key="COE-33">COE-33</a> ? He pointed to <a href="https://jira.opendaylight.org/browse/INTPAK-12" title="Add Jenkins jobs that do Packer builds, accepting vars as key:value params vs using var-files" class="issue-link" data-issue-key="INTPAK-12">INTPAK-12</a>.</p> <p>It's not something for tomorrow morning as I haven't even got to being able to build that image locally, and I first need to progress on where I actually use that image - but I'll get back.</p> <p>Note that the goal of this issue is to build and push a container image of some Go code, not an ODL distribution (and same for another container in <a href="https://jira.opendaylight.org/browse/COE-32" title="Watcher container image, build and push to repository" class="issue-link" data-issue-key="COE-32">COE-32</a>; but not <a href="https://jira.opendaylight.org/browse/COE-33" title="ODL with CoE containerized" class="issue-link" data-issue-key="COE-33">COE-33</a> which is an ODL image).</p> <p>OK, changed comment to right ticket <img class="emoticon" src="https://jira.opendaylight.org/images/icons/emoticons/smile.png" height="16" width="16" align="absmiddle" alt="" border="0"/></p> <p>I'll see how hard it is to get the POC container with <tt>odlovs-cni</tt> from <a href="https://jira.opendaylight.org/browse/COE-22" title="Create CNI docker image and odlcni Yaml file to facilitate the deployment " class="issue-link" data-issue-key="COE-22"><del>COE-22</del></a> (which BTW I'm not really even sure works yet) deployed on Quay.io ... I wonder if Go is available there, or if we need to do something like <a href="https://git.opendaylight.org/gerrit/#/c/78105/6/odlCNIPlugin/odlovs-cni/Dockerfile" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/#/c/78105/6/odlCNIPlugin/odlovs-cni/Dockerfile</a> ...</p> <p>watch (WIP) <a href="https://quay.io/repository/vorburger/test-opendaylight-coe-cni/" class="external-link" target="_blank" rel="nofollow noopener">https://quay.io/repository/vorburger/test-opendaylight-coe-cni/</a> (FYI <a href="https://quay.io/organization/opendaylight" class="external-link" target="_blank" rel="nofollow noopener">https://quay.io/organization/opendaylight</a> reserved for future use...)</p> <p>&gt; I wonder if Go is available there, or if we need to do something like <a href="https://git.opendaylight.org/gerrit/#/c/78105/6/odlCNIPlugin/odlovs-cni/Dockerfile" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/#/c/78105/6/odlCNIPlugin/odlovs-cni/Dockerfile</a> ...</p> <p>yeah, it builds (only) off a <tt>Dockerfile</tt> and can't launch a "native" (non-containerized) Go build from a <tt>Makefile</tt> or <tt>build.sh</tt> ...</p> <p>With my first 3-4 related changes required for this just merged, I've now set up a build trigger on <a href="https://quay.io/repository/opendaylight/opendaylight-coe-cni/" class="external-link" target="_blank" rel="nofollow noopener">https://quay.io/repository/opendaylight/opendaylight-coe-cni/</a> :</p> <ul> <li>Please enter the HTTP or SSH style URL used to clone your git repository : <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></li> <li>Please select the location of the Dockerfile to build when this trigger is invoked : /odlCNIPlugin/odlovs-cni/Dockerfile</li> <li>Please select the context for the Docker build : /odlCNIPlugin/odlovs-cni</li> </ul> <p>which then gave me this information:</p> <p>Please note: If the trigger continuously fails to build, it will be automatically disabled. It can be re-enabled from the build trigger list. In order to use this trigger, the following first requires action:</p> <p>1. You must give the following public key read access to the git repository:</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQC0gURKttJAy2B1Ohm56hLfGk9dQLcdYzjpq1xcNNot41aJF2m2NBw8Prn//TGCBGOsjLFO/T5pQFkd8Q85dhRKq8ZRHGPVxEEVvvZUv0mjG9LyLIZeY4CWTBoH38V+pJDoyDRtQKzlIBS4TeYkUdyB54k4LFLDCm0s7WEOFoY4rLigMqVcsWRSnEhBP5hi1I3u0LUbvLCv06TCi8p2ufxrWqY6m+w3sOa4MZgG5GmtMVjTAdmjCrGv3lMMO9RxTdxO1IyUTgqhP7+3kYLpMD/1ePwmOm/R9gjNH9A+Zx8sTNlIoELOoKVq2Xo3ycGv78bfzNEzoJHFh/2cVHDQ96mX</pre> </div></div> <p>2. You must set your repository to POST to the following URL to trigger a build: (For more information, <a href="http://docs.quay.io/guides/custom-trigger.html" class="external-link" target="_blank" rel="nofollow noopener">refer to the Custom Git Triggers documentation</a>.)</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>https://$token:D...R@quay.io/webhooks/push/trigger/9...e</pre> </div></div> <p>The ... are perhaps best not posted here, I'll send them by private email to anyone who asks for it, for <a href="https://jira.opendaylight.org/browse/COE-56" title="COE Container builds automated on DockerHub" class="issue-link" data-issue-key="COE-56"><del>COE-56</del></a>.</p> <p>I've deleted <a href="https://quay.io/repository/vorburger/test-opendaylight-coe-cni" class="external-link" target="_blank" rel="nofollow noopener">https://quay.io/repository/vorburger/test-opendaylight-coe-cni</a> again to avoid future confusion.</p> <p>Considering this done, but follow-up required in <a href="https://jira.opendaylight.org/browse/COE-56" title="COE Container builds automated on DockerHub" class="issue-link" data-issue-key="COE-56"><del>COE-56</del></a> (by others than me).</p> <p>Because <a href="https://jira.opendaylight.org/secure/ViewProfile.jspa?name=zxiiro" class="user-hover" rel="zxiiro">zxiiro</a> in <del><a href="https://jira.opendaylight.org/browse/COE-56" title="COE Container builds automated on DockerHub" class="issue-link" data-issue-key="COE-56"><del>COE-56</del></a></del> opted for using Docker Hub instead of Quay.io, I have deleted <a href="https://quay.io/repository/opendaylight/opendaylight-coe-cni/" class="external-link" target="_blank" rel="nofollow noopener">https://quay.io/repository/opendaylight/opendaylight-coe-cni/</a> again.</p> Blocks COE-10 COE-32 COE-33 COE-56 COE-55 COE-22 Relates INTPAK-12 Development Epic Link COE-10 Rank 0|i03k3q:c Sprint COE Sprint 2