13:03:09 #startmeeting openstackclient 13:03:10 Meeting started Thu Nov 17 13:03:09 2016 UTC and is due to finish in 60 minutes. The chair is dtroyer. Information about MeetBot at http://wiki.debian.org/MeetBot. 13:03:11 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 13:03:13 The meeting name has been set to 'openstackclient' 13:03:24 So who is here? 13:03:52 Hi, dtroyer 13:03:58 o/ 13:04:15 Good morning/evening huanxuan 13:05:51 Seems like it is just us 13:06:00 I have made a bp for refactoring transfer commands, you could check it when you have time. 13:06:04 yes ... 13:06:07 just we two 13:06:16 ok, I will, thank you 13:06:18 https://blueprints.launchpad.net/python-openstackclient/+spec/transfer-request-refactor 13:06:47 and I have some review questions 13:06:57 very nice, I will look at it closely after the meeting 13:07:12 ok. real quick before the review questions... 13:07:44 I wanted to mention that the 3.4.0 release is almost ready, stevemar had one more thing to add to it, then we should do the release later today 13:08:22 #topic reviews 13:08:30 ok, huanxuan, what questions? 13:08:58 What your suggestion about this one: https://review.openstack.org/#/c/398123/ 13:09:25 it seems like a show command, because just one result will be returned 13:09:47 yes it does 13:09:59 in cinderclient, it is a new command : cinder type-default 13:10:01 it is also a configuration command 13:10:18 yes 13:10:21 well, it shows configuration. IIRC default volume type is set in cinder.conf? 13:10:48 so it is nice in that the user can actually discover something about the cloud config 13:11:05 I am wondering if we shouldn't have a single global command for this? 13:11:28 and it can have API options (—volume, —compute, etc) for when only one portion of the cloud config is desired 13:12:48 You mean a global command for showing config for every service (compute volume network..)? 13:13:11 yes. there are other things that can be discovered like this 13:13:27 we should have a common way to do that 13:13:43 OK, get it! 13:14:16 that doesn't mean we have to implement them all right away, but we should at least sort out what it will look like 13:14:40 yes 13:17:35 huanxuan: did you have more reviews to discuss? 13:18:25 https://review.openstack.org/#/c/383025/ this one... looks a bit weird... 13:18:45 about the command name 13:19:29 that one seems backwards to me 13:19:50 I think of having a port that I want to add a floating Ip to: port add floating ip 13:20:17 the question to ask, is which resource contains the other resource? 13:20:25 yes 13:21:07 IMO, is floating IP add a fixed IP of a port 13:21:46 sometimes port have more than one fixed IP 13:22:15 right, which is what makes me think it should be the other way around, just like a security group has multiple rules 13:23:08 yes 13:24:12 ah, right, this has gone back and forth a few times… 13:25:40 I will update my comments 13:25:52 ok, thank you :) 13:28:36 anything else? 13:29:38 ah.. I have on other questions today, thank you! hope to see you comment for the transfer command refactor BP 13:30:11 I will, that will take a little more caffiene to think about :) 13:30:53 yes, it is not a easy work 13:34:23 ok, nobody else has chimed in, let's call it a day 13:34:36 thank you huanxuan 13:34:38 ok 13:34:40 #endmeeting