[RFC] docs: add design, roadmap, bof notes

[AkihiroSuda]

Signed-off-by: Akihiro Suda suda.akihiro@lab.ntt.co.jp

• docs/roadmap.md

Based on BoF discussions, but ETA is just my 2 cents

• docs/misc/design-distribuetd.md

Based on BoF discussions, but maybe not accurate

• docs/misc/bof-2017-{losangeles,copenhagen.md}

I think @tiborvass has more accurate notes, so I'd like to replace my broken notes with his ones if he allows 😄

(For Los Angeles summit, I have a copy of @tiborvass 's note, but not for Copenhagen summit)

@tonistiigi @tiborvass @vdemeester @dnephin @thaJeztah

[vdemeester]

😍

[tonistiigi]

Maybe the raw bof notes are better in a public google doc where they can be revised, commented on, and maybe separate points turned into issues. We could link to that doc from here.

[AkihiroSuda]

updated

[AkihiroSuda]

@tonistiigi

I guess this task requires integrating the containerd image store to moby-engine first?

[dnephin]

Isn't it possible to export images to the current engine image storage using docker load ?

[tonistiigi]

@dnephin It is, but it has quite a significant performance penalty because data needs to be copied.

@AkihiroSuda I agree. Should it get very delayed we could consider implementing the snapshotter dependency with moby storage drivers but let's try the correct way first.

[AkihiroSuda]

@mlaventure Do you know when we will integrate the containerd image store & snapshot subsystem to Moby-engine?

[mlaventure]

I do not, @stevvooe & @dmcgowan would have a better idea.

[dmcgowan]

The plan is still that work starts early next year. The snapshotters will be available to use before then. Something to consider is that having integration with the containerd snapshotter does not necessarily mean the storage drivers will not continue to be used. I don't know what the plan will be but it might be wise to plan on using the snapshotters and having a way to export into an existing Docker storage driver.

[AkihiroSuda]

closing temporarily, as we might need more consideration