BT

Pulp 2.5 Released Including Docker Repository Management

| by Carlos Sanchez Follow 0 Followers on Dec 23, 2014. Estimated reading time: 1 minute |

Pulp is a repository content management tool, supporting RPM, Debian, Puppet modules, and now Docker repositories amongst other content. The project has released version 2.5, including bug fixes and a new plugin to manage Docker repositories.

As part of the SysAdvent series, Justin Garrison has provided an introduction to managing repositories with Pulp. Pulp uses importers to fetch and sync content from external sources, local filesystem or other repositories, and distributors then publish that content via http, ISO, rsync or other means. New sources and formats can be added and extended with plugins.

Pulp 2.5.0 works with pulp_docker, an optional plugin to manage Docker repositories, still in tech preview status. The plugin allows to locally mirror either all of or part of a Docker repository, host content in new repositories, and manage content from multiple sources in a single place, including:

  • Separation of administrator interface (Pulp API) and end-user interface (Docker)
  • Role-based access control (RBAC) with LDAP support.
  • Synchronization of content across an organization using nodes.
  • Promotion of content through user-defined environments, like "dev", "test", and "prod".
  • Event-based notifications through http, amqp or email.
  • Read-only implementation of the Docker registry API that can be deployed independently.

Pulp can be deployed with the Docker registry functionality as a VM, with Crane as a Docker container, or using a multi-container environment. A Puppet module is also provided for installation and configuration in RHEL and Fedora.

Pulp components include:

  • Apache httpd: front-end for API and http(s) published repos.
  • Pulp Workers: process for long running tasks like repo syncing and publishing.
  • Pulp CeleryBeat: maintains workers and task cancellation.
  • Pulp Resource Manager: job assigner for tasks.
  • MongoDB: repository and content metadata value store.
  • Apache Qpid/RabbitMQ: message bus for job assignation.
  • pulp-admin: command line tool for managing content and consumers.

All the components can be distributed to scale the service. Pulp servers can also be distributed, replicating other servers fully or partially, across multiple locations in parent-child node relationships.

Rate this Article

Adoption Stage
Style

Hello stranger!

You need to Register an InfoQ account or or login to post comments. But there's so much more behind being registered.

Get the most out of the InfoQ experience.

Tell us what you think

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread
Community comments

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread

Discuss

Login to InfoQ to interact with what matters most to you.


Recover your password...

Follow

Follow your favorite topics and editors

Quick overview of most important highlights in the industry and on the site.

Like

More signal, less noise

Build your own feed by choosing topics you want to read about and editors you want to hear from.

Notifications

Stay up-to-date

Set up your notifications and don't miss out on content that matters to you

BT