Hi Sean, Are you referring to the directory where the content is stored long
term or the working directory that is used as scratch space as files are
downloaded? Generally the recommended means by which the long term storage is
recommended to be addressed is to change the mount point for
Hi Sean,
FWIWI that's what we do.. /var/lib/pulp is an NFS mount. And recently did the
same for /var/lib/mongodb, where mongo stores its data, as it became too much
for the root partition.
-Original Message-
From: pulp-list-boun...@redhat.com [mailto:pulp-list-boun...@redhat.com] On
Same here
/var/lib/pulp/content and /var/lib/pulp/working are symbolic links on
a network volume (provided by Cinder and supported by Netapp storage
bay)
mongo database is also stored on a network volume
On Mon, Dec 15, 2014 at 4:10 PM, Ashby, Jason (IMS) ash...@imsweb.com wrote:
Hi Sean,
What we have now:
- Storage directory defined here [0]
- The above value is used to create a path for working directories here [1]
Proposed changes:
- Add a new config value in the 'server' section called 'working_directory'.
It's default value would be /var/lib/storage
- Change
- Original Message -
- Original Message -
From: Dennis Kliban dkli...@redhat.com
To: pulp-list pulp-list@redhat.com
Sent: Monday, December 15, 2014 2:37:35 PM
Subject: [Pulp-list] working directories proposal
What we have now:
- Storage directory defined here
