[Pulp-list] Configuring pulp-server data storage

[Chris St. Pierre]

We use symlinks, but since we use root_squash on our NFS server it's
not the best solution because then the pulp RPM can't upgrade itself.
That makes the upgrade a manual process (although that's maybe not the
worst thing ever with the quick release cycle...).

If you're not squashing root, then that's not a concern and symlinking
should work fine.

On Mon, Oct 3, 2011 at 10:46 AM, Jay Dobies <jason.dobies at redhat.com> wrote:
> I meant to write that in my last reply (lack of coffee made me forget over
> the course of the two paragraphs I did write).
>
> Our suggestion is either symlinks or mounting to that directory to control
> where the content is actually stored. It's one reason we haven't taken all
> of the steps yet to make that configurable; symlink or mount gives a pretty
> solid amount of flexibility.
>
> On 10/03/2011 10:42 AM, Phil Gardner wrote:
>>
>> Thanks for the quick response. That clears those things up nicely.
>>
>> The reason I was asking about the storage location is because I am
>> trying to use an NFS share to store the repos on. A coworker of mine
>> suggested something that slipped my mind, using a symlink to get around
>> this. Do you see any issues doing it this way? I'm gonna give it a try
>> in a few and will let you know if I run into any issues.
>>
>>
>>
>> On 10/03/2011 10:29 AM, Jay Dobies wrote:
>>>
>>> Currently, it's hardcoded in for the server. Eventually it would be
>>> nice to have that configurable.
>>>
>>> As for pulp and pulp-cds, they are not compatible to be installed on
>>> the same box. It would always have caused a conflict, but recently it
>>> was explicitly added to the CDS RPM spec for these two packages to be
>>> conflicting and not installable on the same instance.
>>>
>>>
>>> On 10/03/2011 10:23 AM, Phil Gardner wrote:
>>>>
>>>> Is it possible to change the location where the pulp-server stores its
>>>> packages and repo stuff? I can see where you control where the CDS
>>>> stores the packages, the 'packages_dir' option in /etc/pulp/cds.conf.
>>>> I'm not seeing any option like that in /etc/pulp/pulp.conf.
>>>>
>>>> It is possible that I have this model mixed up, and the pulp-server just
>>>> takes in the updates and pushes them out to the different CDS servers.
>>>> If this is the case, I have run into a small problem where it appears
>>>> that I am unable to install pulp-server and pulp-cds on the same box.
>>>> This happened with the most recent update.
>>>>
>>>> Reading version lock configuration
>>>> Setting up Install Process
>>>> Resolving Dependencies
>>>> -->   Running transaction check
>>>> --->   Package pulp-cds.noarch 0:0.0.230-3 set to be updated
>>>> -->   Processing Conflict: pulp conflicts pulp-cds
>>>> -->   Processing Conflict: pulp-cds conflicts pulp
>>>> -->   Finished Dependency Resolution
>>>> pulp-cds-0.0.230-3.noarch from rhel-pulp has depsolving problems
>>>>    -->   pulp-cds conflicts with pulp
>>>> pulp-0.0.230-3.noarch from installed has depsolving problems
>>>>    -->   pulp conflicts with pulp-cds
>>>> Error: pulp conflicts with pulp-cds
>>>> Error: pulp-cds conflicts with pulp
>>>>   You could try using --skip-broken to work around the problem
>>>>   You could try running: package-cleanup --problems
>>>>                          package-cleanup --dupes
>>>>                          rpm -Va --nofiles --nodigest
>>>>
>>>> Thoughts?
>>>>
>>>
>>>
>>
>
>
> --
> Jay Dobies
> RHCE# 805008743336126
> Freenode: jdob @ #pulp
> http://pulpproject.org | http://blog.pulpproject.org
>
> _______________________________________________
> Pulp-list mailing list
> Pulp-list at redhat.com
> https://www.redhat.com/mailman/listinfo/pulp-list
>



-- 
Chris St. Pierre