Earlier  
Posted Nick Remark
#openstack-sdks - 2017-03-30
16:22:53 ankur-gupta-f4 i have attended 2 Mariners games and both times i left after the 1st inning. can't do baseball.
16:47:15 ankur-gupta-f4 stevemar: if you get a chance I addressed your comments https://review.openstack.org/#/c/385729/
17:56:45 openstackgerrit Dean Troyer proposed openstack/python-openstackclient master: start using api.versions https://review.openstack.org/451618
18:25:47 openstackgerrit Merged openstack/python-openstackclient master: Trivial Fix https://review.openstack.org/451890
19:00:37 rabel now is osc meeting, right?
19:01:41 rabel dtroyer?
19:01:55 dtroyer eek!!
19:02:19 ankur-gupta-f4 love meetings
19:02:39 dtroyer started in -meetings
20:04:01 amotoki rabel: dtroyer: regarding the interface list in router show output, I think it is useful for users (even though we need an extra API call to fetch it)
20:04:44 dtroyer I'd do it as an option, and its the output formatting that I am mostly worried about, not the number of API calls
20:04:59 amotoki a list of (UUID and IP address) would be enough
20:05:28 amotoki that concern is fair enough. I am looking output of some other commands
20:05:38 dtroyer can you put that in rabel's bug?
20:05:39 dtroyer https://bugs.launchpad.net/python-openstackclient/+bug/1675489
20:05:39 openstack Launchpad bug 1675489 in python-openstackclient "router show should include interfaces" [Undecided,New]
20:05:58 amotoki dtroyer: sure
20:06:03 dtroyer thanks
20:06:12 dtroyer and I need to step away for a bit…
20:07:30 rabel ok. maybe we can continue this issue another day. it's not urgent anyways. ;)
20:07:55 rabel thank you two for your opinion. i got to go now
20:09:29 rabel cu
20:51:29 openstackgerrit Nakul Dahiwade proposed openstack/python-openstacksdk master: Introduce L7Policy for Octavia (load balancing) https://review.openstack.org/451980
20:53:21 openstackgerrit Nakul Dahiwade proposed openstack/python-openstacksdk master: Introduce L7Policy for Octavia (load balancing) https://review.openstack.org/451980
20:57:03 openstackgerrit Nakul Dahiwade proposed openstack/python-openstacksdk master: Introduce Listener for Octavia (load balancing) https://review.openstack.org/451574
20:57:57 ankur-gupta-f4 nakul_d: its on my todo list
20:58:35 nakul_d ankur-gupta-f4: cool..thanks:)
23:30:24 openstackgerrit Merged openstack/osc-lib master: Change noauth strategy for plugin loading https://review.openstack.org/450452
#openstack-sdks - 2017-03-31
00:33:04 reedip anything new happeneing?
00:36:00 reedip armax : never mind, got the info from the new stadium docs :)
00:50:59 reedip wrong place :P
03:21:37 RuiChen hi rabel: I saw your discussion in IRC meeting about "router show interface", seems that the key is identify which port is interface and which is gateway, if i'm not wrong, so "port list --router <router> --long" might be helpful, that show "device owner", looks like: network:router_interface/network:router_gateway
04:22:31 openstackgerrit Merged openstack/python-openstackclient master: Remove log translations https://review.openstack.org/447888
09:36:59 reedip RuiChen : need your help
09:37:35 reedip RuiChen : https://review.openstack.org/#/c/356263/18 was lost somewhere , couldnt track it. I am pushing it now.... can you review it ?
09:38:25 reedip just doing the final test cases
09:38:43 reedip ankur-gupta-f4 : for you as well, when you are awake :D ^^
09:59:41 openstackgerrit Reedip proposed openstack/python-openstackclient master: Add extra dhcp option to 'port create/set/unset' https://review.openstack.org/356263
10:07:10 openstackgerrit Reedip proposed openstack/python-openstackclient master: Add extra dhcp option to 'port create/set/unset' https://review.openstack.org/356263
10:25:00 reedip sindhu : ^^
10:25:04 reedip thanks
13:01:19 openstackgerrit Cedric Brandily proposed openstack/python-openstackclient master: Enable to create legacy router https://review.openstack.org/449176
14:16:08 openstackgerrit Dean Troyer proposed openstack/python-openstackclient master: start using api.versions https://review.openstack.org/451618
14:49:45 sindhu reedip: will take a look :)
14:50:05 reedip great sindhu : cheers :D
14:56:44 openstackgerrit Cedric Brandily proposed openstack/python-openstackclient master: Enable to specify which vm fixed-ip to add https://review.openstack.org/452235
16:37:58 ZZelle reedip, hi
16:38:15 reedip hi Cedrick / ZZelle :)
16:38:32 ZZelle reedip, about https://review.openstack.org/#/c/452235/1/doc/source/command-objects/server.rst
16:38:38 reedip yeah
16:39:05 ZZelle reedip, i don't see the added value of your proposed change
16:39:15 reedip ZZelle : okay
16:39:31 ZZelle reedip, 'Requested fixed ip address' comes from novaclient help
16:39:49 reedip it may not add too much value , thats why I said nit. But it is in line with the message format followed in OSC.
16:40:17 reedip ZZelle : its not necessary to translate the help messages exactly as that from the original client. But similarity is expected.
16:40:43 reedip ZZelle : I find the message , IMO, short. But this is my opinion.
16:41:11 reedip again, its a nit. If others find it Ok, then I dont have a problem.
16:42:52 ZZelle reedip, short doesn't mean meaningless
16:43:31 reedip ZZelle : does my message change the meaning of the one proposed in the patch?
16:44:10 ZZelle reedip, no, longer without added value IMO
16:45:08 reedip ZZelle ; I am not in agreement with you , but yes, thats a nit. I will revert my analysis, but retain my comment
16:45:34 ZZelle reedip, longer also means line-wrapped and less readable
16:45:57 reedip ZZelle : if we are going beyond 80 characters, yes
17:15:27 openstackgerrit Cedric Brandily proposed openstack/python-openstackclient master: Enable to specify which vm fixed-ip to add https://review.openstack.org/452235
20:12:31 stevelle elmiko_ or any other API-WG types paying attention?
20:38:46 figleaf stevelle: I'm around
20:40:29 rosmaita figleaf: got a question about supporting partial downloads. we are thinking of supporting only single-range requests. so in response to a multi-range request, would it be better to (A) return 501, or (B) return 200 and the entire content
20:40:52 rosmaita the standard isn't very clear on this point
20:41:01 stevelle figleaf: reference we have been looking at https://tools.ietf.org/html/rfc7233#section-4.4
20:41:16 figleaf rosmaita: 5xx are only for server-side errors
20:41:37 rosmaita well, it's kind of on us because we aren't implementing something
20:41:55 figleaf If you only support single-range, and they request something unsupported, it should be a 400 Bad Request
20:41:57 stevelle our library doesn't support multi-range
20:42:12 figleaf Is that documented?
20:42:32 stevelle we are choosing not to try to work around that limitation at this time
20:45:21 figleaf I still think a 400 with an error message that explains how to correct the request would be best
20:45:59 rosmaita figleaf: i think this is what we have doc'd now: https://developer.openstack.org/api-ref/image/v2/?expanded=download-binary-image-data-detail
20:47:04 figleaf ah, forgot about 416
20:47:15 figleaf Not one of the more popular return codes :)
20:47:20 rosmaita nope
20:47:28 stevelle pointing at what we have now (which is for the wrong header) is kind of terrible though :)
20:47:54 stevelle makes me sad
20:49:14 stevelle the current text saying "For an unsatisfiable partial download request" seems to suggest it is used where it probably shouldn't
20:49:15 rosmaita figleaf: our reading of the rfc7233 is that 416 is for inconsistent range requests, but in this case, you could be making an otherwise OK request syntax-wise, we just don't suport multi-range requests
20:49:47 rosmaita (well, my reading, anyway)
20:50:25 figleaf rosmaita: I tend to agree.
20:52:17 rosmaita figleaf: that worries me, because we are both sensible fellows, so if we agree, we are probably misreading the standard
20:52:20 rosmaita :)
20:52:36 figleaf what makes you think I'm sensible???
20:53:15 rosmaita we tend to agree a lot, it's the only conclusion to draw
20:54:24 rosmaita in any case, you seem to not like the 501 idea
20:56:07 figleaf No, since the server *does* support the functionality. The user can re-formulate the request so that it will succeed
20:56:44 stevelle to advocate for the other side, the server doesn't support the correctly-formatted request
20:56:48 stevelle so "not supported"
20:57:18 stevelle "I can't do that, Dave." is different from "Syntax Error"
20:58:58 figleaf Well, if I were a user, and I got that, I would assume you don't support any downloads
20:59:31 figleaf the problem with that is that the server *can't* do it
21:00:04 stevelle I thought 501 was that. Note that we WILL return an Accepts-Range header
21:00:19 stevelle regardless of the status code
21:01:13 figleaf Remember that in the RFC, "method" means GET, PUT, etc.

Earlier   Later