Object Relationships¶
There are models which are expected to be used in plugin implementation, so understanding what they are designed for is useful for a plugin writer. Each model below has a link to its documentation where its purpose, all attributes and relations are listed.
Here is a gist of how models are related to each other and what each model is responsible for.
Repository
containsContent
.RepositoryContent
is used to represent this relation.Content
can haveArtifact
associated with it.ContentArtifact
is used to represent this relation.ContentArtifact
can haveRemoteArtifact
associated with it.Artifact
is a file.RemoteArtifact
contains information aboutArtifact
from a remote source, including URL to perform download later at any point.Remote
knows specifics of the pluginContent
to put it into Pulp.Remote
defines how to synchronize remote content. Pulp Platform provides support for concurrent downloading of remote content. Plugin writer is encouraged to use one of them but is not required to.PublishedArtifact
refers toContentArtifact
which is published and belongs to a certainPublication
.PublishedMetadata
is a file generated while publishing and belongs to a certainPublication
.Publication
is a result of publish operation of a specificRepositoryVersion
.Distribution
defines how a publication is distributed for a specificPublication
.ProgressReport
is used to report progress of the task.GroupProgressReport
is used to report progress of the task group.
An important feature of the current design is deduplication of
Content
and Artifact
data.
Content
is shared between Repository
,
Artifact
is shared between
Content
.
See more details on how it affects remote implementation in Define your plugin Remote section.
Check pulp_file
implementation to see how all
those models are used in practice.
More detailed explanation of model usage with references to pulp_file
code is below.