User Tools

Site Tools


services:pulp

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
services:pulp [2026/07/16 12:31]
vaibhav
services:pulp [2026/07/16 13:06] (current)
vaibhav
Line 9: Line 9:
 By adopting a cloud-native strategy, the Pulp cluster is deployed on OpenShift to achieve optimal scalability and high availability. The official resources for OpenShift deployment can be accessed at [[https://​pulpproject.org/​pulp-operator|Pulp Project Documentation]]. By adopting a cloud-native strategy, the Pulp cluster is deployed on OpenShift to achieve optimal scalability and high availability. The official resources for OpenShift deployment can be accessed at [[https://​pulpproject.org/​pulp-operator|Pulp Project Documentation]].
  
-  * **Unordered List ItemOperator-Based Deployment:​** The architecture utilizes the Pulp Operator to manage the full lifecycle of the Pulp components, including database (PostgreSQL) and cache (Redis) instances.+  * **Operator-Based Deployment:​** The architecture utilizes the Pulp Operator to manage the full lifecycle of the Pulp components, including database (PostgreSQL) and cache (Redis) instances.
  
   * **Persistent Storage:** Artifact storage is managed via Persistent Volume Claims (PVCs), ensuring data persistence across pod restarts and updates.   * **Persistent Storage:** Artifact storage is managed via Persistent Volume Claims (PVCs), ensuring data persistence across pod restarts and updates.
Line 25: Line 25:
  
 The pulp-cli tool must be installed and configured with the appropriate server username and password. Refer to the [[https://​pulpproject.org/​pulp-cli/​docs/​user/​guides/​installation/​|Pulp CLI installation guide]] for installation instructions. The pulp-cli tool must be installed and configured with the appropriate server username and password. Refer to the [[https://​pulpproject.org/​pulp-cli/​docs/​user/​guides/​installation/​|Pulp CLI installation guide]] for installation instructions.
 +
 +**Configure Pulp Client**
 +
 +To configure the Pulp client, run the following command with ceph specific Pulp username and password.
 +
 +  $ pulp config create --base-url https://​pulp.apps.pok.os.sepia.ceph.com/​pulp/​api/​v3/​ --username <​PULP_USERNAME>​ --password <​PULP_PASSWORD>​
 +
 +**Filtering Repositories by Label**
 +
 +Ceph repositories use metadata labels such as branch names, Ceph versions, or operating systems to help you isolate the specific artifacts you need.
 +
 +  * **List repositories by a single label**
 +      * $ pulp <rpm | deb> repository list --label-select "​branch=<​branch_name>"​
 + 
 +  * **List repositories using multiple labels**
 +      * $ pulp <rpm | deb> repository list --label-select "​branch=<​branch_name>,​distro=<​os_distro>"​
 +
 +**Inspecting Repository Content**
 +
 +After identifying the target repository using label queries, view the specific packages hosted within it.
 +
 +  $ pulp rpm repository show --name <​repository_name>​
  
 ==== Purge and Retention Policy ==== ==== Purge and Retention Policy ====
  
 +The automated cleanup cycle initiates daily at midnight to maintain storage efficiency. Data longevity is governed by the following retention framework
 +
 +  * **Branch-Specific Configurations:​** Unique branch settings define varying storage durations (typically 14 to 30 days) and ensure the preservation of a mandatory build count (between 2 and 10 builds) as specified by the policy.
 +
 +  * **Standard Retention:​** Branches lacking custom rules adhere to a baseline default policy, which maintains artifacts for 14 days without a guaranteed minimum build count.
services/pulp.1784205071.txt.gz ยท Last modified: 2026/07/16 12:31 by vaibhav