[katello-devel] Katello Backend Service Relationships and Architecture

Partha Aji paji at redhat.com
Thu Dec 6 15:54:31 UTC 2012



----- Original Message -----
> From: "Tom McKay" <thomasmckay at redhat.com>
> To: "Eric D Helms" <ericdhelms at gmail.com>
> Cc: katello-devel at redhat.com
> Sent: Thursday, December 6, 2012 10:45:23 AM
> Subject: Re: [katello-devel] Katello Backend Service Relationships	and	Architecture
> 
> > Candlepin
> > 
> > 
> > - Contains a single Candlepin only model without corresponding
> > inclusion in a Katello entity (OwnerInfo)
> > - Contains some proxied functionality mainly for subscription
> > manager
> > - Not all Candlepin functionality is contained in glue layer
> > - Basic functionality is orchestrated (CRUD)
> > 
> 
> Definitely room for clean-up in the candlepin layer. I would love to
> see us move to align with the clean pulp v2 integration style.
> 
Candlepin used to have something similar to Runcible, a wrapper library for its calls.
We just didn't use em for unknown reasons (may be it was deemed that calling the Rest API directly via url was just as simple as using a wrapper library).

Partha




More information about the katello-devel mailing list