Earlier  
Later
New Search
Posted Nick Remark
#openstack-sdks - 2017-01-16
15:16:11 openstackgerrit Nikita Gerasimov proposed openstack/python-openstackclient: Switch server create to block_device_mapping_v2 https://review.openstack.org/407111
15:17:08 stevemar dtroyer: okay, the network help one should be ready to go and is arguably necessary for the next release
15:17:38 stevemar aside from that, *only* new fucntionality should land (like the volume type encryption stuff)
15:18:15 dtroyer right
15:18:44 stevemar dtroyer: kk, just wanted to make sure we're on the same page :)
15:18:46 dtroyer I'm not sure if we can have manage/unmanage settled in time, I still _really_ do not like those actions
15:19:10 stevemar yeah, debatable stuff can wait
15:19:14 stevemar tests are always welcomed :)
15:27:17 openstackgerrit Merged openstack/keystoneauth: Replace yaml.load() with yaml.safe_load() https://review.openstack.org/420572
16:34:57 openstackgerrit zhiyong.dai proposed openstack/python-openstackclient: Update functional test for aggregate. https://review.openstack.org/418685
17:26:26 openstackgerrit OpenStack Proposal Bot proposed openstack/osc-lib: Updated from global requirements https://review.openstack.org/420846
17:28:10 openstackgerrit OpenStack Proposal Bot proposed openstack/python-openstackclient: Updated from global requirements https://review.openstack.org/420862
17:28:13 openstackgerrit OpenStack Proposal Bot proposed openstack/python-openstacksdk: Updated from global requirements https://review.openstack.org/420863
19:24:59 openstackgerrit Merged openstack/osc-lib: Updated from global requirements https://review.openstack.org/420846
20:04:23 stevemar dtroyer: did you want me to abandon the revert of the SDK bump?
20:04:42 stevemar actually, i think we want that merged now that i think about it
20:07:42 dtroyer stevemar: which is that?
20:08:06 stevemar dtroyer: https://review.openstack.org/#/c/418663/
20:08:52 dtroyer yeah, we do want that merged.
20:09:28 stevemar dtroyer: tweaked it a bit, made the minimum .12
20:09:44 dtroyer it leaves the 0.9.11 block in place, any particular reason? I know it'll probably never be used in practice
20:10:20 dtroyer ok, refreshed
20:12:01 stevemar dtroyer: yah, refreshed and added relevant people
20:12:33 dtroyer have you seen any tests yet since u-c merged? I just now heading off to look for some
20:13:03 stevemar dtroyer: not yet
20:58:35 openstackgerrit Steve Martinelli proposed openstack/python-openstackclient: Update functional test for aggregate. https://review.openstack.org/418685
21:06:42 stevemar dtroyer: i think mitaka is when folks really started to use OSC
21:06:50 stevemar judging by the backports
21:06:57 stevemar interested
21:06:59 stevemar interesting*
21:08:24 openstackgerrit Merged openstack/python-openstackclient: Updated from global requirements https://review.openstack.org/420862
21:50:11 openstackgerrit John Dennis proposed openstack/keystoneauth: Use comma as separator in ECP Accept HTTP header https://review.openstack.org/420970
#openstack-sdks - 2017-01-17
01:22:10 openstackgerrit Merged openstack/python-openstackclient: Update functional test for aggregate. https://review.openstack.org/418685
02:18:32 openstackgerrit Merged openstack/python-openstacksdk: Updated from global requirements https://review.openstack.org/420863
04:29:10 openstackgerrit jiahui.qiang proposed openstack/python-openstackclient: Error in the return of command 'volume qos create' https://review.openstack.org/421065
04:38:05 openstackgerrit jiahui.qiang proposed openstack/python-openstackclient: Functional test for volume qos https://review.openstack.org/421066
06:02:16 openstackgerrit jichenjc proposed openstack/api-wg: fix no sample file in browser https://review.openstack.org/421084
06:03:18 openstackgerrit Merged openstack/python-openstackclient: functional test for volume https://review.openstack.org/417349
06:43:39 openstackgerrit Merged openstack/keystoneauth: Use comma as separator in ECP Accept HTTP header https://review.openstack.org/420970
09:17:56 openstackgerrit Rui Chen proposed openstack/python-openstackclient: Update devref about "--no-property" https://review.openstack.org/421160
10:10:55 openstackgerrit zhiyong.dai proposed openstack/python-openstackclient: Add "volume host failover" command https://review.openstack.org/411259
10:13:49 openstackgerrit jiahui.qiang proposed openstack/python-openstackclient: Functional test for volume snapshot https://review.openstack.org/421194
11:43:33 openstackgerrit jiahui.qiang proposed openstack/python-openstackclient: Error in the return of command 'volume qos create' https://review.openstack.org/421065
12:58:00 amotoki hi, could someone from OSC team advise the command naming in neutronclient OSC plugin review? https://review.openstack.org/#/c/416321/6/setup.cfg
12:58:41 amotoki what I'd like to ask are 'net-assoc' and 'router-assoc'.
12:59:29 amotoki (1) In OSC we don't use '-' as a delimiter. we use a space as a delimiter. Should we use 'bgpvpn net assoc create' for example?
12:59:51 amotoki (2) Should we use 'network associate' instead of 'net-assoc'?
13:00:49 amotoki (OSC has commands like 'network xxxx' rather than 'net xxxx', so I think we should not abbreviate command names as possible as we can)
13:06:55 stevemar amotoki: definitely 'network' over 'net'
13:07:18 stevemar amotoki: what's 'assoc' ?
13:07:36 amotoki stevemar: thanks. 'assoc' is abbrev of association.
13:07:51 stevemar amotoki: an bgvpn?
13:07:57 amotoki yes
13:07:59 stevemar bgp*
13:08:17 stevemar amotoki: sorry, i meant, what is bgpvpn?
13:08:48 amotoki neutron stadium has bgpvpn project (though not yet approved)
13:09:24 amotoki it is related to BGP VPN (not BGP (which is part of dynamic-routing)
13:10:01 stevemar ohh bgp == bagpipe
13:10:59 amotoki let me check
13:11:19 stevemar amotoki: associations are tricky
13:11:21 amotoki there are networking-bgpvpn and networking-bagpipe...
13:12:03 amotoki what we are looking at is networking-bgpvpn (not bagpipe)
13:12:08 amotoki See http://git.openstack.org/cgit/openstack/networking-bgpvpn/tree/setup.cfg
13:13:38 amotoki honestly I am not sure 'association' is the right word.
13:17:07 amotoki stevemar: at least, I think 'assoc' is confusing (even though 'association' is the right word)
13:18:10 openstackgerrit Rodrigo Duarte proposed openstack/keystoneauth: Add test for header in Saml2 plugin https://review.openstack.org/421265
13:19:33 openstackgerrit Rodrigo Duarte proposed openstack/keystoneauth: Add test for header in Saml2 plugin https://review.openstack.org/421265
13:21:00 stevemar amotoki: commented
13:21:10 amotoki stevemar: thanks!
13:21:18 openstackgerrit Nikita Gerasimov proposed openstack/python-openstackclient: Switch server create to block_device_mapping_v2 https://review.openstack.org/407111
13:21:44 stevemar amotoki: its mostly what we already do for the volume type qos resource
13:22:32 amotoki stevemar: your suggestion sounds more reasonable and natural to me. the second word should be a verb.
13:25:11 stevemar amotoki: :)
13:25:34 stevemar amotoki: i think combining the 4 commands into 2 makes a lot more sense
13:26:28 stevemar amotoki: and we often combine API calls to get all the information -- so making an extra call to get associations, when displaying information about bgpvpn makes sense to me
13:27:05 stevemar amotoki: we have a bad habit of: 1 API == 1 CLI
13:27:06 stevemar :)
13:30:02 amotoki stevemar: hehe
13:31:44 amotoki stevemar: in addition, most developers of CLI are implementors of API itself, so they tend to mirror API to CLI.
13:32:23 stevemar amotoki: yep :)
13:44:18 openstackgerrit Rodrigo Duarte proposed openstack/keystoneauth: Add test for header in Saml2 plugin https://review.openstack.org/421265
14:51:22 reedip_ dtroyer: ping
14:52:34 dtroyer reedip: heyo
14:53:05 openstackgerrit Dean Troyer proposed openstack/os-client-config: Add OpenTelekomCloud to the vendors https://review.openstack.org/412098
14:53:42 reedip_ dtroyer :need your opinion about https://review.openstack.org/#/c/383025/
14:53:48 dtroyer mordred: ^^^ I'm cleaning up o-c-c-'s queue for a release before freeze
14:55:39 reedip_ dtroyer : I have mentioned my opinion as below :
14:55:43 reedip_ dtroyer: Can we rename these commands as
14:55:44 reedip_ floating ip set --port
14:55:44 reedip_ floating ip unset --port
14:55:44 reedip_ If we rename the commands as above, then it should follow the OSC convention of Updating Floating IP objects.
14:55:44 reedip_ And basically as we are Updating the Floating IP objects in the current CLIs by adding/removing ports, therefore our target functionality will also be achieved.
14:56:16 dtroyer reedip: for the OSC command set consistency, the questions to ask are "can a port have more than one floating IP?" and "can a floating IP have more than one port?" If the answer to both is yes, then we need to thing about how to represent many-to-many relationships, we don't have any other of those.
14:56:40 dtroyer If the answer to one of those is ues, the resource that has multiples is the first one on the command
14:57:02 dtroyer if the answer to both is no, we can use a set command, then argue about which one it belongs to
14:57:48 reedip_ dtroyer : that makes it better to understand. Can you please mention the same on the review ? It would help neutron team push it forward :)
14:58:08 dtroyer ok
14:58:16 reedip_ thanks a tonne dtroyer :)
15:04:49 openstackgerrit Huanxuan Ao proposed openstack/python-openstackclient: Fix functional test for creating subnet https://review.openstack.org/421310
15:30:44 openstackgerrit Samuel Pilla proposed openstack/keystoneauth: Correctly Omit Response Body in Debug Mode https://review.openstack.org/421319

Earlier   Later