Containers#

Pulp#

An all-in-one pulp image that can assume each of the following types of service:

  • pulpcore-api - serves the Pulp(v3) API. The number of instances of this service should be scaled as demand requires. Administrators and users of all of the APIs put demand on this service.

  • pulpcore-content - serves content to clients. pulpcore-api redirects clients to pulpcore-content to download content. When content is being mirrored from a remote source, this service can download that content and stream it to the client the first time the content is requested. The number of instances of this service should be scaled as demand requires. Content consumers put demands on this service.

  • pulpcore-worker - performs syncing, importing of content, and other asynchronous operations that require resource locking. The number of instances of this service should be scaled as demand requires. Administrators and content importers put demands on this service.

  • pulpcore-resource-manager - a different type of pulp-worker that plays a coordinating role for the tasking system. All asynchronous work flows through this service. Because pulpcore-resource-manager coordinates pulp-workers, it is only possible to run one at a time, but other instances can be run as hot spares that will take over if the active one fails.

Currently built with the following plugins:

Tags#

  • latest: Built nightly, with master/main branches of each plugin.
  • stable: Built on push, with latest released version of each plugin.
  • 3.y.z: Pulpcore 3.y.z version and its compatible plugins.

https://quay.io/repository/pulp/pulp?tab=tags

Pulp Web#

An Nginx image based on centos/nginx-116-centos7, with pulpcore and plugins specific configuration.

Tags#

  • latest: Built nightly, with master/main branches of pulpcore and its plugins.
  • stable: Built on push, with latest released version of each plugin.
  • 3.y.z: Pulpcore 3.y.z version and its compatible plugins.

https://quay.io/repository/pulp/pulp-web?tab=tags

Galaxy#

An all-in-one galaxy image that can assume each of the following types of service:

  • pulpcore-api - serves the Galaxy (v3) API. The number of instances of this service should be scaled as demand requires. Administrators and users of all of the APIs put demand on this service.

  • pulpcore-content - serves content to clients. pulpcore-api redirects clients to pulpcore-content to download content. When content is being mirrored from a remote source, this service can download that content and stream it to the client the first time the content is requested. The number of instances of this service should be scaled as demand requires. Content consumers put demands on this service.

  • pulpcore-worker - performs syncing, importing of content, and other asynchronous operations that require resource locking. The number of instances of this service should be scaled as demand requires. Administrators and content importers put demands on this service.

  • pulpcore-resource-manager - a different type of pulp-worker that plays a coordinating role for the tasking system. All asynchronous work flows through this service. Because pulpcore-resource-manager coordinates pulp-workers, it is only possible to run one at a time, but other instances can be run as hot spares that will take over if the active one fails.

Tags#

  • latest: Built nightly, with master branch of galaxy.
  • stable: Built on push, with latest released version of galaxy.
  • 4.y.z: Galaxy 4.y.z version.

https://quay.io/repository/pulp/galaxy?tab=tags

Galaxy Web#

An Nginx image based on centos/nginx-116-centos7, with galaxy specific configuration.

Tags#

  • latest: Built nightly, with master branch of galaxy.
  • stable: Built on push, with latest released version of galaxy.
  • 4.y.z: Galaxy 4.y.z version.

https://quay.io/repository/pulp/galaxy-web?tab=tags

Pulp Operator#

Ansible Operator image, with the following ansible roles:

Tags#

  • latest: Built nightly, with main branch of pulp-operator.
  • 0.y.z: Pulp Operator 0.y.z version.

https://quay.io/repository/pulp/pulp-operator?tab=tags

Build#

The images can be built with the help of an Ansible playbook. To build the images:

ansible-playbook build.yaml

See containers/vars/defaults.yaml for how to customize the "images" variable (data structure).

You can add -e cache=false to that command to prevent outdated image layers from being used.