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-22 coe <ul class="alternate" type="square"> <li>Create a Docker file to create a docker image for odl cni binary &amp; config</li> </ul> <ul class="alternate" type="square"> <li>Create a Yaml file to easily deploy the odlcni with a running k8s cluster</li> </ul> COE-22

Create CNI docker image and odlcni Yaml file to facilitate the deployment

Story Medium Resolved Done Michael Vorburger Mohamed ElSerngawy Wed, 28 Nov 2018 14:41:11 +0000 Tue, 29 Jan 2019 14:18:09 +0000 Tue, 29 Jan 2019 14:18:09 +0000 Neon 0 2 <p><a href="https://git.opendaylight.org/gerrit/#/c/78105/" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/#/c/78105/</a></p> <p><a href="https://jira.opendaylight.org/secure/ViewProfile.jspa?name=serngawy" class="user-hover" rel="serngawy">serngawy</a> shall we say that the "scope" of this issue that the goal of it is to be able to locally build the CNI container, and then have another issue <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> to have what this issue did run in CI on an ODL Jenkins incl. pushing it to a registry?</p> <p>BTW: I'm too dumb to understand <a href="https://git.opendaylight.org/gerrit/#/c/78105/2/odlCNIPlugin/odlovs-cni/config/Readme.md" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/#/c/78105/2/odlCNIPlugin/odlovs-cni/config/Readme.md</a> - can you update that, or simply clarify by comment here in this issue, what exact commands a noob (me) would have to type to build the container image?</p> <p><a href="https://jira.opendaylight.org/secure/ViewProfile.jspa?name=vorburger" class="user-hover" rel="vorburger">vorburger</a> they kind of related <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>/30. Yes, we can assume <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> for creating the dockerfile , k8s yaml and Test it. <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> for doing the jenkines job, ..etc.</p> <p>Will update the Readme, its really bad. May I was in hurry <img class="emoticon" src="https://jira.opendaylight.org/images/icons/emoticons/wink.png" height="16" width="16" align="absmiddle" alt="" border="0"/></p> <p><a href="https://jira.opendaylight.org/secure/ViewProfile.jspa?name=serngawy" class="user-hover" rel="serngawy">serngawy</a> thanks, now I was easily able to build the container image. I'm willing to help test it, and have left some review comments in the c/78105; not +1/-1, more some questions and suggestions.</p> <p>Also a question: This container has to run on the master(s) and all work minions nodes, right? But from what little I understand, unless you do that thing where you "taint" a master, pods don't actually run on the master, so how would we deploy it on master(s) then?</p> <p> </p> <p>&gt; and have left some review comments in the c/78105; not +1/-1, more some questions and suggestions.</p> <p>raised <a href="https://git.opendaylight.org/gerrit/#/c/79579" class="external-link" target="_blank" rel="nofollow noopener">c/79579</a> implementing the build related suggestions.</p> <p>More later in separate PRs.</p> <p>Considering this Done now; the next step is <a href="https://jira.opendaylight.org/browse/COE-55" title="CSIT should use (locally built, not remote fetched) containerized CNI (and later Watcher and ODL)" class="issue-link" data-issue-key="COE-55">COE-55</a> (to test, continuously, if it actually works; and fix it, if it doesn't).</p> Blocks COE-10 COE-30 COE-55 Development Rank 0|i03k3q:a Sprint COE Sprint 2