Open Stack

Another thing to consider is how would you write a heat resource to consume the new api. Usually you can find api problems while considering this case. Heat's resources are very light weight to implement if the api is good. Quite difficult when not.

Thanks,
Kevin

________________________________
From: Everett Toews
Sent: Tuesday, June 23, 2015 6:58:52 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [api][Solum] Request for feedback on new API resource

On Jun 18, 2015, at 3:07 PM, Devdatta Kulkarni <devdatta.kulkarni at RACKSPACE.COM<mailto:devdatta.kulkarni at RACKSPACE.COM>> wrote:

Hi, API WG team,

In Solum, recently we have been working on some changes to our REST API.

Basically, we have introduced a new resource ('app'). The spec for this has been accepted by Solum cores.
https://github.com/stackforge/solum-specs/blob/master/specs/liberty/app-resource.rst

Right now we have a patch for review implementing this spec:
https://review.openstack.org/#/c/185147/

If it is not too much to request, I was wondering if someone from your team can take a look
at the spec and the review, to see if we are not violating any of your guidelines.

Thank you for your help.

- Devdatta

Do you have this API documented anywhere?

Is there a spec or similar for this API change?

In our experience, it’s best to consider the API design apart from the implementation. The separation of concerns makes for a cleaner review and a better design. The Glance team did a good job of this in their Artifact Repository API specification [1].

Regards,
Everett

[1] https://review.openstack.org/#/c/177397/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150623/4710a0bf/attachment.html>