[COE-22] Create CNI docker image and odlcni Yaml file to facilitate the deployment Created: 28/Nov/18  Updated: 29/Jan/19  Resolved: 29/Jan/19

Status: Resolved
Project: coe
Component/s: None
Affects Version/s: None
Fix Version/s: Neon

Type: Story Priority: Medium
Reporter: Mohamed ElSerngawy Assignee: Michael Vorburger
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Blocks
blocks COE-10 COE Deployment and Packaging for Kube... Open
blocks COE-30 Make CNI container image available on... Resolved
blocks COE-55 CSIT should use (locally built, not r... Confirmed

 Description   
  • Create a Docker file to create a docker image for odl cni binary & config
  • Create a Yaml file to easily deploy the odlcni with a running k8s cluster


 Comments   
Comment by Mohamed ElSerngawy [ 28/Nov/18 ]

https://git.opendaylight.org/gerrit/#/c/78105/

Comment by Michael Vorburger [ 29/Nov/18 ]

serngawy 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 COE-30 to have what this issue did run in CI on an ODL Jenkins incl. pushing it to a registry?

BTW: I'm too dumb to understand https://git.opendaylight.org/gerrit/#/c/78105/2/odlCNIPlugin/odlovs-cni/config/Readme.md - 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?

Comment by Mohamed ElSerngawy [ 30/Nov/18 ]

vorburger they kind of related COE-22/30. Yes, we can assume COE-22 for creating the dockerfile , k8s yaml and Test it. COE-30 for doing the jenkines job, ..etc.

Will update the Readme, its really bad. May I was in hurry

Comment by Michael Vorburger [ 17/Dec/18 ]

serngawy 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.

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?

 

Comment by Michael Vorburger [ 16/Jan/19 ]

> and have left some review comments in the c/78105; not +1/-1, more some questions and suggestions.

raised c/79579 implementing the build related suggestions.

More later in separate PRs.

Comment by Michael Vorburger [ 29/Jan/19 ]

Considering this Done now; the next step is COE-55 (to test, continuously, if it actually works; and fix it, if it doesn't).

Generated at Wed Feb 07 19:15:25 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.