Distribution 1.7 Project Page
Amy Lindburg edited this page Jun 29, 2015
·
5 revisions
- 05/26/2015 - Code Freeze
- 06/18/2015 - Release
Separation of engine code #447
To get the distribution related code split out of the engine, distribution will need a full client implementation which is capable of registry discovery and configuration through namespace as well as provide the necessary interface implementations for the engine.
- P1 Registry client using distribution interface #387 (https://github.com/dmcgowan/docker/tree/use-distribution-api)
- P2 Namespace Specification #303
- P2 Distribution client package (provides interface on top of registry client and namespace)
The registry should be able to operate as a pull-through mirroring cache. This means that if a pull operation cannot proceed locally due to missing content, the registry should be able to defer the request to an upstream registry.
(26 May 2015 - 5 Jun 2015)
- Separation of Engine Code
- Devise interfaces
- Preliminary work on separation of v2 code
- Evaluate v1 code future
- Agree on the concepts of #193
- Mirroring
- Mirror Proposal #459
(8 Jun 2015 - 19 Jun 2015)
- Mirroring implementation
- Separation of engine code continued
- v1 deprecation plan
- engine refactor discussion with engine team
- container format brainstorming
- manifest evolutions