Hi,

Generally the directory structure that pulp uses for saving & serving data is 
not something that you should have to worry about. The Pulp server will manage 
it's space and the links that are created during publishing. Generally, content 
is stored in /var/lib/pulp/content and then when repositories are published 
they link back to the content from the publish locations in the 
/var/lib/pulp/published directory.  The /var/lib/pulp/working directory should 
be on a local disk on your server as it is used for temp space during 
repository syncing & publishing.  Regards,

-Barnaby

----- Original Message -----
From: "Vijayabalan Balakrishnan" <[email protected]>
To: [email protected]
Sent: Friday, February 13, 2015 8:37:48 AM
Subject: [Pulp-list] Pulp repository - Consumer Group and Repository Group



Hi, 

I have implemented pulp infrastructure based on the following scenario's. 

1. Pulp server - bserver1.example.com [getting update from origin feed] 
2. Pulp Server & Admin Client - bserver2.example.com [getting update from 
parent pulp server that is bserver1] 
3. Pulp Consumer/Client - bclient.example.com 

I have created the following 3 repositories and one consumer group and synced 
with upstream repository from internet. Now 3 repositories configured and 
published with all rpms. Now i have registered bclient.example.com client with 
pulp server. I have installed one package also via pulp from pulp master and 
got installed successfully. 

As per my understanding through pulp we can save huge space for all 
repositories and avoid duplication. 

Pulp's usage model involves syncing multiple up-stream repositories locally; 
these repositories can then be cloned, which uses hard links to sync them 
locally with almost no disk space used. This allows us to sync a repository 
once, then duplicate it as many times as necessary to support multiple teams 
and multiple stability levels. 
Can anyone suggest me the good link to understand the directory structure and 
the purpose behind it in order to design well for multiple repository 
infrastructure to save disk space. 

Please help me on this... 

Thanks, 
BVIJAY 

_______________________________________________
Pulp-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/pulp-list

_______________________________________________
Pulp-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/pulp-list

Reply via email to