Difference between revisions of "Meetings/API-SIG"
< Meetings
(→Next Meeting) |
m (→Agenda) |
||
| Line 23: | Line 23: | ||
** #link https://wiki.openstack.org/wiki/Meetings/API-WG#Agenda | ** #link https://wiki.openstack.org/wiki/Meetings/API-WG#Agenda | ||
* #topic previous meeting action items | * #topic previous meeting action items | ||
| − | ** #link http://eavesdrop.openstack.org/meetings/api_wg/2015/api_wg.2015-11- | + | ** #link http://eavesdrop.openstack.org/meetings/api_wg/2015/api_wg.2015-11-12-00.00.html |
* new topics | * new topics | ||
| − | ** #topic | + | ** #topic Glance image import refactor spec (rosmaita) |
| + | *** #link https://review.openstack.org/#/c/232371/ | ||
| + | *** (it's a big spec, will add specific points I need help with before the meeting) | ||
| + | ** #topic Version discovery (rosmaita) | ||
| + | *** was looking for some info related to a recent Glance patch | ||
| + | *** #link https://review.openstack.org/#/c/244571/ | ||
| + | *** didn't see anything in the API WG repo, but did find this in the wiki: | ||
| + | *** #link https://wiki.openstack.org/wiki/VersionDiscovery | ||
| + | *** just wondering what the API WG's position is on this? i.e., wiki info left out because no one got around to including it yet, or left out because it's controversial? | ||
| + | *** also, the Glance patch referenced above is related to Glance implementing a /versions endpoint ... the wiki doc just says that the 'versions' response should be returned from the base entry point to a service ... is it OK to remove /versions as long as / returns the correct response? (/versions endpoint isn't documented anywhere) | ||
** #topic your topic here | ** #topic your topic here | ||
* #topic guidelines dashboard | * #topic guidelines dashboard | ||
Revision as of 16:08, 17 November 2015
Contents
Weekly API Working Group Meeting
This is a weekly meeting to discuss the OpenStack API. It's intended as a forum for:
- Standardizing the OpenStack project APIs and creating guidelines and rules for projects to follow when designing their REST APIs
- Feedback from users as to the usability of OpenStack REST APIs
- Discussion of future directions of OpenStack APIs
Meetings
- Meeting Time: Weekly, Thursday at 16:00UTC/00:00 UTC (alternating)
- IRC channel:
#openstack-meeting-3 - MeetBot Manual http://meetbot.debian.net/Manual.html
- Chaired by: Jay Pipes | Everett Toews | Any API WG Member
Next Meeting
Thursday 2015-11-19 at 16:00UTC
Agenda
- #startmeeting api wg
- #topic agenda
- #topic previous meeting action items
- new topics
- #topic Glance image import refactor spec (rosmaita)
- #link https://review.openstack.org/#/c/232371/
- (it's a big spec, will add specific points I need help with before the meeting)
- #topic Version discovery (rosmaita)
- was looking for some info related to a recent Glance patch
- #link https://review.openstack.org/#/c/244571/
- didn't see anything in the API WG repo, but did find this in the wiki:
- #link https://wiki.openstack.org/wiki/VersionDiscovery
- just wondering what the API WG's position is on this? i.e., wiki info left out because no one got around to including it yet, or left out because it's controversial?
- also, the Glance patch referenced above is related to Glance implementing a /versions endpoint ... the wiki doc just says that the 'versions' response should be returned from the base entry point to a service ... is it OK to remove /versions as long as / returns the correct response? (/versions endpoint isn't documented anywhere)
- #topic your topic here
- #topic Glance image import refactor spec (rosmaita)
- #topic guidelines dashboard
- #link http://ghostcloud.net/openstack_gerrit_dashboards/dashboard_api-wg.html
- New guidelines to propose for freeze?
- #topic APIImpact
- #endmeeting
