Project

Profile

Help

Pulp Container Roadmap » History » Sprint/Milestone 2

ipanova@redhat.com, 02/21/2018 06:28 PM

1 1 ipanova@redhat.com
# Pulp Docker Roadmap
2 2 ipanova@redhat.com
3
~~~
4
This is a living document that is moving towards a long term plan to develop Docker plugin for Pulp 3.0 and beyond.
5
~~~
6
7
## Supported Content Types
8
9
### MVP
10
11
  - Image manifest schema1 and schema2
12
  - Manifest list
13
  - Blob
14
  - Tag
15
16
## Pulp Docker Plugin Use Cases
17
18
### MVP
19
20
##### Sync
21
22
  - As a user I can sync docker repo from docker registry  
23
    \* assumes registry is compliant v2 api specs  
24
    \* with token based auth or basic auth  
25
    \* specify \`feed\` and \`upstream_name\`
26
  - As a user I can sync from a docker repo published by Pulpand served by Crane
27
  - As a user, I can exactly mirror the content of a remote repository.
28
  - As a user, I can mirror the content of a remote repository with an additive behavior, so content is never removed locally.
29
30
**NOTE**: dropping enable_v1, enable_v2, mask_id options
31
32
h5 Publish
33
34
  - As a user I can create a publication of docker content  
35
    \* publication is consumable by Crane
36
  - As a user, I can specify relative path at which a repository will be served.
37
38
##### Addition of the content to the repo with deps
39
40
  - As a user I can add Manifest and all Blobs it references to the destination repo
41
  - As a user I can add Manifest List and all Manifests and Blobs it references to the destination repo
42
  - As a user I can add Tag and all its' associated content it references to the destination repo
43
44
##### Upload Artifacts( units are not created):
45
46
  - As a user I can upload  
47
    \* Manifest Lists  
48
    \* Image Manifests  
49
    \* Blobs  
50
    \* (no upload of tags)
51
52
##### Create Content Units from uploaded Artifacts:
53
54
h5.
55
56
### Post-MVP
57
58
##### Sync
59
60
  - As a user I can sync a registry by whitelisting tags ( Filtered Sync)
61
62
## What will be dropped in Pulp3
63
64
  - v1 API support. In Pulp3 we'll have just v2 api registry and corresponding v2 content types
65
  - v1/search. There is no v2/search so \`docker search\` for v2 content will not work. If upstream docker will add support for v2 docker content search by the time we deliver docker plugin for pulp3 we will reconsider and include the endpoint.