[katello-devel] Katello-Foreman Integration API Layer Question

[Martin Bacovsky]

On 08/22/2012 04:10 PM, Eric Helms wrote:
> Excellent - this is exactly what I was looking for and missed that there was a separate set of API bindings in a gem due to no requires at the top of the file in lib/resources.
>
> Looking closer at the lib/resources/foreman_model.rb this mostly seems like a generic layer for interacting with a set of Ruby API bindings and could be re-purposed to used by any of the glue layers.  Keeping in mind I am pondering this with regards to our migration to Pulp V2 and the re-factoring and work that will be associated with it.  How much in this file is Foreman specific?
>
>   -Eric
You are right, the ForemanModel is pretty generic and could be used for 
any other resources with API bindings. Only the resource method is 
Foreman specific and that would be easy to fix. Im not sure however if 
it is applicable for Candlepin and Pulp as they don't use API bindings 
but just are proxying the requests (someone correct me if I'm wrong).

-Martin


>
> ----- Original Message -----
> From: "Martin Bacovsky" <mbacovsk at redhat.com>
> To: katello-devel at redhat.com
> Sent: Wednesday, August 22, 2012 4:23:10 AM
> Subject: Re: [katello-devel] Katello-Foreman Integration API Layer Question
>
> On 08/22/2012 09:12 AM, Ivan Nečas wrote:
>> On Tue 21 Aug 2012 05:31:43 PM CEST, Eric Helms wrote:
>>> A question after seeing the current progress of the Foreman
>>> integration work around the API layer. This is inspired by some
>>> thoughts we've had around the Pulp v2 migrations.
>>>
>>> Has any thought been given to generating a separate
>>> library/gem/project for the API part? Since this would be a re-usable
>>> component by potentially other communities and present a nice, clean
>>> set of ruby bindings for the Foreman APIs that we could consume (as
>>> well as others).
>> Is this the answer?
>>
>> https://github.com/mbacovsky/foreman_api
>>
>> -- Ivan
> The foreman_api is generated from API documentation using the Apipie
> tool [1]. The tool's other nice feature is that you can generate simple
> CLI client, but as the new API is still far from complete neither we nor
> the foreman community provide one.
>
> The foreman_api is available in git repo [3] (most fresh version is
> usually on the link Ivan provided), as a gem on rubygems.org and also in
> our katello-thirdparty repo as a rpm. It should be available soon as a
> rpm and deb for the Foreman community by their own means.
>
> Here is short wiki [2] on how we use the bindings in katello. If you
> find anything you need to add there, let me know.
>
> Martin
>
> [1] https://github.com/Pajk/apipie-rails
> [2] https://fedorahosted.org/katello/wiki/ForemanIntegrationAPI
> [3] https://github.com/theforeman/foreman_api
>
>
>>> - Eric
>>>
>>> _______________________________________________
>>> katello-devel mailing list
>>> katello-devel at redhat.com
>>> https://www.redhat.com/mailman/listinfo/katello-devel
>>
>>
>> -- 
>> Ivan
>>
>> _______________________________________________
>> katello-devel mailing list
>> katello-devel at redhat.com
>> https://www.redhat.com/mailman/listinfo/katello-devel
> _______________________________________________
> katello-devel mailing list
> katello-devel at redhat.com
> https://www.redhat.com/mailman/listinfo/katello-devel
>
> _______________________________________________
> katello-devel mailing list
> katello-devel at redhat.com
> https://www.redhat.com/mailman/listinfo/katello-devel