On 21/09/11 17:45 +0100, Martyn Taylor wrote:
All,
I have put down an initial design for the Image Management API to be
exposed on conductor and used via aeolus-image CLI and Katello.
It's in the wiki, and can be found here:
https://www.aeolusproject.org/redmine/projects/aeolus/wiki/Conductor_Imag...
Thanks
Martyn
_______________________________________________
aeolus-devel mailing list
aeolus-devel(a)lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/aeolus-devel
Martyn and I have been discussing the topic of api data format. Today, we have several
components that interact using XML as the transport data format. Katello will be format
data in JSON, and I think it's reasonable to have a consistent api data format (at
least from the REST apis exposed from conductor). I agree with Geert Jansen's posted
contrast comments re XML vs JSON (referenced by Martyn's design document). By
exposting a consistent data format I think we achieve 1) reducing surprises to the
consuming developer 2) reduce the test coverage needed to ensure the apis are working
correctly 3) appearing as though we are somewhat decisive and organized (which I've
personally never achieved).
The discussion that Martyn and I had resurfaced after a conversation regarding TLD export
data format from Katello as seen here:
http://mmccune.fedorapeople.org/scratch/template-export.png
Should we get work on the backlog to make the api transport data format consistent (ie use
JSON) or should we just continue to be indifferent?
--
Chris