Skip to content

Pulp's Blog

  • 4 min read

Checkpoint Support - A Journey Towards Predictable and Consistent Deployments

In the ever-evolving landscape of software development, ensuring predictability and consistency in deployments has always been a challenge. Our team faced similar hurdles, especially when managing historical versions of repositories. We needed a solution that could help us recreate environments from specific points in time, ensure reproducible deployments, and track changes in package behavior over time.

Inspired by the success stories of Ubuntu Snapshots on Azure and the increased security and resiliency of Canonical workloads on Azure, we embarked on a journey to develop a feature that could address these challenges.

  • 6 min read

Whenever, Whatever-based Release Cycle

"Release fast, release often!" is not a metaphor, it is a mantra.

Pulp used to be a service mainly running on-premises as part of products with extremely long release cycles. About two years ago, we heard rumors to add highly volatile cloud service style installations to the mix. Because releasing a new version of pulpcore or any of its many plugins was a herculean task, the rumors were accompanied by very concerning sentences like: "We will run this service off of main branches of all the plugins." If that does not make you shiver, you can just stop reading here and go on with your happy life.

  • 1 min read

Pulp UI Beta out now in Pulp images

Pulp-UI (beta) is now available in the latest pulp/pulp image. This was a huge effort over the last two months to get the beta into the hands of our users. Big thanks to Martin Hradil, Zita Nemeckova and everyone who helped us get here. Check out the demo below:

  • 7 min read

RPM Content Service Performance and Scale Testing

Goals

  1. Help pulp_rpm users plan the number of pulp-content apps to serve a given traffic rate for their object-storage backed installation.

  2. Determine what the architectural scalability limit is for pulp_rpm content serving.

To achieve these goals in this blog post, I'll be doing two things:

  • Characterize the relationship between sustained requests / sec to the pulp-content app and the number of pulp-content apps without increases in latency.

  • Identify rate limiting components in various test scenarios.