12:00:09 #startmeeting nova api 12:00:10 Meeting started Tue Feb 16 12:00:09 2016 UTC and is due to finish in 60 minutes. The chair is alex_xu. Information about MeetBot at http://wiki.debian.org/MeetBot. 12:00:12 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 12:00:14 The meeting name has been set to 'nova_api' 12:00:28 who is here today? 12:00:30 o/ 12:00:41 hi 12:01:10 super quite recently 12:01:25 I guess due to ops meetup? 12:01:55 o/ 12:02:21 February is a dreary month in the norther hemisphere... 12:02:40 For the concept doc, all the existed patch already merged 12:03:04 cdent: ok... 12:03:18 make people tired and quite :) 12:03:26 cdent: :) 12:03:29 :) 12:04:09 :) 12:04:14 I remember johnthetubaguy already closed the concept doc bp, but I think people still can free feel to add more doc 12:04:29 alex_xu: +1, nice work 12:04:39 #topic API futures - patches for approved specs 12:04:49 any patches we want to discussion? 12:05:28 For the allow server_id param as DB index 12:05:59 agree with gmann_ and sdague should check ec2 first 12:06:27 alex_xu: yea at first glance i grep into ec2 repo, so there their use uuid 12:06:35 if ec2 didn't depend on that, I think we can remove that totally and without microversion, as there isn't a way to get that 'id' from nova api 12:06:50 o/ 12:06:55 gmann_: cool, thanks 12:06:55 but we need to completely check their usage from external API too 12:07:12 it might be an some extended response 12:07:19 I though that's what 2.4 was all about 12:07:40 oops, I may only check the 2.1 12:07:59 that being said, it's not as easy to remove as you think, the get_id assumes either numeric or uuid at a very early stage in the code 12:08:00 sdague: you mean 2.3 12:08:05 gmann_: yeh, 2.3 12:08:20 it was one of the first microversions 12:08:25 yea 12:10:23 #link https://github.com/openstack/nova/blob/master/doc/api_samples/os-extended-server-attributes/v2.3/server-get-resp.json 12:10:35 I didn't find out one field for that id 12:11:37 sdague: what is 'get_id' point to? 12:12:19 i also remember we do not put that in response 12:12:23 #link https://github.com/openstack/nova/blob/master/nova/api/openstack/compute/views/servers.py#L107 12:13:11 but it still worth for checking to find out why ec2 needn't that for now 12:13:59 yea 12:14:07 https://github.com/openstack/nova/blob/dbdf27021cc23bf8cec8d3f51fa03c6dac5da53a/nova/compute/api.py#L1939 12:14:28 that's where pretty deep in the compute api we go a lot of different directions 12:15:30 sdague: you mean there may have code still use compute_api.get with id in nova code? 12:15:46 yes 12:16:13 because this is pretty deep in the code, the fallout could be a pretty big deal to unwind 12:16:18 ok, let's double check it 12:16:32 I consider this a really low priority issue to address 12:16:39 yeah, I did a quick check on this, network related functions used it 12:16:41 yes 12:16:45 +1 12:16:51 it didn't hurt anything 12:16:54 sdague: yea, we can do later.+1 12:16:57 https://bugs.launchpad.net/nova/+bug/1522536 12:16:58 Launchpad bug 1522536 in OpenStack Compute (nova) "500 error returned from server GET by numeric id" [Undecided,Confirmed] - Assigned to Sriteja (sriteja-alapati) 12:17:03 so this bug should be invalid ?Just saw it 12:17:11 jichen: that's a little different 12:17:17 because we're getting a 500 12:17:45 sdague: yeah, actually I also got 500 when I did test 12:18:35 I think that's just because we're not checking if the instance is really found 12:19:07 sdague: yea from cache 12:19:24 ok 12:19:53 anyway, that's a real bug to be fixed, and I think it's because something is not entirely safe in the db fetch 12:20:17 I guess it due to we save the instance into the case with uuid, not the id? 12:20:19 jichen: I'd start with a new test case in tree for that 12:20:48 sdague: ok, will take a look ,thx 12:20:51 no, I think it's an assumption in the code that get_by_id isn't going to fail on a context check 12:21:51 ok 12:22:59 ok, I think we are done this problem, anymore want to bring up? 12:23:37 if no, let's jump to open 12:24:00 #topic open 12:24:27 let's talk about newton ideas? 12:24:50 alex_xu: can we discuss tempest microversion before that 12:25:22 unfortunately johnthetubaguy and ken'ichi isn't here today 12:25:24 gmann_: sure 12:25:34 sdague: as discussed, i submitted patch for using fixture for microversion setting 12:25:40 #link https://review.openstack.org/#/c/279430/ 12:25:48 if you can have look 12:25:59 gmann_: ok, cool. I'll look today 12:26:13 mtreinish is proposing that tempest-lib spins back into tempest 12:26:13 sdague: Thanks. 12:26:22 sdague: yea 12:26:22 that will make some of this easier 12:26:38 sdague: yea that will be really helpful for miceroversion testing 12:26:55 sdague: m also almost +2 on that patch 12:27:01 gmann_: sdague, a question, which microversion we will test in the tempest? 12:27:31 alex_xu: All but with specific tests for that microversion 12:27:40 right, what gmann_ said 12:27:46 gmann_: ok, got it, thanks 12:28:03 so for projects that need specific microversions tested we'll have dedicated tests for those (especially ones with behavior changes) 12:28:05 alex_xu: example v2,2 - https://github.com/openstack/tempest/blob/master/tempest/api/compute/keypairs/test_keypairs_v22.py 12:28:12 we probably late on lastest version a lot 12:28:19 sdague: yea 12:29:11 gmann_: cool 12:29:26 alex_xu: yea, at end we would like to run a experimental job running with latest to check any version tests missing etc. 12:31:07 alex_xu: that's all on this, we can move to next topic 12:31:59 sorry for unstable network... 12:32:33 sdague: do you want to talk about newtown idea today? 12:33:02 or just wait johnthetubaguy and ken'ichi at here someday 12:33:14 let's postpone until next week when they are back 12:33:20 we're not really in a rush on it 12:33:26 ok 12:33:38 yea, Ken'ichi shifted to USA last week 12:33:50 gmann_: ah, that's cool 12:34:09 I can't catch him in my working time anymore :( 12:34:20 :), me too 12:34:28 so...no more from today, anyone have more bring up today? 12:34:44 s/no more from/no more from me/... 12:35:00 nothing from my side 12:35:06 3... 12:35:06 no, I'm good for now 12:35:13 0.. 12:35:31 ok, let's close the meeting early today, thanks all! 12:35:34 thanks 12:35:36 Thanks all 12:35:40 #endmeeting