Project

Profile

Help

Pulp RPM Roadmap » History » Sprint/Milestone 11

ttereshc, 02/19/2019 05:35 PM

1 1 ttereshc
# Pulp RPM Roadmap
2
3
~~~
4
This is a living document that is moving towards a long term plan to develop RPM plugin for Pulp 3.0 and beyond.
5
~~~
6
7
## Supported Content Types
8
9
### MVP
10
11
  - RPM \[#3199\]
12 6 ttereshc
  - SRPM \[#3199\]
13 1 ttereshc
  - Erratum \[#3201\]
14
15
### Post-MVP
16
17
  - DRPM
18
  - Distribution (kickstart tree)
19
  - Comps.xml content types (package group, environment, category, langpacks)
20
  - Yum repo metadata file
21 7 ttereshc
  - Modules
22 1 ttereshc
23
## Pulp RPM Plugin Use Cases
24
25
### MVP
26
27
##### Sync
28
29
  - Basic Sync
30
31
<!-- end list -->
32
33
  - As an authenticated user, I can sync a remote yum/dnf repository
34
35
<!-- end list -->
36
37
  - RPM \[#3202\]
38
  - SRPM \[#3202\]
39 4 ttereshc
  - Erratum \[#3202\]
40 1 ttereshc
41
<!-- end list -->
42
43
  - Sync types
44
45
<!-- end list -->
46
47
  - As a user, I can exactly mirror the content of a remote repository. \[provided by pulpcore\]
48
  - As a user, I can mirror the content of a remote repository with an additive behavior, so content is never removed locally. \[provided by pulpcore\]
49
50
<!-- end list -->
51
52
  - Download Behaviors
53
54
<!-- end list -->
55
56
  - As a user, my sync task does not fail just because one download failed. \[provided by pulpcore?\]
57 10 ttereshc
  - As a user, I can limit the number of concurrent downloads
58
  - As a user, I can sync content on-demand by setting a repository's download policy
59 1 ttereshc
60
##### Publish
61
62
  - As an authenticated user, I can publish a yum/dnf repository.
63
64
<!-- end list -->
65
66
  - RPM \[#3204\]
67
  - SRPM \[#3204\]
68 5 ttereshc
  - Erratum \[#3204\]
69 1 ttereshc
70
<!-- end list -->
71
72
  - As a user, I can specify relative path at which a repository will be served. \[provided by pulpcore\]
73 2 ttereshc
  - As a user, I can configure if a repository will be served over an SSL or a non-SSL connection. \[provided by pulpcore\] 
74
  - As user, I can sync from a yum/dnf repo published by Pulp. \[should be taken into account for any publish story\]
75 1 ttereshc
76 2 ttereshc
### Post-MVP
77
78
##### Sync
79
80
  - Basic Sync
81
82 1 ttereshc
<!-- end list -->
83
84 2 ttereshc
  - As an authenticated user, I can sync a remote yum/dnf repository
85 1 ttereshc
86
<!-- end list -->
87
88 2 ttereshc
  - DRPM
89
  - Distribution (kickstart tree)
90
  - Comps.xml content types (package group, environment, category, langpacks)
91
  - Yum repo metadata file
92 7 ttereshc
  - Modules
93 1 ttereshc
94 2 ttereshc
<!-- end list -->
95
96
  - Sync behaviors
97
98
<!-- end list -->
99
100
  - As a user, I can mirror only the most recent X versions that correspond to a particular rpm name.
101
  - As a user, I can force a full re-sync of a remote repository
102
  - As a user, I can sync from a mirrorlist feed.
103 3 ttereshc
  - As a user, I can sync from a metalink URL to avoid a replay attack from a malicious mirror. \[provided by pulpcore [3415](https://pulp.plan.io/issues/3415)\]
104 2 ttereshc
  - As a user, I can sync only signed packages (RPM/DRPM/SRPM)
105
  - As a user, I can have sync skip one or more content types, e.g. drpm, errata, etc
106 9 ttereshc
  - As a user, I can sync yum/dnf repository when only primary.xml is provided in repomd.xml
107 2 ttereshc
108
<!-- end list -->
109
110
  - Performance features
111
112
<!-- end list -->
113
114
  - As a user, my sync will skip most of its work if the repomd.xml revision number has not changed is equal to or older (lower) than the previously successfully synced one.
115
116
<!-- end list -->
117
118
  - As a user, my sync is not skipped if it's a first sync
119
  - As a user, my sync is not skipped if the importer configuration has changed since the last sync
120
  - As a user, my sync is not skipped if any content has been removed from the repository since the last sync
121
  - As a user, downloading of content starts quickly
122
123
<!-- end list -->
124
125
  - Sync types
126
127
<!-- end list -->
128
129
  - As a user, I can sync a kickstart tree from the same feed as other rpm/yum/dnf content.
130
131
<!-- end list -->
132
133
  - Download Behaviors
134
135
<!-- end list -->
136
137 8 bmbouter
  - As a user, I can limit the maximum speed of downloading in bytes / sec
138 2 ttereshc
  - As a user, I can specify the number of retries to be done before failing a given download
139
140
<!-- end list -->
141
142
  - Checksum Features
143
144
<!-- end list -->
145
146
  - As a user, I can sync a repository and have the files' checksums validated to ensure that no content is corrupt.
147
148
<!-- end list -->
149
150
  - GPG Signature Features
151
152
<!-- end list -->
153
154
  - As a user, I can verify that repo metadata has a valid signature. (would be a new feature)
155
  - As a user, I can specify a set of trusted GPG keys. Any packages that are not signed with one of these keys is not synced.
156
157
<!-- end list -->
158
159
  - Mirror List Support
160
161
<!-- end list -->
162
163
  - As a plugin writer I can configure mirror lists and rotate between the mirrors
164
165
<!-- end list -->
166
167
  - round robin support
168
  - nearest mirror support (GeoIP or ping times)
169
170
##### Publish
171
172
  - As an authenticated user, I can publish a yum/dnf repository.
173
174
<!-- end list -->
175
176
  - DRPM
177
  - Distribution (kickstart tree)
178
  - Comps.xml content types (package group, environment, category, langpacks)
179
  - Yum repo metadata file
180 7 ttereshc
  - Modules
181 2 ttereshc
182
<!-- end list -->
183
184 11 ttereshc
  - As a user, I can publish a repository incrementally (re-use the pre-existing metadata and only add additional units) \[not relevant in Pulp3 world?\]
185 2 ttereshc
  - As a user, I can force a full republish of a repository.
186
  - As a user, my publish will skip most of its work if no changes to a repository were made since last publish.
187
  - As a user, I can configure which checksum algorithm to use when creating metadata.
188
  - As a user, I can configure which checksum algorithm to use when creating updateinfo.xml.
189 7 ttereshc
  - Special publish for modules \[TBD\]
190 2 ttereshc
191
##### Export
192
193
  - As a user, I can export a repository or group of repositories to an ISO file (ISO 9660)
194
  - As a user, I can export a repository or group of repositories to a DVD / Blueray file (UDF aka. ISO/IEC 13346)
195
  - As a user, I can export a repository to a specified directory
196
  - As a user, I can export a repositories content that is associated or updated (errata) since a specific datetime( aka incremental?)
197
  - As a user, I can export RPM packages and errata as a set of JSON files
198
199
##### Upload
200
201
  - As an authenticated user, I can upload yum/dnf content types (not including Distribution)
202
  - As an authenticated user, I can upload a comps.xml file and have it parsed into its constituent content units (requires knowledge of the destination repo at creation time)
203
204
##### Copy
205
206
  - As a user, I can copy a content of a specific type from one repository to another repository
207
  - As a user, I can copy RPM packages and all their dependencies from one repository to another repository
208
  - As a user, I can copy an Erratum and all the RPM packages it references from one repository to another repository
209
  - As a user, I can copy an Erratum and all the RPM packages it references and all the RPM dependencies from one repository to another repository
210 11 ttereshc
  - Some content types create a new content unit in the destination repo instead of just copying, e.g. yum_repo_metadata_file
211 7 ttereshc
  - Special copy for modules \[TBD\]
212 2 ttereshc
213
#### Not much yet discussed use cases
214
215
##### Content Protection
216
217
  - As an authenticated user, I can use key based authentication to allow/disallow access to content served by the content app
218
  - As an authenticated user, I can use user/password based authentication to allow/disallow access to content served by the content app.
219
220
##### Applicability
221
222
  - As an authenticated user, I can trigger an applicability for a consumer.
223
  - As an authenticated user, I can trigger an applicability for a repository.
224
225
##### Rsync Distributor
226
227
  - As a user i can distribute rpm content using a remote server.
228
229
## Pulp 2 features not present in Pulp 3
230
231
  - "gpgkey" importer setting - only used by pulp-agent.
232
  - "generate_sqlite" - sqlite files are only used by yum as an optimization. DNF does not use them and has no plans to. Performance gains marginal.
233
234
<!-- end list -->
235
236
  - they are also used by the "repoview" feature which we will also leave out of 3.0. Making browseable publications will hopefully be solved in the core.
237
238
<!-- end list -->
239
240
  - As a user, I can have publish skip one or more content types, e.g. drpm, errata, etc
241
242
<!-- end list -->
243
244
  - We can't think of a use case for this. Maybe export of only RPMs and Errata, see export use case.