Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Closed
wants to merge 1 commit into from

Conversation

AkihiroSuda
Copy link
Member

Signed-off-by: Akihiro Suda [email protected]

  • 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

This document roughly describes the roadmap of the BuildKit project.
We will be using GitHub Projects and GitHub Milestones for more detailed roadmap.

## Task 1 (2018Q1)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

😍

@tonistiigi
Copy link
Member

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
Copy link
Member Author

updated


## Task 2 (2018Q2-Q3)

- Promote BuildKit to the default moby-engine build backend
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@tonistiigi

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

Copy link
Member

@dnephin dnephin Nov 20, 2017

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

Copy link
Member

@dmcgowan dmcgowan Nov 22, 2017

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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
Copy link
Member Author

closing temporarily, as we might need more consideration

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants