Project

Profile

Help

Story #162

closed

As a user I have docs about how to store packages/repos content in another areas of the filesystem

Added by apenney@gmail.com about 9 years ago. Updated over 3 years ago.

Status:
CLOSED - WONTFIX
Priority:
Normal
Assignee:
-
Category:
-
Sprint/Milestone:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Platform Release:
Groomed:
Yes
Sprint Candidate:
No
Tags:
Documentation, Pulp 2
Sprint:
Quarter:

Description

The Story

/var/lib/ is the appropriate place to store application data. See the Filesystem Hierarchy Standard for details:

http://www.pathname.com/fhs/pub/fhs-2.3.html#PURPOSE31

As it stands all packages/repos are stored in /var/lib/pulp and I'd like the ability to point these elsewhere. Right now I have moved /var/lib/pulp and symlinked it back, but this is not discussed in the docs anywhere.

Somewhere in the docs a new section should be added titled "Storing Pulp content elsewhere". This section should recommend symlinking to mounted dedicated storage either at /var/, /var/lib/, or /var/lib/pulp/. Also note that mongo can quickly use many GB of storage, so consider making plenty of storage available at /var/lib/mongodb/.

When this is sent to QE it will be just for the verification of the documentation produced. The developer is supposed to do all symlink testing.

Deliverables

  • Perform the test described below and create issues for any regressions observed
  • The new docs section described above.
  • A release note that Pulp is tested in symlinked environments.

Required Testing

0) Setup a released 2.6.x version of Pulp on a system with SELinux enabled
1) Move /var/lib/pulp to /var/lib/the_real_pulp
2) symlink /var/lib/pulp to /var/lib/the_real_pulp
3) startup Pulp
4) run the docker-ized integration tests and ensure that all expected tests pass

Also available in: Atom PDF