Project

Profile

Help

Pulp Container Roadmap » History » Sprint/Milestone 23

ipanova@redhat.com, 08/15/2019 04:57 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 1 ipanova@redhat.com
7 18 ipanova@redhat.com
~~~
8
With Pulp as a docker registry you can:
9
10
- Mirror container image repositories hosted on Docker-hub, Google Container Registry, Quay.io, etc
11
- Reduce disk use space by mirroring container image repositories using the "on demand" policy. An image is only downloaded once it has been requested by a client.
12
- Use local filesystem or an object storage store such as S3 to host all the container images.
13
- Curate container images by whitelisting what is mirrored from an external repository.
14
- Curate container images by creating repository versions with a specific set of images.
15
- Create versioned repositories that can be promoted or rolled back with a single operation.
16
17
Pulp also has:
18
- tasking system that can be used to perform a variety of specialized work such as analysis of content. e.g. integration with clair-scanner
19
- a large community of users
20
- a commuity of plugin developers
21
~~~
22
23 22 ipanova@redhat.com
<span style="color: #458b74;">green</span>
24 1 ipanova@redhat.com
25
### MVP
26
27 22 ipanova@redhat.com
## Supported Content Types
28
29 16 ipanova@redhat.com
  - <span style="color: #458b74;">Image manifest schema2 and schema1</span>
