Story #162
Updated by bmbouter about 9 years ago
h2. The Story +++ This bug was initially created as a clone of "Bugzilla Bug #772336":https://bugzilla.redhat.com/show_bug.cgi?id=772336 +++ /var/lib/ is the appropriate place to store application data. See the Filesystem Hierarchy Standard for details: Description of problem: http://www.pathname.com/fhs/pub/fhs-2.3.html#PURPOSE31 Feature request: As it stands all packages/repos are stored in /var/lib/pulp and I'd like the ability to point these elsewhere. elsewhere (so that my massive packagesets can live on NFS). Right now I have moved /var/lib/pulp and symlinked it back, back but I feel this is not discussed in the docs anywhere. wrong approach and it would be better to just define the package storage location. --- Additional comment from kbidarka@redhat.com at 01/27/2012 07:50:04 --- Somewhere I understand that the below 2 bugs are slightly different but think it would be of great help in this context. https://bugzilla.redhat.com/show_bug.cgi?id=784601(katello) https://bugzilla.redhat.com/show_bug.cgi?id=784519(rhui) In short pulp.spec also needs to handle the docs a new section should be added titled "Storing Pulp content elsewhere". This section should permissions of the custom/separate disks partitions which stores repos/packages. --- Additional comment from mhrivnak@redhat.com at 08/22/2013 15:49:37 --- For this issue, we recommend symlinking to mounted mounting 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 Mounting an NFS device within /var/lib/ is sent to QE it will be just for quite reasonable. Also consider doing a bind mount, which lets you store the verification data on any part of your FS hierarchy you like. /var/lib/ is the documentation produced. The developer is supposed appropriate place to do all symlink testing. h2. Deliverables store application data. See the Filesystem Hierarchy Standard for details: * Perform http://www.pathname.com/fhs/pub/fhs-2.3.html#PURPOSE31 RHEL uses the test described below and create issues FSH as its "authoritative reference": https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Storage_Administration_Guide/s1-filesystem-fhs.html We will certainly consider ways to make it easier for any regressions observed * The new docs section described above. * A release note that Pulp is tested sysadmins to deploy pulp with storage in symlinked environments. non-standard locations. h2. Required Testing --- Additional comment from xdmoon@redhat.com at 07/29/2014 15:10:55 --- 0) Setup a released 2.6.x version Note from attached case 01136189, customer would like to be able to change /var/lib to /var/satellite in satellite 6 for content synchronization. (GSS - when attaching customer cases to RFE BZs let's pls complete the RFE template per step 6 of Pulp on a system https://mojo.redhat.com/docs/DOC-110680#jive_content_id_Red_Hat_Satellite__Proxy, thanks) Xixi --- Additional comment from xdmoon@redhat.com at 08/07/2014 22:55:26 --- RFE review 2014/8/7 with SELinux enabled mmccune/bkearney/cliff/taw: 1) Move /var/lib/pulp Cloned to /var/lib/the_real_pulp 2) symlink /var/lib/pulp Bug 1127809 "[RFE] Ability to /var/lib/the_real_pulp specify a different location to store packages/repos in Satellite 6" to track for some future release of Satellite 6. 3) startup Pulp 4) run the docker-ized integration tests and ensure that all expected tests pass Xixi
.