INIT Verb for CNI 1.1

[MikeZappa87]

We have come to the conclusion that INIT should be implemented in the CNI. To do this we need to do the following.

1. Come up with use cases
2. Propose a spec change (Inputs, Outputs, Error Codes ... )
3. Implement the change in libcni
4. Implement in reference plugins (if applicable)

[s1061123]

Just a note:

INIT (and DEINIT if we need) implementation requires lock mechanism in libcni or CNI plugin because libcni may be invoked twice or more at same time. To prevent race condition, we need some lock before INIT is invoked, somewhere, hence we may require

• add lock mechanism in libcni (i.e. implement lock in libcni side), or
• clearly mention to require lock mechanism in SPEC.md (for CNI plugins which uses INIT, i.e. implement lock in plugin side)

[MikeZappa87]

What if we call INIT when the network configuration is loaded by the container runtime? Prior the configuration being loaded, the runtime is not able to schedule containers

[squeed]

At this point, I think we should drop INIT from v1.1. There are enough other things in this release. Thoughts?

[MikeZappa87]

Let’s push it and get some feedback

[squeed]

This is still awaiting some kind of motivating story; we have nothing against it, but it needs a bit more possible use-cases.