13:00:41 #startmeeting nova api 13:00:42 Meeting started Wed May 11 13:00:41 2016 UTC and is due to finish in 60 minutes. The chair is alex_xu. Information about MeetBot at http://wiki.debian.org/MeetBot. 13:00:43 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 13:00:45 The meeting name has been set to 'nova_api' 13:00:54 who is here today? 13:01:29 * andrearosa lurks 13:01:49 o/ 13:01:51 emm...strange, nobody at here today 13:02:06 as i know, ken'ichi on the travel 13:02:24 o/ 13:02:36 o/ 13:02:40 sorry, was generating new stats for the sprint to put on email 13:02:42 o/ 13:02:48 sdague: np 13:03:00 ok, we have people now, let's start the meeting :) 13:03:27 #topic API priority 13:03:44 let's talk api ref first 13:04:25 sdague: i guess we are good, and maybe we should keep today's meeting short, and back to doc sprint? 13:04:52 alex_xu: yeh, the doc sprint is pretty much the priority this week. I haven't even looked at any of the specs 13:05:12 http://burndown.dague.org/ it's coming along, but it will take a bit 13:05:17 * edleafe shows up late... 13:05:48 ah, that diagram is cool 13:05:59 there are a bunch of changes up for review, we should probably just fix/update reviews that are close when we find issues 13:06:09 a have a quick random question from a review, but I can leave that till open 13:06:11 I was going to go back through the list and do that after the meeting 13:06:12 ++ 13:06:21 johnthetubaguy: no, lets do it now 13:06:43 johnthetubaguy: yea, please go ahead 13:06:45 https://review.openstack.org/#/c/314924/2/api-ref/source/os-hosts.inc@73 13:06:50 sorry creating link 13:06:55 we have two host params 13:07:00 its kinda nested 13:07:08 https://git.openstack.org/cgit/openstack/nova/tree/doc/api_samples/os-hosts/host-get-resp.json#n7 13:07:29 as its an admin API, I am fine ignoring the problem 13:07:38 oh, host / host 13:07:40 just not see that happen before, so its a heads up 13:07:44 yeah 13:07:44 host and host 13:07:52 so... I think you can actually specify it twice 13:07:59 the host at line 68 looks like useless 13:08:01 it's a list 13:08:07 maybe hosts? 13:08:13 oh right, good point 13:08:29 jichen: we can't change the representation, otherwise I would be tempted 13:08:31 I almost anticipated this issue because of nested resources 13:08:40 sdague: :) 13:08:45 johnthetubaguy: ok :) 13:08:46 what we probably should do is actually the following 13:08:49 resource.x 13:08:52 that is just part of structure, no exactly meaning, we needn't list that in the parameters list 13:08:54 for all of these 13:08:57 yeah, I was just thinking about that 13:09:04 they are all the same then 13:09:05 that's what I was doing for complex data in servers 13:09:12 like security_groups.name 13:09:30 because, otherwise, name being in the list twice is super confusing 13:09:44 yeah, that works, when its needed 13:10:57 so, I am happy, lets fix that up 13:11:20 johnthetubaguy great 13:11:20 yes, that is also works. 13:11:33 johnthetubaguy: thanks for catching that 13:12:13 sdague: np 13:12:24 anymore question on the api-ref? 13:12:31 s/anymore/any more/ 13:13:03 FWIW, I thought this was terrible to review, until you have the code open for the API and the samples in another window, and its so much easier 13:13:26 yea 13:13:40 yeh, servers is still a pain, because of all the extensiosn 13:13:46 I can't wait until that's gone 13:13:52 sdague: true, +100 13:14:28 just a note to the docs team, I have no idea how the docs are so good as they are right now! 13:14:36 :) 13:14:59 :) 13:15:07 ok, i think we can move on 13:15:45 for legacy v2 api removing, looks good. just the patches need rebase 13:16:13 after the v2 code removed, we also can begin to clean the policy for legacy v 13:16:36 * mriedem joins late 13:16:42 ah, so looking at this, we totally have a task to clean up our policy rules later on 13:16:50 alex_xu: yeh, let me know when it looks like we're going to be close on the legacy v2 side 13:17:01 the admin_or_owner stuff is very... misleading in how it works today 13:17:04 sdague: ok, got it 13:17:10 as I've got that -2 on the final remove to let everyone pile on for +2 13:17:25 johnthetubaguy: well, that's going to come much later 13:17:36 yeah, once the defaults are in code 13:18:40 ok, next topic? 13:18:40 yeh, as mentioned policy...for the policy discovery, i didn't notice that this week 13:18:59 right, I think that all the specs work is sort of on hold this week to get through as much of the api-ref work as possible 13:19:07 keep folks focussed 13:19:18 yea 13:19:25 next week we should revisit the various specs 13:19:32 sdague: +1 13:19:42 and probably plan to spend this meeting mostly on outstanding specs, including the deprecations ones 13:20:06 +1 13:20:09 do we want to defer any +W on them, till next week? 13:20:48 actually ignore that, regular view process should be fine, I was being over-optimistic 13:20:56 they have -1s anyway 13:21:03 yeah, that would do it 13:21:17 ok, i think we can just to open now 13:21:22 #topic Open 13:21:42 there is one item about "Add support for user defined stop instance" 13:21:50 I can wait for next week 13:22:03 as there are more priority work 13:22:50 people want to talk about it today? or back to doc sprint this week first? 13:22:57 lets focus on doc sprint 13:23:01 the second one 13:23:04 sdague: ok 13:23:08 Kevin_Zheng: thanks 13:23:24 NP, I will try to help on doc tomorrow 13:23:25 keep in mind non-priority spec freeze is in 3 weeks 13:23:47 mriedem: got it, thanks 13:23:50 Kevin_Zheng: thanks again 13:23:59 so we can close the meeting now? 13:24:11 3... 13:24:14 2.. 13:24:18 1. 13:24:22 thanks all! 13:24:25 thanks~ 13:24:26 #endmeeting