Bug 1386284

Summary: [RFE] Support mounting a share with populated content and allow usage without requiring re-download from network.
Product: Red Hat Satellite Reporter: John Matthews <jmatthew>
Component: PulpAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED DUPLICATE QA Contact: Katello QA List <katello-qa-list>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.2.3CC: bbuckingham, bkearney, bmbouter, daviddavis, dkliban, ggainey, ipanova, mhrivnak, pcreech, rchan, tsanders, ttereshc
Target Milestone: UnspecifiedKeywords: FutureFeature, Reopened, Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-11-21 17:27:11 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On:    
Bug Blocks: 1212602    

Description John Matthews 2016-10-18 14:39:26 UTC 
Description of problem:

In QCI we would like the ability to mount a share with populated content (RPM/Puppet/Docker/etc) and have a means of instructing Satellite to use this content, without requiring a re-sync from a network source.

Our experience has been when we do this, Satellite will ignore the local content on the mount point and re-download the content from the network....not just metadata but all of the content will be fetched from a remote source again, defeating the time savings of using the local volume.

Use case:
1) Deploy a Satellite, configure /var/lib/pulp to be a separate EBS volume in EC2.
2) Sync 200GB of content
3) Create a snapshot the /var/lib/pulp volume
4) Deploy a new Satellite and mount the copied /var/lib/pulp volume
5) Resync content, we would like this to be a quick operation as the majority of the content already exists locally.


(In Pulp v1 we would accomplish this by just copying /var/lib/pulp and remounting it, we are asking for a similar mechanism)
Comment 1 Bryan Kearney 2016-10-18 17:51:33 UTC 
Please check out https://access.redhat.com/articles/1531833
Comment 4 Michael Hrivnak 2016-10-21 17:47:39 UTC 
Documented here:

http://docs.pulpproject.org/user-guide/deferred-download.html#re-using-files-on-disk-when-db-is-lost
Comment 5 pulp-infra@redhat.com 2016-10-23 15:33:26 UTC 
The Pulp upstream bug status is at CLOSED - CURRENTRELEASE. Updating the external tracker on this bug.
Comment 6 pulp-infra@redhat.com 2016-10-23 15:33:29 UTC 
The Pulp upstream bug priority is at High. Updating the external tracker on this bug.
Comment 7 Brian Bouterse 2016-11-21 17:27:11 UTC 
Closing as a duplicate of 1132692. They both refer to the same upstream Pulp issue.

*** This bug has been marked as a duplicate of bug 1132692 ***