30
  - {color: #458b74} Manifest list
31
  - {color: #458b74} Blob
32
  - {color: #458b74} Tag
33 2 ipanova@redhat.com
34 1 ipanova@redhat.com
## Pulp Docker Plugin Use Cases
35
36
### MVP
37
38 2 ipanova@redhat.com
##### Sync
39 8 ipanova@redhat.com
40 16 ipanova@redhat.com
  - <span style="color: #458b74;">As a user I can sync docker repo from docker registry</span>
41 1 ipanova@redhat.com
42
<!-- end list -->
43 8 ipanova@redhat.com
44 16 ipanova@redhat.com
  - {color: #458b74} assumes registry is compliant v2 api specs
45
  - {color: #458b74} with token based auth
46 21 ipanova@redhat.com
  - {color: #458b74} with basic auth
47 16 ipanova@redhat.com
  - {color: #458b74} specify \`feed\` and \`upstream_name\`
48 8 ipanova@redhat.com
49
<!-- end list -->
50 1 ipanova@redhat.com
51 19 ipanova@redhat.com
  - {color: #458b74} As a user I can sync a registry by whitelisting tags ( Filtered Sync)
52
  - {color: #458b74} As a user i can lazily fetch docker repo by specifying the download policy
53 23 ipanova@redhat.com
  - {color: #458b74} As a user I can sync a private docker repo from docker registry
54
  - {color: #458b74} As a user I can sync from a docker repo published by Pulp ( pulp2pulp3 and pulp3pulp3 sync)
55 17 ipanova@redhat.com
  - {color: #458b74} As a user, I can mirror the content of a remote repository with an additive behaviour, so content is never removed locally.
56 19 ipanova@redhat.com
  - As a user I can validate the size and the checksum of downloaded content against metadata ( #2625 #2624)
57 1 ipanova@redhat.com
58
**NOTE**: dropping enable_v1, enable_v2, mask_id options
59
60 8 ipanova@redhat.com
##### Publish
61
62 16 ipanova@redhat.com
  - {color: #458b74} As a user I can distribute docker content
63
  - {color: #458b74} As a user, I can specify publish_directory( i.e base_path) from which the content will be served( provided by pulp_core)
64 1 ipanova@redhat.com
  - As a user, I can specify repo-registry-id that will be used in the docker registry
65 13 ipanova@redhat.com
  - As a user i can specify redirect-url which will lead to the location the content is stored
66 1 ipanova@redhat.com
  - As a user I can specify whether i want to convert docker image schema2 to schema1( aka schema convertor, for older clients support)
67 20 ipanova@redhat.com
  - As a user I cam pull from docker registry that has auth mechanish  
68
    \* token auth  
69
    \* basic auth
70 8 ipanova@redhat.com
71 1 ipanova@redhat.com
As a result the above section should enable clients to perform \`docker/podman pull\`
72
73 21 ipanova@redhat.com
**NOTE** dropping protected option
74 1 ipanova@redhat.com
75 21 ipanova@redhat.com
##### Filtering
76
77 22 ipanova@redhat.com
  - {color: #458b74} As a user I can filter tags and images by digest, media_type, tag_name
78 21 ipanova@redhat.com
79 1 ipanova@redhat.com
##### Addition of the content to the repo with deps
80
81
  - As a user I can add Manifest and all Blobs it references to the destination repo
82
  - As a user I can add Manifest List and all Manifests and Blobs it references to the destination repo
83 2 ipanova@redhat.com
  - As a user I can add Tag and all its' associated content it references to the destination repo
84 1 ipanova@redhat.com
85 21 ipanova@redhat.com
##### Removal of the content from the repo with deps
86 1 ipanova@redhat.com
87 21 ipanova@redhat.com
  - As a user I can remove Manifest and all Blobs it references from the repo
88
  - As a user I can remove Manifest List and all Manifests and Blobs it references from the repo
89
  - As a user I can remove Tag and all its' associated content it references from the repo
90
91
**NOTE** units that are referenced by other units are not removed, unless force flag is specified
92
93
##### Force removal of the content from the repo with deps
94
95
  - As a user I can remove Manifest and all Blobs it references from the repo
96
  - As a user I can remove Manifest List and all Manifests and Blobs it references from the repo
97
  - As a user I can remove Tag and all its' associated content it references from the repo
98
99
##### Copy of the content form source repo to the dest repo with deps
100
101
  - As a user I can copy by digest Manifest and all Blobs it references from the source repo to the destination repo
102
  - As a user I can copy by digest Manifest List and all Manifests and Blobs it references from the source repo to the destination repo
103
  - As a user I can copy Tag by name and all its' associated content it references from the source repo to the destination repo
104
105
##### Adding/removing Tag via pulp api
106
107
  - As a user I can Tag an imagine in a repo
108
  - As a user I can Untag an imagine in a repo
109
  - As a user I can point existing Tag to a different image in a repo
110
111 1 ipanova@redhat.com
### Post-MVP 4.1+
112
113 21 ipanova@redhat.com
##### Sync
114
115
  - As a user, I can sync from a repository with Forein Layers and save them in pulp for disconnected env.
116
  - As a user, I can exactly mirror the content of a remote repository( mirror on sync)
117
118 1 ipanova@redhat.com
##### Publish
119
120
  - As a user I can distribute docker content using a remote server ( rsync exporter)
121 16 ipanova@redhat.com
122 22 ipanova@redhat.com
##### Docker push  
123
\* As a user, I can 'docker push' to a Pulp repository  
124
\* As a user I can 'docker tag' to a Pulp repository
125 19 ipanova@redhat.com
126 22 ipanova@redhat.com
##### Skopeo copy  
127
\* As a user I can use skopeo pulp transport to push images to Pulp container registry
128 16 ipanova@redhat.com
129 1 ipanova@redhat.com
##### Enable v2/catalog endpoint
130 10 ipanova@redhat.com
131 13 ipanova@redhat.com
##### Custom Live API (4.1+))
132 11 ipanova@redhat.com
133 7 ipanova@redhat.com
  - some dedicated storage for the metadata files ( remove the need of in-memory database)
134 13 ipanova@redhat.com
  - enable docker push functionality or provide this as a separate plugin/package
135 8 ipanova@redhat.com
136 3 ipanova@redhat.com
## What will be dropped in Pulp3
137 1 ipanova@redhat.com
138 2 ipanova@redhat.com
  - v1 API support. In Pulp3 we'll have just v2 api registry and corresponding v2 content types
139
  - 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.
140 1 ipanova@redhat.com
  - content protection. In Pulp3 docker repos will not support entitlement cert protection. ( option \`protected\` is dropped)
141 7 ipanova@redhat.com
  - export content into a tar file. It was possible to do so for v1 content.
142 13 ipanova@redhat.com
  - Crane is not longer used as a registry API. Pulp 3's ability to serve custom live APIs has made it possible for Crane's feature set to be incorporated into the pulp_docker plugin