[katello-devel] Fwd: Package Profile Upload

[Pradeep Kilambi]

Yea thats fine, we only have one profile set in pulp. But in katello case we'll have both package and hardware i assume, so it makes sense to be explicit.

Yes a list of package dicts is what we pass in to pulp server. So that works.

~ Prad

----- Original Message -----
From: "Devan Goodwin" <dgoodwin at rm-rf.ca>
To: "Pradeep Kilambi" <pkilambi at redhat.com>
Cc: katello-devel at redhat.com
Sent: Monday, July 11, 2011 3:05:48 PM
Subject: Re: [katello-devel] Fwd: Package Profile Upload

On Tue, Jul 5, 2011 at 2:43 PM, Pradeep Kilambi <pkilambi at redhat.com> wrote:
>> Greetings all, is anyone familiar with the planned package profile
>> uploading in Katello? I'm working on the subscription-manager support,
>> just wondering what URL I need to PUT.
>>
>> How does /consumers/{uuid}/packages sound?
>>
>> Cheers,
>>
>> Devan
>
> In pulp we do a PUT on /consumers/<id>/profile/. I assume katello would be
> following the same.
>
> ~ Prad

Ok I used the same URL, but this should be a TODO when this gets
worked on in Katello. It looks like a profile isn't actually a
"resource" that gets persisted to the database as an entity itself,
rather we just save a list of packages? If so trailing with /packages/
might be more clear as far as the API goes. If a profile is actually a
resource in Katello then it makes more sense to me.

I don't think Katello is bound to expose the same API URL as Pulp as
pulp-client won't be talking to Katello (afaik), so it might be a good
time to adjust it if we'd rather use something else.

The code is currently sending a list of package dicts as the JSON in
the request. Does this match pulp-client?

Whoever picks up the implementation to accept the package profile in
Katello feel free to let me know and I can work with to sort out any
issues.

Cheers,

Devan

-- 
 
-- 
Pradeep Kilambi | irc: prad
Red Hat Systems Management
Phone: +1 919 754 4285
RHCE/RHCDS # 805008680430554