On 08/26/11 - 11:06:26AM, Lukas Zapletal wrote:
On 08/25/2011 07:35 PM, Chris Lalancette wrote:
> That being said, the*concept* is much the same, so what you say below is
> still valid.
I guess I understand the format now. However, the next topic I am most
interested in is how are we going to communicate.
My proposal is to extend our template REST API:
GET /api/templates/:id
When you provide content-type set to "application/tdl-xml" it would
return template in TDL XML format.
Information from Katello to Aeolus could go via:
- simple HTTP get link (once we have a SSO)
- via Aeolus API (is there any?)
Well, it depends. I've honestly not followed the Katello/Aeolus integration
that closely yet, so I'm not sure where the integration point is. Is Katello
going to talk to the conductor, or directly to the imagefactory? The conductor
does have a REST API of sorts, though it is pretty limited right now. The
imagefactory is commanded via QMF at the moment, though we are also adding a
REST API to it for the next sprint. So either one will work, it just depends
on what we are trying to accomplish.
--
Chris Lalancette