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.
RepositoryContentis used to represent this relation.
Artifactassociated with it.
ContentArtifactis used to represent this relation.
RemoteArtifactassociated with it.
Artifactis a file.
RemoteArtifactcontains information about
Artifactfrom a remote source, including URL to perform download later at any point.
Remoteknows specifics of the plugin
Contentto put it into Pulp.
Remotedefines 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.
ContentArtifactwhich is published and belongs to a certain
PublishedMetadatais a repository metadata which is published, located in
/var/lib/pulp/publishedand belongs to a certain
Publisherknows specifics of the plugin
Contentto make it available outside of Pulp.
Publisherdefines how to publish content available in Pulp.
Publicationis a result of publish operation of a specific
Distributiondefines how a publication is distributed for a specific
ProgressBaris used to report progress of the task.
An important feature of the current design is deduplication of
Content is shared between
Artifact is shared between
See more details on how it affects remote implementation in Define your plugin Remote section.
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.