Project

Profile

Help

Pulp 3 Minimum Viable Product » History » Sprint/Milestone 119

bmbouter, 11/27/2017 09:55 PM
Adding "Consumer Profile" and "Applicability" terms to the glossary

1 1 bmbouter
# Pulp 3.0.0 Minimum Viable Product (MVP)
2
3 21 bmbouter
<span style="color:red;">Lines highlighted in red need more attention.</span>
4 20 bmbouter
5 37 bmbouter
## Overall Guarantees
6
7 57 mhrivnak
  - This is not a direct replacement for Pulp 2.
8
  - This is the minimum required for a 3.0.0 beta and GA.
9
  - All REST API calls will update the DB using transactions as necessary to ensure data integrity.
10 37 bmbouter
11 59 bmbouter
## Legend
12
13
\[done\] means merged and documented  
14
\[in-progress\] means started but not fully done  
15
If there is no label the effort has not yet been started
16
17 1 bmbouter
## Authentication
18
19 59 bmbouter
As an authenticated user I can manage user(s). \[done\]
20 17 semyers
21
  - Add a user
22
  - View user(s)
23 58 mhrivnak
  - Update any user detail
24 1 bmbouter
  - Delete a user
25
26 59 bmbouter
As an API user, I can have documentation to generate a JSON Web Token (JWT) without the server being online. \[done\]
27 1 bmbouter
28 59 bmbouter
As an administrator, I can disable JWT token expiration. This configuration is in the settings file and is system-wide. \[done\]
29 1 bmbouter
30 59 bmbouter
As an administrator, I can configure the JWT tokens to expire after a configurable amount of time. This configuration is in the settings file and is system-wide. \[done\]
31 1 bmbouter
32 59 bmbouter
The JWT shall have a username identifier \[done\]
33 1 bmbouter
34 59 bmbouter
<span style="color:red;">As an API user, I can authenticate any API call (except to request a JWT) with a JWT. (not certain if this should be the behavior) \[in progress\]</span>
35 17 semyers
36 59 bmbouter
As an API user, I can invalidate all existing JWT tokens for a given user. \[done\]
37 17 semyers
38 59 bmbouter
As an authenticated user, when deleting a user 'foo', all of user 'foo's existing JWTs are invalidated. \[done\]
39 17 semyers
40 59 bmbouter
As an un-authenticated user, I can obtain a JWT token by using a username and password. \[done\]
41 1 bmbouter
42 110 daviddavis
As an authenticated user, I can filter users by: \[[3142](https://pulp.plan.io/issues/3142)\]
43
44
  - username: (equality, username_in_list)
45
46 1 bmbouter
## Repositories
47
48 18 dkliban@redhat.com
As an authenticated user, I can list all repos.
49
50 60 bmbouter
  - All fields are included \[done\]
51
  - Pagination is supported \[done\]
52 1 bmbouter
53 112 bmbouter
As an authenticated user I can use filters on Repositories list: \[[3079](https://pulp.plan.io/issues/3079)\]
54 109 amacdona@redhat.com
55
  - id: (id_in_list) \# id equality is not necessary, v3/repositories/\<UUID\>/
56
  - name: (equality, name_in_list)
57
58 18 dkliban@redhat.com
As an authenticated user, I can CRUD a repository
59
60 60 bmbouter
  - Create a repo \[done\]
61
  - Read a repo \[done\]
62
  - Update all mutable repo fields \[done\]
63
  - Delete a repo (asynchronous) \[done\]
64 1 bmbouter
65 112 bmbouter
As an authenticated user, I can view content for a repository.
66
67 18 dkliban@redhat.com
As an authenticated user, I can list a repository's associated importers and publishers
68
69 60 bmbouter
  - All fields are included \[done\]
70
  - Pagination is supported \[done\]
71 1 bmbouter
72 104 bmbouter
As an authenticated user, I can see the number of content unit types with counts for each \[done\]\[[3059](https://pulp.plan.io/issues/3059)\]
73 18 dkliban@redhat.com
74 51 bmbouter
## Importers
75
76
note: Importer attributes will commonly be available on importers, but aren't guaranteed to be used by all importers.
77
78 18 dkliban@redhat.com
As an authenticated user, I can CRUD an importer
79
80
  - Create an importer
81
  - Read an importer
82
  - Update all mutable importer fields
83 21 bmbouter
  - Delete an importer (asynchronous)
84 1 bmbouter
85 113 bmbouter
As an authenticated user, I have filters on the Importer list: \[[3080](https://pulp.plan.io/issues/3080)\]
86 109 amacdona@redhat.com
87
  - id: (id_in_list) \# id equality is not necessary, objects are referenced by id
88
  - name: (equality, name_in_list)
89
90 64 mhrivnak
As an authenticated user I can configure the following attributes on an Importer: \[done\]
91 47 bmbouter
92 48 amacdona@redhat.com
  - validate (bool) \[optional: defaults to True\]: If true, the plugin will validate imported content.
93
  - ssl_ca_certificate (str) \[optional\] String containing a PEM encoded CA certificate used to validate the server certificate presented by the external source.
94
  - ssl_client_certificate (str) \[optional\] Contains a PEM encoded client certificate used for authentication.
95
  - ssl_client_key (str) \[optional\] Contains a PEM encoded private key used for authentication.
96
  - ssl_validation (bool) \[optional: defaults to True\]: If true, SSL peer validation must be performed.
97 65 mhrivnak
  - proxy_url (str) \[optional\] Contains the proxy URL. Format: scheme://user:password@host:port.
98 48 amacdona@redhat.com
  - username (str) \[optional\] Contains the username to be used for authentication when syncing.
99 1 bmbouter
  - password (str) \[optional\] Contains the password to be used for authentication when syncing.
100 63 mhrivnak
  - <span style="color:orange;">download_policy (str) \[optional\] Contains the downloading policy name. This is a choice of three options:  
101
 \- immediate (default) - Downloading occurs during sync. The sync task does not complete until downloading is done.  
102
 \- background - Downloading is started by the sync but occurs in the background. The sync task completes before downloading is complete.  
103
 \- on-demand - The sync task records everything that would be downloaded but does not download content. Downloading occurs on demand as driven by client requests for content.</span>
104 1 bmbouter
  - feed_url (str) \[optional\] Contains the URL of an external content source. This is optional.
105 63 mhrivnak
  - <span style="color:orange;">sync mode: (str) \[optional\]. It has two choices 'additive' and 'mirror':  
106
 \- additive (default) - all remote content is added to the local repository on sync. During sync no content is removed from the local repository.  
107
 \- mirror - the local content will mirror the remote content exactly, removing local content if not also present in the remote content.</span>
108 50 bmbouter
  - name (str) \[required\] Contains the name.
109
  - last_updated (datetime) \[read-only\] Contains the datetime of the last importer update.
110 53 bmbouter
  - last_synced (datetime) \[read-only\] Contains the datetime of the last importer sync.
111 51 bmbouter
112 52 bmbouter
## Publishers
113 51 bmbouter
114
note: Publisher attributes will commonly be available on publishers, but aren't guaranteed to be used by all publishers.
115 47 bmbouter
116 18 dkliban@redhat.com
As an authenticated user, I can CRUD a publisher
117
118
  - Create a publisher
119 1 bmbouter
  - Read a publisher
120
  - Update all mutable publisher fields
121 50 bmbouter
  - Delete a publisher (asynchronous)
122 1 bmbouter
123 113 bmbouter
As an authenticated user, I have filters on the Publisher list: \[[3081](https://pulp.plan.io/issues/3081)\]
124 109 amacdona@redhat.com
125
  - id: (id_in_list) \# id equality is not necessary, objects are referenced by id
126
  - name: (equality, name_in_list)
127
128 50 bmbouter
As an authenticated user I can configure the following attributes on a Publisher:
129
130 1 bmbouter
  - relative_path (str) \[optional\] The (relative) path component of the published url.
131 50 bmbouter
  - name - (str) \[required\] contains the name.
132 109 amacdona@redhat.com
  - last_published (datetime) \[read-only\] When the last successful publis%{color:red}h occurred.
133 50 bmbouter
  - last_updated (datetime) \[read-only\] The datetime of the last publisher update.
134 1 bmbouter
  - <span style="color:red;">auto_publish(bool) - ??? consider adding auto-publish feature to MVP</span>
135
136 109 amacdona@redhat.com
## <span style="color:red;">Distributions</span>
137
138
<span style="color:red;">As an authenticated user, I can CRUD Distributions:</span>  
139
{color:red} \* Create a Distribution  
140
{color:red} \* Read a Distribution  
141
{color:red} \* Update all mutable Distribution fields  
142
{color:red} \* Delete an Distribution (asynchronous?)
143
144 113 bmbouter
As an authenticated user, I have filters on the Distribution list: \[[3082](https://pulp.plan.io/issues/3082)\]
145 109 amacdona@redhat.com
146
  - id: (id_in_list) \# id equality is not necessary, objects are referenced by id
147
  - name: (equality, name_in_list) 
148
  - base_path: (equality, substring, base_path_in_list)
149
150
## <span style="color:red;">Publications</span>
151
152
{color:red} \* Read a Publication  
153
{color:red} \* List all Publications  
154
{color:red} \* Delete a Publication (asynchronous?)
155
156 113 bmbouter
{color:red} As an authenticated user, I have filters on the Publication list:  
157 109 amacdona@redhat.com
{color:red} \* id: (id_in_list) \# id equality is not necessary, objects are referenced by id
158
159 72 mhrivnak
## Sync and Publish
160 1 bmbouter
161 66 mhrivnak
As an authenticated user, I can trigger an importer to sync. \[done\]
162 19 bmbouter
163
  - I can follow the progress of all syncs. (Syncs are asynchronous.)
164
  - I cannot pass "sync" options.
165
  - Auto-publish is not included as an importer property.
166
167 66 mhrivnak
As an authenticated user, I can trigger a publisher to publish. \[done\]
168 19 bmbouter
169
  - I can follow the progress of all publishes. (Publishes are asynchronous.)
170
  - I cannot pass "publish" options.
171
172 71 mhrivnak
## Content Manipulation
173 25 bmbouter
174 73 mhrivnak
#### Uploading Artifacts
175 32 bmbouter
176 67 mhrivnak
As an authenticated user, I can create an Artifact by uploading a file. \[done\]
177 30 bmbouter
178 68 mhrivnak
As an authenticated user, I can specify a size and/or digest to validate the uploaded file. \[done\]
179
180 71 mhrivnak
#### Creating Content Units
181 70 mhrivnak
182 1 bmbouter
As an authenticated user, I can create a content unit by providing the content type (in the URL), references to Artifacts, and the metadata supplied in the POST body. \[done\]
183 102 bmbouter
184 29 bmbouter
#### Add / Remove Content from a Repository
185 99 bmbouter
186 113 bmbouter
As an authenticated user, I can add content (specific existing content) to a repository
187 99 bmbouter
188
  - I can specify one or more content units by id/href
189
  - I can follow the progress. (adding are asynchronous).
190
191 113 bmbouter
As an authenticated user, I can remove specified content from a repository
192 99 bmbouter
193
  - I can specify one or more content units by id/href
194
  - I can follow the progress. (removing are asynchronous).
195 101 bmbouter
196 1 bmbouter
#### Simple Copy
197 101 bmbouter
198 113 bmbouter
As an authenticated user, I can search (synchronous call) a repository's content using filtering.
199 101 bmbouter
200
  - note: In a separate call (async), I can add this content to another repository. This is effectively a copy operation in two calls.
201
202
As an authenticated user, I can import all content from one repository into another repository in a single async call. (Clone use case)
203
204
  - I can follow the progress. (adding are asynchronous).
205
206
#### Complex Copy
207
208
As a plugin writer I can provide a rich search features with abitrary viewsets. e.g. depsolving, verisoning, etc
209
210
Examples of specific plugin use cases motivating the above general viewset
211
212
  - As an authenticated user, I can add an Errata from one repository to another repository along with packages mentioned in the Errata and all their dependencies that are present in the source repository.
213
  - As an authenticated user, I can add bunch of dependencies and store n versions back for each RPM.
214
  - As an authenticated user, I can use depsolving and versioning copy features together
215
  - As an authenticated user, I can copy a puppet module and all of it's dependencies from one repository to another. 
216 71 mhrivnak
  - As an authenticated user, I can depsolve units to be added to a destination repo based on an errata
217 1 bmbouter
218 95 bmbouter
#### Delete
219 1 bmbouter
220 109 amacdona@redhat.com
FAs an authenticated user, I can delete a specific content unit%  
221 95 bmbouter
<span style="color:red;">\* If the content unit is still in at least one repository the delete fails with a listing of all repositories the unit is part of.</span>  
222
<span style="color:red;">\* Artifacts and associated files from the deleted unit are cleaned up</span>
223
224
<span style="color:red;">As an authenticated user, I can delete multiple content units with filtering</span>  
225
<span style="color:red;">\* If a content unit is still in at least one repository the delete fails with a listing of all repositories the unit is part of.</span>  
226
<span style="color:red;">\* Artifacts and associated files from deleted units are cleaned up</span>
227 1 bmbouter
228 112 bmbouter
#### Filtering
229
230
As an authenticated user, I can filter Content by repository information when plugin writers have provided such a filter
231
232
As an authenticated user, I can filter content by repository
233
234
As an authenticated user, I can filter content by type
235
236
As an authenticated user, I can filter content on plugin specific attributes when plugin writers have provided such a filter
237
238 74 mhrivnak
## <span style="color:red;">Versioned Repositories</span>
239 1 bmbouter
240 40 bmbouter
As an authenticated user, I can list the content in a particular repository version
241
242
  - All fields are included
243
  - Pagination is supported
244
  - <span style="color:red;">Filtering support</span>
245
246
As an authenticated user, I can discover a URL to the latest version of a repository  
247
<span class="resource repository the on attributes or endpoint, API dedicated a through \^ Is" style="color:red;"></span>
248 1 bmbouter
249 43 bmbouter
As an authenticated user, I can run a publisher without a repository version and have it default to the latest version.
250
251 1 bmbouter
<span style="color:red;">As an authenticated user, I can delete a repository version by specifying the version</span>
252
253 43 bmbouter
<span style="color:red;">As an authenticated user, I can upload multiple content(s?) and add create a single new version that adds all of them.</span>
254
255 95 bmbouter
## Orphan Content Units and Artifacts
256 43 bmbouter
257 95 bmbouter
As an authenticated user, I can cause an action that cleans up **both** orphaned content units and orphaned artifacts.
258 43 bmbouter
259 95 bmbouter
  - I cannot specify the units specifically (all types).
260
  - I can follow the progress of all cleanups. (Cleanups are asynchronous.)
261 1 bmbouter
262 22 bmbouter
## Task Management
263
264 76 mhrivnak
As an authenticated user, I can list all tasks
265
266 22 bmbouter
  - <span style="color:orange;">Filtering support on \['state', 'id', 'group'\]</span>
267 76 mhrivnak
  - <span style="color:orange;">This does not include associated progress reports</span>
268 22 bmbouter
269
As an authenticated user, I can see a detail view for a specific task \[done\]
270
271
  - all attributes of a task
272 76 mhrivnak
  - all associated progress reports
273 1 bmbouter
274
As an authenticated user, I can cancel a task \[done\]
275
276 77 mhrivnak
  - don't dare to use the DELETE verb!
277
278 1 bmbouter
As an authenticated user, I can delete tasks.
279
280 114 daviddavis
As an authenticated user, I can filter tags by: \[[3144](https://pulp.plan.io/issues/3144)\]
281 110 daviddavis
282
  - state (equality, state_in_list)
283
  - started_at(started_in_range)
284
  - finished_at(finished_in_range)
285
  - worker (equality)
286
  - parent (equality)
287
288 78 mhrivnak
## Task Group
289 1 bmbouter
290
<span style="color:red;">I can view a summary of the status of all tasks in a group</span>
291
292 82 mhrivnak
## Status
293 1 bmbouter
294 82 mhrivnak
As an unauthenticated user I can view the status of Pulp workers, resource managers, and celerybeats. \[done\]
295 42 dkliban@redhat.com
296 80 mhrivnak
As an unauthenticated user I can view the status of the web server's connection to the database and message broker. \[done\]
297 46 bmbouter
298 28 bmbouter
As an unauthenticated user I can view the versions of core and each installed plugin.
299 110 daviddavis
300 115 daviddavis
## Workers
301 110 daviddavis
302 115 daviddavis
As an authenticated user, I can filter workers by: \[[3143](https://pulp.plan.io/issues/3143)\]
303 110 daviddavis
304
  - last_heartbeat (range)
305
  - name (substring)
306 116 daviddavis
  - gracefully_stopped (equality)
307 1 bmbouter
308 83 mhrivnak
## Plugin API
309 1 bmbouter
310 83 mhrivnak
As a plugin writer, I have a plugin API that is semantically versioned at 0.x separate from the REST API \[done\]
311 28 bmbouter
312 83 mhrivnak
As a plugin writer, I can report progress with a message and state \[done\]
313 28 bmbouter
314 83 mhrivnak
As a plugin writer, I can report progress with an optional suffix \[done\]
315 28 bmbouter
316 83 mhrivnak
As a plugin writer, I can report progress with a total count of things to do an the current count of things done \[done\]
317 28 bmbouter
318 83 mhrivnak
As a plugin writer, non-fatal exceptions on the Task and are included in the Task detail. non_fatal exceptions do not cause the Task to be marked as failed, but may be interpreted by the user as not fully successful. \[done\]
319 28 bmbouter
320 83 mhrivnak
As a plugin writer, the working directory is set before Task work is done and cleaned up afterwards. I should not need to interact with the file system outside of the working dir. \[done\]
321 28 bmbouter
322 84 bmbouter
<span style="color:red;">As a plugin writer, I can provide a subclassed Importer. The importer's responsibility is to synchronize the content of a Pulp repository with the content of a remote repository. (a circular import problem needs to be discussed and may cause this to change) \[done\]</span>
323 28 bmbouter
324 83 mhrivnak
<span style="color:red;">As a plugin writer, I can provide a subclassed Publisher. The publisher's responsibility is to publish content. (a circular import problem needs to be discussed and may cause this to change) \[done\]</span>
325 28 bmbouter
326 83 mhrivnak
As a plugin writer, I can define unit types by subclassing Content models to provide concrete content unit types to be manged by the platform. \[done\]
327 28 bmbouter
328 83 mhrivnak
As a plugin writer, I can interact with and create Artifacts \[done\]
329 28 bmbouter
330 83 mhrivnak
As a plugin writer, my app will be discovered by Pulp's app via an entry point provided by the plugin writer \[done\]
331 6 Ichimonji10
332 83 mhrivnak
As a plugin writer, I can use the plugin API to query content units/artifacts associated with a repository. \[done\]
333 1 bmbouter
334 8 Ichimonji10
As a plugin writer, I can add and remove content units to and from a repository. \[done\]
335 1 bmbouter
336 112 bmbouter
As a plugin writer, I have documentation that shows how I can add filters to filter content responsibly.
337
338
As a plugin writer, I have documentation on how to write a filter for my Content that can use the RepositoryContent through table.
339
340
  - note: This will allow users to filter content by repository information
341
342 103 bmbouter
## Plugin Writer "live APIs"
343
344 106 bmbouter
As a plugin writer, I can provide a Live API with arbitrary views and viewsets.  
345
As a plugin writer, I have documentation on what URLs I should -not use for my views and viewsets
346
347 108 bmbouter
Here are some concrete use cases driving the very Live API use cases above:
348
349
~~~
350
# Concrete user use cases:
351 113 bmbouter
    As an authenticated user, I can use the puppet client to fetch content from Pulp using the Forge API
352
    As an authenticated user I can use the docker client to fetch content from Pulp using the Docker v1 API
353
    As an authenticated user I can use the docker client to fetch content from Pulp using the Docker v2 API
354 108 bmbouter
355
# Concrete plugin writer use cases
356
    As a puppet plugin developer, I can provide a viewset which handles the server side of the puppet Forge v3 API
357
    As a docker plugin developer, I can provide a viewset which handles the server side of the docker v1 API
358
    As a docker plugin developer, I can provide a viewset which handles the server side of the docker v2 API
359
~~~
360
361 117 bmbouter
## Webserver Deployment
362 106 bmbouter
363 113 bmbouter
As an authenticated user, I can deploy all Pulp webservices on one process
364 106 bmbouter
365 113 bmbouter
<span style="color:red;">As an authenticated user, I can deploy the Pulp REST API exclusively in one process</span>  
366
<span style="color:red;">As an authenticated user, I can deploy the Pulp content serving view exclusively in one process</span>  
367
<span style="color:red;">As an authenticated user, I can deploy the Pulp content serving view with reduced permissions.</span>  
368
<span style="color:red;">As an authenticated user, I can deploy a Plugin's Live API exclusively in one process.</span>
369 103 bmbouter
370 94 bizhang
## CLI
371 93 bizhang
372 1 bmbouter
We will use coreapi-cli to generate a one to one mapping of cli commands to rest api schema #3068  
373 26 bmbouter
<span style="color:orange;">We will have a wrapper for coreapi-cli. This wrapper will handle parallel progress reporting</span>
374
375
## Download API
376
377
As a plugin writer, I can download files via
378
379
  - http://
380
  - https://
381
  - file://
382 27 bmbouter
383
As a plugin writer, I can configure a downloader with:
384 26 bmbouter
385
  - Basic Auth
386
  - SSL Cert Client Auth
387
  - Custom CAs will be configured via a "trust store" either on the system or similar. Pulp will not do anything to read/load/manage CAs directly.
388
389
As a plugin writer, I can provide arbitrary behaviors for customized downloaders
390
391
  - For example token authentication in the docker plugin
392
393
As a plugin writer, I can have connection pooling/reuse
394
395
As a plugin writer, I have proxy settings
396
397
  - proxy url (containing basic auth info)
398
399
As a plugin writer, I can have great logs
400
401 113 bmbouter
As an authenticated user, I have documentation about how to use something for bandwidth limiting
402 26 bmbouter
403
As a plugin writer, I can configure the validation mechanisms used at download time
404
405
  - checksum validation - minimum (md5, sha1, sha256, sha512)
406
  - size validation
407 1 bmbouter
408
<span style="color:red;">As a plugin writer, I expect units that are missing from the remote repository to not be created in Pulp when using the immediate download policy.</span>
409
410 26 bmbouter
<span style="color:red;">As a plugin writer, I expect units that are missing from the remote repository to be created in Pulp when using background or on_demand download policies.</span>
411
412 112 bmbouter
<span style="color:red;">As a plugin writer I can configure mirror lists and rotate between the mirrors</span>  
413
<span style="color:red;">\* round robin</span>  
414
<span style="color:red;">\* nearest mirror support</span>
415 26 bmbouter
416 1 bmbouter
As a plugin writer, the plugin API provides tooling whereby I can provide the content to be added and removed from the repository. This tooling supports both immediate and deferred downloading.
417 26 bmbouter
418 27 bmbouter
As a plugin writer I can manage the catalog by using ChangeSets
419 26 bmbouter
420
As a plugin writer, the plugin can participate in adding content for cases where the decision to add additional content is based content that has been downloaded.
421 1 bmbouter
422
As a plugin writer, I can fetch content myself (but I am not encouraged to do so) with code I write
423
424 56 ttereshc
As a plugin writer, I can CRUD content units
425 1 bmbouter
426 118 bmbouter
## <span style="color:red;">Consumer Profile Applicability</span>
427 1 bmbouter
428 118 bmbouter
<span style="color:red;">Using Consumer Profiles and repository bindings I can compute applicability with 2.y parity</span>
429 1 bmbouter
430 118 bmbouter
  - Performance needs to be awesome%
431 36 bmbouter
432 86 mhrivnak
## Migrations only involving Pulp 3
433 1 bmbouter
434 87 mhrivnak
Users can run "pulp-manager migrate" to migrate the database and adjust state in other locations (filesystem, message broker, ...). \[done\]
435 1 bmbouter
436
## Web Server Integration
437
438 105 bmbouter
<span style="color:red;">As a user, I can have content efficiently served to me by Apache by Pulp using the X-SEND response headers \[[2914](https://pulp.plan.io/issues/2914)\]</span>  
439
<span style="color:red;">As a user, I can have content efficiently served to me by Nginx by Pulp using the X-Accel-Redirect response headers \[[2914](https://pulp.plan.io/issues/2914)\]</span>
440
441
<span style="color:red;">As a user, I can have an Ansible role to install Apache which enables Apache integration for Pulp and configures Apache to serve Pulp. \[[2921](https://pulp.plan.io/issues/2921)\]</span>  
442
<span style="color:red;">As a user, I can have an Ansible role to install Nginx which enables Nginx integration for Pulp and configures Nginx to serve Pulp. \[[2922](https://pulp.plan.io/issues/2922)\]</span>
443 87 mhrivnak
444 89 mhrivnak
## Glossary
445 88 mhrivnak
446 1 bmbouter
Repository - A named collection of content.
447
448 39 jortel@redhat.com
Artifact - A file associated with one content (unit). Artifacts are not shared between content (units). Create a content unit using an uploaded file ID as the source for its metadata. Create Artifacts associated with the content unit using an uploaded file ID for each; commit as a single transaction.
449
450
Content (unit) - A single piece of content manged by Pulp. Each file associated with a content (unit) is called an Artifact. Each content (unit) may have zero or many Artifacts.
451 95 bmbouter
452
Orphan Content (unit): A content unit that is a member of 0 repositories
453
454
Orphan Artifact: An Artifact that is associated with 0 Content Units and 0 Publications
455 98 bmbouter
456
Add (Content Unit): An operation causing a repository to contain a content unit(s)
457
458
Remove (content unit): An operation causing a repository to not contain a content unit(s)
459 119 bmbouter
460
Consumer Profile - A set of installed units on a specific machine. In Pulp3 this machine is not a "consumer" in the same sense as Pulp2. Pulp is not "managing" the machine anymore; Pulp3 only collects Profile information.
461
462
Applicability - A plugin defined term meaning when a package update available in a repository is applicable to a given consumer as determined by the Consumer Profile.