Glossary¶

agent: A daemon running on a consumer. The agent provides a command & control API which is used by the Pulp server to initiate content changes on the consumer. It also sends scheduled reports concerning consumer status and installed content profiles to the Pulp server.
binding: An association between a consumer and a repository distributor for the purpose of installing content units on the specified consumer.
bundle: Term used to denote the collection of server, client, and agent components to provide support for a particular set of content types. For example, support for handling RPMs and errata is provided by the RPM bundle whereas support for Puppet modules is provided by the Puppet bundle.
CLI: Command Line Interface
consumer: A managed system that is the consumer of content. Consumption refers to the installation of software contained within a repository and published by an associated distributor.
content unit: An individual piece of content managed by the Pulp server. A unit does not necessarily correspond to a file. It is possible that a content unit is defined as the aggregation of other content units as a grouping mechanism.
distributor: Server-side plugin that takes content from a repository and publishes it for consumption. The process by which a distributor publishes content varies based on the desired approach of the distributor. A repository may have more than one distributor associated with it at a given time.
download policy: The method used to retrieve content for a repository. There are three possible policies: The immediate download policy, background download policy, and on-demand download policy. Both the background download policy and the on-demand download policy are deferred download policies.
immediate download policy: The default download policy for repositories. When using this policy, all content is downloaded before publishing the repository.
background download policy: A download policy that actively retrieves content units in the background after a publish has been performed.
on-demand download policy: A download policy that only saves a content unit locally after a client has requested that content unit.
deferred download policies: Download policies that do not require all content units to be downloaded locally to publish the repository.
extension: Client-side component that augments the CLI with new functionality. While all functionality in the client is provided through extensions, this term is typically used to refer to content type specific extensions provided by a content type bundle.
importer: Server-side plugin that provides support for synchronizing content from an external source and importing that content into the Pulp server. Importers are added to repositories to define the supported functionality of that repository.
iso8601: ISO Date format that is able to specify an optional number of recurrences, an optional start time, and a time interval. More information can be found in the conventions section of this guide.
node: A Pulp node is a Pulp server that has either a parent or child relationship to another Pulp server. Parent nodes provide content to child nodes. Child nodes consume content from a parent node as registered consumers.
registration: The association of a consumer to a Pulp server. Once registered, a consumer is added to Pulp’s inventory and may be bound to Pulp provided repositories. Content installs, updates and uninstalls may be initiated from the Pulp server on consumers running the Pulp agent.
repository: A collection of content units. A repository’s supported types is dictated by the configured importer. A repository may have multiple distributors associated which are used to publish its content to multiple destinations, formats, or protocols.
unit profile: A list of content unit installed on a consumer. The structure and content of each item in the profile varies based on the unit type.