[Pulp-list] Repo Sync Filters

[Jake Davis]

So I found some unit copy nice examples here:
http://www.pulpproject.org/2012/06/15/pulp-v2-preview-unit-copy/ Great blog
posts by the way guys!
Also found and interesting example of automating authentication by parsing
the server.conf file... https://github.com/stpierre/pulp-console
Though I am still curious whether I should be concerned about filtering
duplicates from my copy command. I guess I'll play around with it.


On Mon, Jul 1, 2013 at 12:37 PM, Jake Davis <jake at imapenguin.com> wrote:

> Michael,
>
> Thanks for the clarification. I can work with that.
> It brings up a couple of question in regards to automation. In essence I
> will want to do something like copy all units from upstream that are not
> already in testing (minus "kernel-*").  Do I need to manually determine the
> delta between upstream and testing to craft my filter, or is there some way
> to automatically avoid copying duplicate units? Or is the nature of the
> storage such that copying is too cheap to concern ourselves with duplicate
> operations? Examples would be quite valuable :)
>
> Also, I can schedule a sync but not a copy operation. Would I need to pass
> --password on the command line to automate, or is there another way that
> doesn't involve human intervention?
>
> Thanks!
> -Jake
>
>
>
> On Mon, Jul 1, 2013 at 10:18 AM, Michael Hrivnak <mhrivnak at redhat.com>wrote:
>
>> Jake,
>>
>> We don't yet support the idea of applying filters during a sync operation
>> except that you can exclude an entire type. For example, you can exclude
>> all drpms. We intend to provide better sync-time filtering in the future.
>>
>> For now you can do a normal sync of "upstream", and then create "testing"
>> as an empty local repo into which you copy units from "upstream". The copy
>> operation gives you the ability to do powerful filtering, so it should meet
>> your needs.
>>
>> Michael
>>
>> ----- Original Message -----
>> From: "Jake Davis" <jake at imapenguin.com>
>> To: pulp-list at redhat.com
>> Sent: Monday, July 1, 2013 10:05:50 AM
>> Subject: [Pulp-list] Repo Sync Filters
>>
>> Greetings,
>>
>> I'd like to "clone" a repository and then sync from the origin while
>> applying a filter. For example, let's say I have a repo called "upstream"
>> which will serve as the origin. I'd like to create a new repo called
>> "testing" that pulls everything from upstream with the exception of rpms
>> that match "kernel-*". Is such a workflow currently supported in pulp
>> (2.1)? If so, what's the best way to achieve it? Create an empty repo with
>> no --feed and use copy operations? Or create a repo whose --feed url is
>> that of my local copy of "upstream"?
>>
>> Thanks,
>> -Jake
>>
>>
>> _______________________________________________
>> Pulp-list mailing list
>> Pulp-list at redhat.com
>> https://www.redhat.com/mailman/listinfo/pulp-list
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/pulp-list/attachments/20130702/67e93658/attachment.htm>