16:00:24 #startmeeting api wg 16:00:37 Meeting started Thu Oct 8 16:00:24 2015 UTC and is due to finish in 60 minutes. The chair is etoews. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:00:38 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 16:00:41 The meeting name has been set to 'api_wg' 16:00:50 o/ 16:00:50 hi 16:00:54 hola 16:01:50 bye 16:01:56 just adding something to agenda... 16:02:42 #topic agenda 16:02:51 #link https://wiki.openstack.org/wiki/Meetings/API-WG#Agenda 16:03:11 if anybody wants to add something, now is a good time ;) 16:03:18 * cdent looks 16:03:41 #topic previous meeting action items 16:03:53 #link http://eavesdrop.openstack.org/meetings/api_wg/2015/api_wg.2015-09-24-16.00.html 16:05:02 hmm, i failed to complete my action item =( 16:05:20 ¯\_(ツ)_/¯ 16:05:25 hehe 16:05:39 the world kept turning :) 16:05:47 good point ;) 16:06:07 did you still want to do it or just drop it? 16:06:20 i'll still do it, just needed a good reminder 16:06:32 unless someone else wants to take it 16:06:34 care to action item yerself? 16:06:38 sure 16:06:51 #action elmiko to make PR against http://docs.openstack.org/infra/manual/developers.html to add info about the openstack-api irc channel 16:06:55 I noticed a slowdown in the turning of the earth recently. It was a near miss. 16:07:04 haha 16:07:18 would like to get help with a guideline to need to increase the limit on hours per day. I suspect that we might be able to leverage this 16:07:29 yes 16:07:31 +1 16:07:34 stevelle++ 16:07:42 #topic Magnum 16:07:59 #link https://swaggerhub.com/api/etoews/OpenStack-Magnum/1.0 16:08:12 that looks nice 16:08:14 that is 100% not my work ^ 16:08:28 entire credit to jamie hannaford and annegentle 16:08:41 and really it's 90% Jamie :) 16:08:46 i just threw it out on swaggerhub to share with others 16:09:36 i've been having an email chat with adrian otto (magnum ptl) about getting a liaison from them 16:10:08 now that we have an api ref for magnum, i think it would be good to get some more api wg eyeballs on it 16:10:25 and have a liaison to work with us on any feedback 16:10:56 I see it continues the openStack pattern of url commands 16:11:11 i noticed that too 16:11:35 but we don't have a guideline for such a thing 16:11:37 :( 16:11:54 stevelle? 16:12:21 etoews: +1 for more engagement with magnum 16:12:21 say more about that stevelle, what do you mean? 16:12:30 oh I found it: pause, unpause, stop etc 16:12:34 cdent: ah ok 16:12:44 stevelle: is that what you mean? 16:12:45 re: /containers/{identifier}/start 16:12:48 etc 16:12:51 ok 16:13:11 that's still better than tunneling imo 16:13:39 we have had discussions in the WG before about this but it was a while ago 16:13:52 i vaguely recall... 16:14:30 i think miguelgrinberg had an strong opinion on how actions should be done in an api 16:14:36 unless the API was actually fully designed to use a CQRS pattern, this ends up being not as RESTful as it could be, and it's spreading 16:14:57 yes, he was one who spoke about it strongly. 16:15:07 yeah 16:16:12 miguelgrinberg: do you have the time/interest to do a guideline for actions? 16:17:06 I could, but I expect it will not be easy to agree on this topic 16:17:24 i agree it will not be easy to agree on 16:17:42 I'll probably soften my approach a bit, take what some of the APIs do instead of just propose what I would do from sctratch 16:17:55 probably a wise idea ;) 16:17:55 but certainly the /start /stop have to go 16:18:01 +1 16:18:40 Okay, I'll give it a try 16:19:11 #action miguelgrinberg to begin a guideline for actions 16:19:19 many thanks miguelgrinberg 16:20:51 etoews: it should be fun :) 16:20:58 #action etoews to get a api wg liaison from magnum 16:21:30 #action etoews annegentle to figure out how to best collaborate on the magnum api ref 16:21:59 boom. drive by action item on annegentle. 16:22:26 anything else on magnum? 16:22:31 lol 16:23:26 #topic links 16:24:16 * etoews searches meeting minutes 16:24:49 heh I'll take it. 16:24:54 is this about the embedded links href vs ref issue? 16:25:22 yes 16:25:34 i know we discussed it in the recent past but can't find it 16:25:43 cool, i've started to analyze the openstack apis, but it's been slow going. 16:25:55 i am working on creating a list of all references though. 16:26:48 elmiko: what are you doing to analyze? 16:27:03 mainly grepping through the api-ref site 16:27:11 well, the source wadls 16:27:31 i had envisioned just searching through http://developer.openstack.org/api-ref.html and copying examples of how people are doing links into https://wiki.openstack.org/wiki/API_Working_Group/Current_Design 16:27:53 ok, maybe i'm going about this in an inefficient manner then 16:27:59 gotcha. that was pretty much what i had in mind. 16:28:08 yeah either way should work elmiko 16:28:26 should i keep going and post my results on the wiki then? 16:29:16 sure 16:29:30 i'd say post them as soon as you discover them. 16:29:35 put it on this page https://wiki.openstack.org/wiki/API_Working_Group/Current_Design/Links ? 16:29:51 yea, that's probably smart 16:30:12 y 16:30:13 i'll start posting them by service then 16:30:19 sorry for the delay 16:30:54 np. 16:31:07 gonna escalate this on my trello ;) 16:31:23 then we can do some analysis ala https://wiki.openstack.org/wiki/API_Working_Group/Current_Design/Metadata#Analysis 16:31:37 yea, i figured that was the end goal 16:31:53 miguelgrinberg: i just discovered/remembered https://wiki.openstack.org/wiki/API_Working_Group/Current_Design/Actions 16:32:07 there's some fodder for the action guideline 16:32:31 although it doesn't include any examples of the /start /stop stuff 16:32:51 etoews: ah, great, didn't know about that. It's useful, the nova style is what I was thinking would work well for openstack 16:33:04 and it does support the start/stop actions already 16:34:50 elmiko: need an action item for the links thing? 16:35:01 sure 16:35:21 #action elmiko create analysis of link references for each service in api-ref 16:35:30 thx 16:35:40 #topic guidelines dashboard 16:35:50 #link http://ghostcloud.net/openstack_gerrit_dashboards/dashboard_api-wg.html 16:36:05 this one https://review.openstack.org/#/c/214817/ seems like it might be ready for freeze 16:36:36 https://review.openstack.org/#/c/221163/ too 16:37:12 y and y 16:37:27 do you want to +2 them? 16:37:34 sure 16:37:47 also, have the dashboard been updated with our recent process change? 16:38:11 #action etoews to freeze https://review.openstack.org/#/c/214817/ and https://review.openstack.org/#/c/221163/ 16:38:21 ty 16:38:24 elmiko: which change is that? 16:38:52 using +2 as the freeze marker, or did we do that awhile ago /me forgets 16:39:29 * etoews goes to check 16:39:53 yep. step #4 http://specs.openstack.org/openstack/api-wg/process.html 16:40:20 ok, cool. and it looks like the dashboard reflects too. thanks =) 16:40:39 anything we need to do to move https://review.openstack.org/#/c/187112/ along? 16:40:56 cdent: you have the last comment there. 16:41:10 * cdent looks 16:41:35 do you think it needs that explanation before it can merge? 16:41:52 Yeah, I intentionally did not leave a vote on with that comment, was just reflecting my own reaction to all the microversion discussions I've seen on the mailing list and elsewhere 16:41:53 i think we need some grammar cleanup on that one too (as i see draft comments of mine) 16:42:20 I think it is okay (with grammar tidy) to move it in, and then revise later if possible 16:42:38 agreed, content-wise it seemed ok 16:42:43 In the sense that the microversion ship has sailed far enough that we dont' want to real it in 16:42:51 (despite the fact that I think it is completely the wrong way to do things ;) ) 16:42:53 sorry, i should have said before we *freeze* it 16:43:03 s/real/reel/ 16:43:11 it needs cleanup before freeze 16:43:20 cdent keeps it reel 16:43:25 lol 16:43:37 /o/ 16:43:39 \o\ 16:43:45 /o/ 16:44:12 that goes so well with the music i am listening to 16:44:43 heh 16:44:53 elmiko: can you comment there on the grammar stuff and when it's ready, go through the freeze process? 16:45:04 etoews: yes 16:45:41 #action elmiko comment on https://review.openstack.org/#/c/187112 and freeze when ready 16:47:16 any other guidelines to dive into? 16:47:34 nothing from me 16:48:20 #topic APIImpact 16:48:31 #link https://review.openstack.org/#/q/status:open+AND+(message:ApiImpact+OR+message:APIImpact),n,z 16:49:55 anything anyone wants to highlight? 16:54:27 i realize that i forgot to add this to the agenda, but could we talk about summit for a few? 16:54:49 #topic summit 16:54:56 thanks 16:55:00 #link https://etherpad.openstack.org/p/mitaka-api-wg-session-plans 16:55:14 just wanted to link this again, as i could use some assistance filling out the agenda for our meeting 16:55:37 elmiko: please hassle me to help you with that 16:55:39 sure. 3.3 is my axe to grind. :) 16:56:00 I've been sort of all around the place lately but should be fairly present in the week running up to summit 16:56:02 cdent: noted, increasing cdent.hassle_factor 16:56:16 cool, i just wanted to bring it up again 16:56:33 i imagine some of my 12hr flight will be spent finalizing these pads 16:57:05 but, you know, many hands and all... ;) 16:59:15 if there's nothing else, we can pack it in a whole minute early. 16:59:19 that was all i had, thanks for any contributions folks want to add there =) 16:59:27 and cdent, i'll bug you some next week 16:59:37 cool, please and thank you 16:59:49 etoews: +1 17:00:02 #endmeeting