13:01:01 #startmeeting openstackclient 13:01:02 Meeting started Thu Jun 30 13:01:01 2016 UTC and is due to finish in 60 minutes. The chair is rtheis. Information about MeetBot at http://wiki.debian.org/MeetBot. 13:01:03 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 13:01:05 The meeting name has been set to 'openstackclient' 13:01:10 #topic releases 13:01:22 Looks like we have osc-lib 0.2.0 13:01:27 o/ 13:01:27 #link https://github.com/openstack/osc-lib/releases/tag/0.2.0 13:01:48 Next step is getting to osc 3.0 13:02:19 the fix i had for looking up by ID (without kwargs) is merged 13:02:22 Last week we discussed tangchen's IP commands as one item needed for 3.0 13:02:39 stevemar: nice 13:03:05 stevemar: so we probably want another osc-lib release 13:03:10 ? 13:03:16 rtheis: yep, it's the only one fix: https://github.com/openstack/osc-lib/compare/0.2.0...master 13:03:49 rtheis: we need that since osc would have a regression otherwise 13:04:28 sure, does dtroyer or dhellmann handle the release? 13:04:37 I'm not sure the process for that 13:04:58 rtheis: any one of us can submit a patch to https://github.com/openstack/releases to release it 13:05:16 0.3.0 or 0.2.1 for this? 13:05:20 if the PTL doesn't submit it, he still needs to +1 it 13:05:33 i'd say 0.2.1 -- it's just a bug fix 13:05:37 okay, I can look at submitting a patch set 13:05:52 #action rtheis submit patch for 0.2.1 osc-lib release 13:06:15 cool, dhellmann or dims will look at it 13:06:22 Anything else for osc-lib? 13:06:26 nope 13:06:34 #link https://review.openstack.org/#/c/300388/ 13:06:45 This is tangchen's IP command series start 13:06:50 I think they just need a rebase 13:07:21 and nothing new on role list patches 13:07:42 #link https://review.openstack.org/#/c/283554/ 13:07:46 #link https://review.openstack.org/#/c/311460/ 13:07:57 i can look at tang's stuff today 13:08:04 thanks stevemar 13:08:23 anything else for osc 3.0 release? 13:08:33 not AFAICT 13:08:44 #topic reviews 13:08:52 any reviews that need attention? 13:09:00 I can help to review tomorrow 13:09:01 do we want to wait for the roles stuff to merge before 3.0.0'ing? 13:09:34 stevemar: that was my understanding from last week 13:09:51 yeah, i guess we should 13:10:00 it'll give us some more time to find bugs :) 13:10:06 indeed :) 13:10:18 the puppet guys are running off of master 13:10:22 crazy folks 13:10:42 (osc master) 13:10:53 yes 13:11:31 #topic bugs 13:11:42 any bugs to discuss? 13:12:05 i can't think of any, we should totally have a bug triage day :P 13:12:13 the list is getting long 13:12:13 I have one 13:12:21 https://bugs.launchpad.net/python-openstackclient/+bug/1596511 13:12:21 Launchpad bug 1596511 in python-openstackclient "``volume type unset`` does not accept multiple "--property " arguments" [Medium,In progress] - Assigned to sunyajing (yajing-sun) 13:12:23 stevemar: yes the list is getting long 13:12:40 might we should merge osc part before cinderclient part is merged 13:13:27 RuiChen: so a cinderclient patch is required first? 13:13:28 i think we have to wait for a fix for cinderclient :( 13:13:35 then we need to wait 13:14:17 i have a bug -- one sec 13:14:19 ok, I try to push cinder team 13:14:32 hi 13:14:34 RuiChen: thank you 13:14:49 https://bugs.launchpad.net/python-openstackclient/+bug/1592906 13:14:49 Launchpad bug 1592906 in python-openstackclient "ensure all delete commands can take multiple objects" [Medium,In progress] - Assigned to aohuanxuan (huanxuan-ao) 13:15:01 someone want to do multi-delete for identity commands? :) 13:15:19 looks like that is making good progress 13:15:32 stevemar: is identity the last remaining commands to fix? 13:15:49 i did the volume ones, huanxuan did the compute ones 13:16:01 and network should be done 13:16:20 yep 13:16:26 oh huanxuan did the identity v2 ones too! 13:16:39 sounds great! 13:16:44 is huanxuan planning to do v3? 13:16:58 rtheis: i don't know his irc handle :( 13:17:14 me either 13:17:23 i think aohuanxuan 13:17:29 i think we just want: ec2creds, service, credential, and domain 13:17:43 the other stuff can wait 13:17:59 well, if i'm putting them in order of importance :) 13:18:10 stevemar: sounds good, maybe you could update the bug report and let aohuanxuan know 13:18:15 yep 13:18:18 thanks 13:18:40 ill try and triage the bugs over the weekend 13:18:47 i'm off on fri and mon 13:19:12 okay, i'm off on monday for the us holiday 13:19:31 any other bugs 13:20:04 aohuanxuan, tangchen and I will work together for China OpenStack bug smash in next week 13:20:05 rtheis: nothing critical, just a lot of un-triaged 13:20:13 RuiChen: nice! 13:20:17 ++ 13:20:21 thank you RuiChen 13:20:21 I think we can clean some bugs :-) 13:20:32 RuiChen: i'm positive you three can! 13:21:07 thanks 13:21:10 #topic open discussion 13:21:26 any other topics to discuss? 13:21:50 https://review.openstack.org/#/c/310193/ 13:22:06 --all-property or --all-properties :) 13:22:11 ah, yes ;) 13:22:29 I was hoping to let dtroyer make the call on that 13:23:05 at a first look, 'all-properties' (plural form) sounds natural too me. 13:23:12 --all-properties makes sense (when you say it out loud) 13:23:21 I had send email to him about these, but no replay :( 13:23:28 agreed 13:24:03 I think the trouble comes when we have to make other names plurals 13:24:08 beyond "property" 13:24:27 is there any consensus on '--no-' vs '--no-'? 13:24:29 it is similar one. 13:24:53 --no- is the consensus 13:25:00 at least in the devref 13:25:20 exactly 13:25:34 thanks 13:26:24 what is the other use of it? --no-? 13:27:27 So we would have --property, --no-property and --all- 13:27:34 I'm not sure if we have other usages 13:28:13 I proposed --each-property as an alternative but not sure if I like that 13:28:50 it reads better but "each" is not intuitive to me anyway 13:29:19 "unset --each-property" sounds good to me 13:30:21 "unset --all-properties" sounds better to me because a command unsets all properties. 13:30:38 oh we should probably talk about https://review.openstack.org/#/c/295026/ too 13:30:49 i think we use 'each' when we do something for 'each' thing. 13:31:02 maybe we continue discussion in the devref and give dtroyer time to respond 13:31:11 sorry in the code review 13:31:52 stevemar: yes that's another one 13:32:10 that cinder command is odd and I'm starting to like RuiChen's idea 13:32:52 rtheis: i think that's a good idea for the --no-? --each-? 13:33:01 whats RuiChen's idea? 13:33:11 my gut told me a different command from the beginning 13:33:20 we're going to try and display a list in a list 13:33:39 see his latest comment in https://review.openstack.org/#/c/295026/ 13:34:07 I have no idea about --each-property or --all-properties, both good to me :) 13:35:22 reading 13:35:53 does "cinder type-access-list" work without a --volume-type argument? 13:35:57 in https://review.openstack.org/#/c/295026/ , I think we can add access info into volume type object in show command 13:36:10 stevemar: it doesn't appear to 13:36:32 but I haven't checked the API 13:36:35 stevemar: no, --volume-type is required in cinderclient 13:36:40 i'd say "list" in cinderclient was incorrectly named .... 13:37:01 adding it to volume type show sounds good to me 13:37:08 we can show a list in a single command 13:37:17 just like we do with properties 13:37:37 stevemar: do we have any similar examples for this in other commands? 13:38:12 meaning show pulls in additional properties to display for a resource 13:38:15 rtheis: i'm positive we do 13:38:43 thanks 13:39:19 looks like cinder API requires volume type to show access: http://developer.openstack.org/api-ref-blockstorage-v2.html 13:40:52 If anyone has an example to share with sheel in the review, I think that would be good. I can take a look too 13:41:09 i am looking for one too 13:41:26 anything else to discuss on these 2 reviews? 13:41:34 speaking of sheel and the volume commands, it looks like he's slowed down, maybe more $day_job for him 13:41:50 yeah 13:42:08 we should probably pick up the slack a bit with the volume commands 13:43:00 any other topics? 13:43:25 let's have a midcycle :P 13:43:43 hawaii might be nice 13:43:53 :) 13:44:04 stevemar: has osc had a midcycle in the past? 13:44:04 it's right between us and RuiChen and tangchen :) 13:44:12 indeed 13:44:25 +1 for hawaii :) 13:44:40 rtheis: we have not, it was dtroyer and myself for the longest time 13:44:52 but now our empire has grown! 13:45:11 we could do a virtual one 13:45:19 it has, so definitely something to consider 13:45:22 trove and ceilometer do that 13:46:35 tangchen, RuiChen and aohuanxuan meeting up during the china bug smash will be like a midcycle for them :) 13:47:10 we could send it to the mailing list 13:47:20 i'll poke dtroyer about it today and see what he says 13:47:27 thanks stevemar 13:47:31 yeah, we can talk face to face, it's great 13:48:00 Maybe RuiChen could post to mailing list about the bug smash and see if others would like to help virtually 13:48:30 ok, I will send it 13:48:43 thanks 13:48:58 my pleasure 13:49:10 looks like google hangouts is mostly used for virtual sprints https://wiki.openstack.org/wiki/Sprints 13:50:39 rtheis: we'd run into a timezone problem 13:50:47 but i wouldn't mind trying it out 13:51:26 right, may have to split it up morning and evening 13:52:12 anything else for today? 13:52:16 nothing from me 13:52:40 last call ... 13:52:42 maybe we can vote the midcycle time for all the osc team members 13:53:24 nothing from me too 13:53:41 RuiChen: let's see if dtroyer wants to do it anyway :P 13:53:56 RuiChen: when is the china bug smash? 13:54:04 yep and then we can discuss and work out the details 13:54:10 6-8 July in china 13:54:18 nice, 3 days 13:54:51 rtheis: wrap this up! 13:55:00 yes 13:55:07 thanks all 13:55:07 #endmeeting