00:01:24 #startmeeting nova api 00:01:25 Meeting started Fri Sep 19 00:01:24 2014 UTC and is due to finish in 60 minutes. The chair is cyeoh. Information about MeetBot at http://wiki.debian.org/MeetBot. 00:01:26 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 00:01:28 The meeting name has been set to 'nova_api' 00:01:37 Hi! Who is here today? 00:01:42 hello! 00:01:42 good morning! 00:01:46 hi cyeoh. 00:01:59 hi 00:02:31 ok let's get started. 00:02:35 #topic v2 on v3 api 00:03:11 So nothing merging now given the rc is so close but I think we should continue spending some time reviewing the patches we do have 00:03:23 eg. there's a bunch of new network related ones 00:03:36 so when Kilo opens we can merge very quickly 00:03:54 cyeoh: that means revewing with WIPs? 00:04:02 everyone ok with that? (Just ignore the -2's/WIPs on the patches) 00:04:15 oomichi: yea I don't think that will hurt will it? 00:04:15 I'm ok 00:04:30 cyeoh: nice for me 00:04:31 The only patch I have that is WIP that is truly WIP is the extension info one 00:04:52 sounds good 00:04:54 remove WIP of network proxy patch? 00:05:12 eliqiao: don't remove the WIP or they might get -2'd 00:05:30 but when you have time do review any of the v2-on-v3 patches even if they are marked WIP 00:05:42 okay 00:05:50 so hopefully we can get them all cleaned up a ready to merge 00:06:11 cyeoh: we need to post spec for v2.1 kilo 00:06:38 oomichi: I was hoping to just sneak them in :-) 00:06:49 I guess we could just repost the same spec 00:06:58 on https://review.openstack.org/#/c/116699/ discussion, the v2.1 spec will be approved soon after kilo open 00:07:36 cyeoh: yes, right. enough to repost the same spec for kilo, maybe 00:08:16 oomichi: it should be - we'll keep microversions separate 00:08:48 cyeoh: yea, we should separate it for avoiding slow progress :) 00:08:58 will ask PTL & John - perhaps can just get an exemption since its continuing work 00:09:37 cyeoh: sounds nice 00:10:01 anything else on v2 on v3? (will talk about microversions separately) 00:10:31 cyeoh: V2 has 'os-volume_attachments' resource to attach/detach/swap volume and V3 has server action ('attach' etc) for the same 00:11:01 as we need to port 'os-volume_attachments' for V2.1, do we keep V3 version also or remove that? 00:11:01 gmann: hrm v2 doesn't have the attach server action? 00:12:10 did we miss os-volume_attachments? 00:12:33 i think no, V2 has 'os-volume_attachments' no server action. 00:12:43 cyeoh: maybe we missed it. 00:12:48 yes, we missed to port os-volume_attachment 00:13:08 * cyeoh is just looking through his git tree 00:13:26 we can move attach/detach code as os-volume_attachment 00:14:48 alex_xu: yes but as in microversion we might need those API implemented as server action, should not we keep those also and provide os-volume_attachments for backward compatibility 00:16:08 gmann, I just think of share the code attach/detach/swap and os-volume_attachment will complex, so maybe we introduce those action back will more easy 00:16:44 but I'm ok with both way 00:17:01 is the implementation exactly the same? For some reason I remember talking about this before 00:17:13 and I think I ended up deliberately removing the attachment code from volumes.py 00:18:49 ok anyone I think this needs more looking into.... 00:18:56 a lot of different in input/output 00:19:00 can work it out offline I think 00:19:17 yes, request response is main diff 00:19:31 yes, can file a bug then track it 00:20:54 ok, i will release a WIP patch (by keeping V3 server action too) and then we can go for better direction. 00:20:57 yea I think we'll need to re-implement it again 00:20:58 is it ok? 00:21:32 yep thats fine. I think eventually we should just drop the v3 version 00:21:39 I'm fine too 00:21:49 ok. 00:21:52 gmann: thanks for picking that up! 00:22:11 ok anything else for v2 on v3 api 00:22:28 while testing i found some more extension missed like disk_config too. 00:22:51 I will keep updating etherpad about my finding. 00:23:03 gmann: argh :-( Could you put them on the etherpad? And then someone can pick them up. 00:23:04 thanks! 00:23:12 gmann: nice work! 00:23:12 gmann, great job! 00:23:24 sure thanks 00:23:42 hrm config_drive does seem to be ported? 00:24:10 unless for some reason its not loading properly? 00:24:51 anyway can look into it more - but it does appear that there is a v3 version which looks like it implements everything the v2 one does 00:24:55 yeah, config_drive seems to be ported with I8a0d50efcda6fcd12971a41505127de5987eec18 00:25:25 yes, but need to look. is it same with disk_config 00:25:28 on sorry I misread - you said disk_config 00:25:31 gmann: NotFound config_drive with Tempest? 00:26:14 gmann: yes you're right we're missing disk_config 00:26:19 error is 'OS-DCF:diskConfig' not in server body 00:26:37 gmann: sorry, that is a part of SchedulerHints 00:27:05 Ieed7619f3cb310b25d157ebb07f24468aea1af9d is right commit id. 00:28:05 i have added disk_config in etherpad. i will try to release today. 00:28:27 gmann: cool :-) 00:29:02 gmann: thanks, I will see it. 00:29:10 #topic microversions 00:29:27 Alex has some ideas he's mailed out about microversions. 00:29:36 alex_xu: do you want to paste think link to your blog post in here? 00:29:56 There is the blog post 00:29:56 #link http://soulxu.github.io/blog/2014/09/12/one-option-for-nova-api/ 00:30:25 alex_xu: sorry I haven't read the revised version yet but will look at it soon 00:30:37 cyeoh, thanks! 00:31:14 just wondering if anyone else had anything they want to talk about it? 00:31:37 I think it's also fine if we just discuss it via email as well.... 00:32:14 alex_xu: nice doc :-) 00:32:26 cyeoh: I agree, we need time for it. 00:32:33 oomichi, thanks, I also hope got your suggestion 00:32:54 oomichi: ok, fair enough. I know I need to think about it all a bit more myself.... 00:33:35 maybe it would be nice to discuss it on -dev ml 00:33:48 yes, that was really nice doc and POC. I also need to go through it completely. ll provide my input if any 00:34:02 many people will join into the discussion. 00:34:04 gmann, cool, thanks 00:34:21 oomichi: yes we should. alex_xu: do you want to start off an email thread? 00:34:43 cyeoh, sure 00:34:46 I still have strong reservations about parts. eg I don't want a method per version 00:34:47 the doc is already nice for discussing it :-) 00:35:11 because I think that's too much duplicated code, but we can talk about that more 00:35:17 but the doc isn't good for comment... 00:35:55 cyeoh, yea, a lot of thing need more think about 00:36:00 yea a nova-spec is better for discussion but I think its worth sending it out for some general discussions first 00:36:44 yeah, right. we need many opinions. -dev is nice for getting them. 00:37:10 yes, send as nova-spec when we ensure it is ready 00:37:58 alex_xu: thanks 00:38:04 oomichi, np 00:38:41 #topic open discussion 00:39:05 ok, is there anything else people would like to talk about? 00:40:29 one point 00:40:51 can we add v2.1 endpoint setting to devstack now? 00:41:30 as yesterday maling list discussion, v2.1 endpoint is not registered to keystone yet. 00:41:43 oomichi: I don't see why not 00:42:08 it'd be useful for testing 00:42:14 cyeoh: my concern was experimental v2.1 now. 00:42:53 but it is necessary to test/use v2.1 with nova command. 00:43:22 yes, i have to change locally each time i test V2.1 :) 00:43:29 I will try it later anyway :-) 00:44:02 oomichi: i think its fine with it experimental. keystone folks are probably going to complain about yet another versioned endpoint though! 00:44:08 since that's not how its supposed to work 00:44:22 gmann: right, in many cases I use curl command for v2.1 testing. that is not useful for me:-( 00:45:29 cyeoh: nice info, yeah will do it :-) 00:46:36 ok is there anything else? 00:47:09 yeah, good for me now :) 00:47:21 nothing from my side 00:47:41 that's for me 00:48:03 that's all for me 00:48:36 ok thanks everyone! 00:48:50 #endmeeting