Greetings OpenStack community,
We were joined today by mordred who introduced a stack of documents that describe the
current state of API version discovery, some of the hoops required to do it today, and
the clean way to do it henceforth. There is a ton of information in these proposals
(linked below in the "Under Review" section).
We also discussed how there was only a very light response to edleafe's plea
for people to update the API-WG liaisons [0]. There's not a lot we can do about
this. We'll correct what we know to correct and while we are all fans of active
consensus we'll accept passive agreement.
elmiko and I (cdent) will be at summit, hosting an API-WG BOF session [4].
Please attend if you have the time and interest.
# Newly Published Guidelines
* "Define pagination guidelines" from https://review.openstack.org/#/c/446716/
merged into
http://specs.openstack.org/openstack/api-wg/guidelines/pagination_filter_sort.html
* "Recommend the correct HTTP method for tags" from
https://review.openstack.org/#/c/451536/ merged into
http://specs.openstack.org/openstack/api-wg/guidelines/tags.html and
http://specs.openstack.org/openstack/api-wg/guidelines/http.html
# API Guidelines Proposed for Freeze
Guidelines that are ready for wider review by the whole community.
* Create a set of api interoperability guidelines:
https://review.openstack.org/#/c/421846/
This had been frozen before but it was referring to another guideline that
will not merge for a while so we took that reference out.
# Guidelines Currently Under Review [3]
* Microversions: add next_min_version field in version body
https://review.openstack.org/#/c/446138/
* A suite of five documents about version 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
# Highlighting your API impacting issues
If you seek further review and insight from the API WG, 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 WG mission and the work we do, see OpenStack API
Working Group [2].
Thanks for reading and see you next week!
# References
[0] http://lists.openstack.org/pipermail/openstack-dev/2017-April/115921.html
[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://www.openstack.org/summit/boston-2017/summit-schedule/events/18679/api-working-group-update-and-bof
Meeting Agenda
https://wiki.openstack.org/wiki/Meetings/API-WG#Agenda
Past Meeting Records
http://eavesdrop.openstack.org/meetings/api_wg/
Open Bugs
https://bugs.launchpad.net/openstack-api-wg
--
Chris Dent ┬──┬◡ﾉ(° -°ﾉ) https://anticdent.org/
freenode: cdent tw: @anticdent
__________________________________________________________________________
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
