Project

Profile

Help

Pulp RPM Roadmap » History » Sprint/Milestone 7

ttereshc, 04/20/2018 04:32 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
58
##### Publish
59
60
  - As an authenticated user, I can publish a yum/dnf repository.
61
62
<!-- end list -->
63
64
  - RPM \[#3204\]
65
  - SRPM \[#3204\]
66 5 ttereshc
  - Erratum \[#3204\]
67 1 ttereshc
68
<!-- end list -->
69
70
  - As a user, I can specify relative path at which a repository will be served. \[provided by pulpcore\]
71 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\] 
72
  - As user, I can sync from a yum/dnf repo published by Pulp. \[should be taken into account for any publish story\]
73 1 ttereshc
74 2 ttereshc
### Post-MVP
75
76
##### Sync
77
78
  - Basic Sync
79
80 1 ttereshc
<!-- end list -->
81
82 2 ttereshc
  - As an authenticated user, I can sync a remote yum/dnf repository
83 1 ttereshc
84
<!-- end list -->
85
86 2 ttereshc
  - DRPM
87
  - Distribution (kickstart tree)
88
  - Comps.xml content types (package group, environment, category, langpacks)
89
  - Yum repo metadata file
90 7 ttereshc
  - Modules
91 1 ttereshc
92 2 ttereshc
<!-- end list -->
93
94
  - Sync behaviors
95
96
<!-- end list -->
97
98
  - As a user, I can mirror only the most recent X versions that correspond to a particular rpm name.
99
  - As a user, I can force a full re-sync of a remote repository
100
  - As a user, I can sync from a mirrorlist feed.
101 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)\]
102 2 ttereshc
  - As a user, I can sync only signed packages (RPM/DRPM/SRPM)
103
  - As a user, I can have sync skip one or more content types, e.g. drpm, errata, etc
104
105
<!-- end list -->
106
107
  - Performance features
108
109
<!-- end list -->
110
111
  - 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.
112
113
<!-- end list -->
114
115
  - As a user, my sync is not skipped if it's a first sync
116
  - As a user, my sync is not skipped if the importer configuration has changed since the last sync
117
  - As a user, my sync is not skipped if any content has been removed from the repository since the last sync
118
  - As a user, downloading of content starts quickly
119
120
<!-- end list -->
121
122
  - Sync types
123
124
<!-- end list -->
125
126
  - As a user, I can sync a kickstart tree from the same feed as other rpm/yum/dnf content.
127
128
<!-- end list -->
129
130
  - Download Behaviors
131
132
<!-- end list -->
133
134
  - As a user, I can limit the maximum speed of downloading in bytes / sec
135
  - As a user, I can limit the number of concurrent downloads
136
  - As a user, I can sync content on-demand by setting a repository's download policy.
137
  - As a user, I can specify the number of retries to be done before failing a given download
138
139
<!-- end list -->
140
141
  - Checksum Features
142
143
<!-- end list -->
144
145
  - As a user, I can sync a repository and have the files' checksums validated to ensure that no content is corrupt.
146
147
<!-- end list -->
148
149
  - GPG Signature Features
150
151
<!-- end list -->
152
153
  - As a user, I can verify that repo metadata has a valid signature. (would be a new feature)
154
  - 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.
155
156
<!-- end list -->
157
158
  - Mirror List Support
159
160
<!-- end list -->
161
162
  - As a plugin writer I can configure mirror lists and rotate between the mirrors
163
164
<!-- end list -->
165
166
  - round robin support
167
  - nearest mirror support (GeoIP or ping times)
168
169
##### Publish
170
171
  - As an authenticated user, I can publish a yum/dnf repository.
172
173
<!-- end list -->
174
175
  - DRPM
176
  - Distribution (kickstart tree)
177
  - Comps.xml content types (package group, environment, category, langpacks)
178
  - Yum repo metadata file
179 7 ttereshc
  - Modules
180 2 ttereshc
181
<!-- end list -->
182
183
  - As a user, I can publish a repository incrementally (re-use the pre-existing metadata and only add additional units)
184
  - As a user, I can force a full republish of a repository.
185
  - As a user, my publish will skip most of its work if no changes to a repository were made since last publish.
186
  - As a user, I can configure which checksum algorithm to use when creating metadata.
187
  - As a user, I can configure which checksum algorithm to use when creating updateinfo.xml.
188 7 ttereshc
  - Special publish for modules \[TBD\]
189 2 ttereshc
190
##### Export
191
192
  - As a user, I can export a repository or group of repositories to an ISO file (ISO 9660)
193
  - As a user, I can export a repository or group of repositories to a DVD / Blueray file (UDF aka. ISO/IEC 13346)
194
  - As a user, I can export a repository to a specified directory
195
  - As a user, I can export a repositories content that is associated or updated (errata) since a specific datetime( aka incremental?)
196
  - As a user, I can export RPM packages and errata as a set of JSON files
197
198
##### Upload
199
200
  - As an authenticated user, I can upload yum/dnf content types (not including Distribution)
201
  - 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)
202
203
##### Copy
204
205
  - As a user, I can copy a content of a specific type from one repository to another repository
206
  - As a user, I can copy RPM packages and all their dependencies from one repository to another repository
207
  - As a user, I can copy an Erratum and all the RPM packages it references from one repository to another repository
208
  - 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
209
  - Some content types create a new content unit in the destination repo instead of just copying.
210 7 ttereshc
  - Special copy for modules \[TBD\]
211 2 ttereshc
212
#### Not much yet discussed use cases
213
214
##### Content Protection
215
216
  - As an authenticated user, I can use key based authentication to allow/disallow access to content served by the content app
217
  - As an authenticated user, I can use user/password based authentication to allow/disallow access to content served by the content app.
218
219
##### Applicability
220
221
  - As an authenticated user, I can trigger an applicability for a consumer.
222
  - As an authenticated user, I can trigger an applicability for a repository.
223
224
##### Rsync Distributor
225
226
  - As a user i can distribute rpm content using a remote server.
227
228
## Pulp 2 features not present in Pulp 3
229
230
  - "gpgkey" importer setting - only used by pulp-agent.
231
  - "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.
232
233
<!-- end list -->
234
235
  - 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.
236
237
<!-- end list -->
238
239
  - As a user, I can have publish skip one or more content types, e.g. drpm, errata, etc
240
241
<!-- end list -->
242
243
  - We can't think of a use case for this. Maybe export of only RPMs and Errata, see export use case.