Greetings OpenStack community,
Today's meeting was primarily focused on a request for guidance related
to action endpoints and on planning topics for the upcoming PTG.
Tommy Hu has sent an email to the developer list[7] describing how
several types of actions are currently being handled through the cinder
and nova REST interfaces. In specific this is related to how APIs are
registered with a gateway service. The current methodology within cinder
and nova has been to use generic action endpoints, allowing the body of
the request to further define the action. These overloaded endpoints
cause difficulty when using an API gateway. The SIG has taken up
discussion about how this could be improved and what guidance can be
created for the community. Although no firm plan has been derived yet,
the SIG will join the conversation on the mailing list and also discuss
the wider topic of actions at the PTG.
On the topic of the PTG, the SIG has created an etherpad[8] where agenda
items are starting to be proposed. If you have any topic that you would
like to discuss, or see discussed, please add it to that etherpad.
As always if you're interested in helping out, in addition to coming to
the meetings, there's also:
* The list of bugs [5] indicates several missing or incomplete guidelines.
* The existing guidelines [2] always need refreshing to account for
changes over time. If you find something that's not quite right, submit
a patch [6] to fix it.
* Have you done something for which you think guidance would have made
things easier but couldn't find any? Submit a patch and help others [6].
# Newly Published Guidelines
None this week.
# API Guidelines Proposed for Freeze
Guidelines that are ready for wider review by the whole community.
None this week.
# Guidelines Currently Under Review [3]
* Add guideline on exposing microversions in SDKs
https://review.openstack.org/#/c/532814/
* A (shrinking) suite of several documents about doing version and
service discovery
Start at https://review.openstack.org/#/c/459405/
* WIP: microversion architecture archival doc (very early; not yet ready
for review)
https://review.openstack.org/444892
* WIP: Add API-schema guide (still being defined)
https://review.openstack.org/#/c/524467/
# Highlighting your API impacting issues
If you seek further review and insight from the API SIG about APIs that
you are developing or changing, please address your concerns in an email
to the OpenStack developer mailing list[1] with the tag "[api]" in the
subject. In your email, you should include any relevant reviews, links,
and comments to help guide the discussion of the specific challenge you
are facing.
To learn more about the API SIG mission and the work we do, see our wiki
page [4] and guidelines [2].
Thanks for reading and see you next week!
# References
[1] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[2] http://specs.openstack.org/openstack/api-wg/
[3]
https://review.openstack.org/#/q/status:open+project:openstack/api-wg,n,z
[4] https://wiki.openstack.org/wiki/API_SIG
[5] https://bugs.launchpad.net/openstack-api-wg
[6] https://git.openstack.org/cgit/openstack/api-wg
[7]
http://lists.openstack.org/pipermail/openstack-dev/2018-January/126334.html
[8[ https://etherpad.openstack.org/p/api-sig-ptg-rocky
Meeting Agenda
https://wiki.openstack.org/wiki/Meetings/API-SIG#Agenda
Past Meeting Records
http://eavesdrop.openstack.org/meetings/api_sig/
Open Bugs
https://bugs.launchpad.net/openstack-api-wg
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
