Ed Leafe
2018-05-03 17:02:51 UTC
Greetings OpenStack community,
A well-attended meeting today. I'm pleased to report that a good time was had by all.
The discussion centered primarily on the email to the dev list [7] from Gilles Dubreuil regarding the possibility of using GraphQL [8] as a wrapper/replacement for the OpenStack APIs/SDKs. None of us are familiar with GraphQL in more than a cursory way, so we thought it would be best to propose starting with a limited proof-of-concept test. This would involve a team of people interested in GraphQL to work separately to wrap a single OpenStack service, and then, based on the results, either make it something we embrace OpenStack-wide, or chalk up as another interesting experiment. mordred suggested that they use Neutron as the test case, as their API requires a lot of client-side work for many typical queries. edleafe agreed to respond on the mailing list with these thoughts. We also agreed that edleafe needs to be more mindful of his phrasing in emails.
Due to the late interest of Gilles and others, we decided to resurrect our BoF session at the upcoming Vancouver Forum. If you will be there, and you have an interest in anything API- or SDK-related, please plan on joining us!
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
# API Guidelines Proposed for Freeze
Guidelines that are ready for wider review by the whole community.
None
# Guidelines Currently Under Review [3]
* Update parameter names in microversion sdk spec
https://review.openstack.org/#/c/557773/
* Add API-schema guide (still being defined)
https://review.openstack.org/#/c/524467/
* 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
# 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-April/129987.html
[8] http://graphql.org/
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
-- Ed Leafe
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-***@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/
A well-attended meeting today. I'm pleased to report that a good time was had by all.
The discussion centered primarily on the email to the dev list [7] from Gilles Dubreuil regarding the possibility of using GraphQL [8] as a wrapper/replacement for the OpenStack APIs/SDKs. None of us are familiar with GraphQL in more than a cursory way, so we thought it would be best to propose starting with a limited proof-of-concept test. This would involve a team of people interested in GraphQL to work separately to wrap a single OpenStack service, and then, based on the results, either make it something we embrace OpenStack-wide, or chalk up as another interesting experiment. mordred suggested that they use Neutron as the test case, as their API requires a lot of client-side work for many typical queries. edleafe agreed to respond on the mailing list with these thoughts. We also agreed that edleafe needs to be more mindful of his phrasing in emails.
Due to the late interest of Gilles and others, we decided to resurrect our BoF session at the upcoming Vancouver Forum. If you will be there, and you have an interest in anything API- or SDK-related, please plan on joining us!
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
# API Guidelines Proposed for Freeze
Guidelines that are ready for wider review by the whole community.
None
# Guidelines Currently Under Review [3]
* Update parameter names in microversion sdk spec
https://review.openstack.org/#/c/557773/
* Add API-schema guide (still being defined)
https://review.openstack.org/#/c/524467/
* 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
# 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-April/129987.html
[8] http://graphql.org/
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
-- Ed Leafe
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-***@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/