Earlier  
Posted Nick Remark
#openstack-sdks - 2018-10-11
16:06:37 mordred edleafe: are we there yet?
16:07:09 edleafe mordred: I swear, if you don't settle down, I'm turning this car around and going back home!!
16:08:18 mordred edleafe: but but but
16:13:42 elmiko edleafe: lol
16:13:54 elmiko edleafe: are we there yet?
16:14:18 edleafe elmiko: I'm going to count to 3...
16:17:07 mordred edleafe: elmiko keeps hitting me!
16:18:02 mordred if people are bored in office hours and want to review some fairly insane python patches - I've got plenty I can point you at ...
16:18:55 elmiko best office hours ever!
17:02:58 edleafe Well, that was underwhelming. :)
17:29:18 openstackgerrit Merged openstack/openstacksdk master: Correct updating baremetal nodes by name or ID https://review.openstack.org/608674
18:14:55 elmiko edleafe: lol
18:21:18 openstackgerrit Sean McGinnis proposed openstack/python-openstackclient master: Handle not having cinderclient.v1 available https://review.openstack.org/609473
20:02:52 openstackgerrit Merged openstack/openstacksdk master: Use discovery instead of config to create proxies https://review.openstack.org/600292
20:16:47 openstackgerrit Merged openstack/openstacksdk master: Remove api version default values https://review.openstack.org/600330
21:02:50 openstackgerrit Sean McGinnis proposed openstack/python-openstackclient master: Handle not having cinderclient.v1 available https://review.openstack.org/609473
#openstack-sdks - 2018-10-12
03:09:39 openstackgerrit Yang JianFeng proposed openstack/openstacksdk master: Add support for octavia's resuorces quota https://review.openstack.org/590193
07:53:00 openstackgerrit Merged openstack/openstacksdk master: Add functional tests for clustering https://review.openstack.org/607061
09:50:26 openstackgerrit Vishakha Agarwal proposed openstack/python-openstackclient master: Modify the help message for 'registered limit set' https://review.openstack.org/609985
11:32:24 openstackgerrit Matthias Lisin proposed openstack/openstacksdk master: openstackcloud.py: Implement FWaaS wrapper methods. https://review.openstack.org/604811
12:51:20 openstackgerrit Dmitry Tantsur proposed openstack/openstacksdk master: Switch bare metal NIC actions in OpenStackCloud to baremetal Proxy calls https://review.openstack.org/610024
13:01:41 dtantsur Shrews: hi, if you have a minute: https://review.openstack.org/#/c/609399/
13:16:12 Shrews dtantsur|afk: sure, will take a look in a little bit
13:43:02 mordred oh my god the discovery patch landed
13:46:14 edleafe mordred: ?? Which patch?
13:46:42 mordred edleafe: Merged openstack/openstacksdk master: Use discovery instead of config to create proxies https://review.openstack.org/600292
13:46:53 mordred edleafe: sdk is now fully discovery driven
13:47:15 mordred with config values only used for override
13:47:47 edleafe mordred: ah. For a second there, I thought you were referring to https://review.openstack.org/459405
13:48:02 mordred edleafe: bah. like we'll ever finish that. it's too hard :)
13:48:43 edleafe nah, we have dtantsur|afk on it.
13:49:21 mordred good point
13:49:31 Shrews mordred: good grief. i +A'd that DAYS ago
13:49:33 mordred mnaser: do you know who a good person is to ping about the broken magnum job for sdk?
13:49:39 Shrews i assumed it merged already
13:50:00 mordred Shrews: there was an oslo.messaging release which broke bifrost which broke the sdk bifrost gate
13:50:30 Shrews see... this is why we should test in a silo
13:50:33 mnaser mordred: I think spyros (PTL) is usually pretty good about that stuff. I can’t recall his IRC nick off the top of my head
13:51:01 mnaser mordred: strigazi
13:51:05 mordred awesome- thanks!
13:51:37 mordred mnaser: openstack-magnum doesn't seem to be their irc channel ...
13:55:24 hansmoleman dtroyer: i was just reminded of this bug i opened for osc https://storyboard.openstack.org/#!/story/2002158 - curious as to how to handle that. you can't set a volume as read-only while it's being created, but the option is on the volume create CLI.
13:55:42 hansmoleman there is a --wait option on the volume create CLI, so if --wait and --read-only, then wait for it to be available and then make the read-only change?
13:55:50 hansmoleman or make --read-only imply --wait?
13:56:21 hansmoleman oh nvm, i guess there is no --wait option for volume create
13:56:23 hansmoleman that's on server create
13:56:51 hansmoleman welp, i could add --wait to volume create and then build on that for --read-only, but that wouldn't work for anyone using older versions of osc
14:04:45 mnaser mordred: #openstack-containers is the one to look at
14:25:27 openstackgerrit Chuck Short proposed openstack/os-client-config master: Change python3.5 job to python3.7 job on Stein+ https://review.openstack.org/610051
14:42:51 mordred hansmoleman: does the volume have to be in ready state to have its readonly attribute set?
14:43:05 hansmoleman yeah it has to be available
14:43:10 mordred how fun
14:43:17 hansmoleman $ openstack volume create --size 1 --read-only read-only-vol1
14:43:17 hansmoleman Failed to set volume read-only access mode flag: Invalid volume: Volume 70539836-fbb9-478d-9cd1-0e733c0eb0cc status must be available to update readonly flag, but current status is: creating. (HTTP 400) (Request-ID: req-ac54552a-3784-4028-8262-8a600844c186)
14:43:42 mordred well - I'd certainly support --read-only implying --wait
14:43:50 mordred because otherwise it's a pretty useless flag
14:43:57 hansmoleman either that or that option just needs to die because it never worked
14:44:01 hansmoleman and was clearly not tested when it was added
14:44:04 mordred yah
14:44:14 openstackgerrit Chuck Short proposed openstack/os-client-config master: Change python3.5 job to python3.7 job on Stein+ https://review.openstack.org/610051
14:44:30 mordred hansmoleman: I say add a wait, make --read-only imply it, and don't worry about backwards compat bcaues the previous thing never worked
14:44:35 hansmoleman there is no --wait on the volume create CLI, so i figure i can just make --read-only wait and i'll update the help on the option to say if you use this, the command will wait
14:44:46 hansmoleman or that
14:45:25 hansmoleman ok that wfm
14:47:22 mordred \o/
14:57:31 openstackgerrit Merged openstack/openstacksdk master: cloud: rename with deprecation validate_node -> validate_machine https://review.openstack.org/609399
19:19:58 openstackgerrit Sean McGinnis proposed openstack/python-openstackclient master: Handle not having cinderclient.v1 available https://review.openstack.org/609473
19:52:59 smcginnis mordred or dtroyer: If one of you has a few minutes - I have a couple openstack volume command additions with one +2 that I would like to make sure are good before proceeding on more updates.
19:53:03 smcginnis https://review.openstack.org/#/q/owner:sean.mcginnis%2540gmail.com+status:open+project:openstack/python-openstackclient
19:53:31 dtroyer smcginnis: I'll have a look in a bit
19:54:10 smcginnis Thanks dtroyer!
20:31:24 dtroyer smcginnis: around? now that I see both commands I have a question…
20:31:45 smcginnis Sure!
20:31:50 dtroyer I had assumed 'volume backend capability' and 'volume backend pool' were your resource names
20:32:02 dtroyer you added 'volume backend' to commands.rst
20:32:29 dtroyer maybe that should be the resource name and —capability and —pool are attributes? dunno, trying to sort out how to thing about these
20:33:02 smcginnis I think that may be confusing. Thinking though...
20:34:09 dtroyer it isn't obvious to me, but I don't have the data models around the backends in my head either
20:35:06 smcginnis I guess you could look at it that way that a backend has a set of capabilities and one or more pools, so I suppose you could use flags for those attributes of the backend.
20:35:13 smcginnis Doesn't really sit right with me though.
20:35:21 dtroyer will there ever be other verbs for this/these resources?
20:35:37 dtroyer maybe it feels like capabilities are attributes but pools are resources
20:35:38 smcginnis What would be the expected behavior of not providing a flag. List both capabilities and pools?
20:35:54 dtroyer so let's go with what you have… and just update commands.rst to list ehm both separately
20:36:08 smcginnis I don't think there will be any other verbs. At least nothing on the horizon that I can tell.
20:36:10 dtroyer ok, yeah, that seals it, too ambiguous
20:36:42 smcginnis Yeah, I kind of like how unambiguous this turned out after changing directions from where I started off.
20:36:59 smcginnis So I should update commands.rst to have each one separately?
20:37:30 smcginnis And it would just be "openstack volume backend capability" and "openstack volume backend pool", no verbs, right?
20:38:55 dtroyer right… I'm leaving comments
20:39:27 smcginnis OK, great. Would it be OK if I did that in a follow up patch? There's one or two other internal things I would like to clean up too.
20:40:27 smcginnis Guess that's what I get for using one of Monty's release notes as a template. :D
20:40:42 dtroyer that works for me, they both had tweaks needed :)
20:40:58 smcginnis Will get that going right now...
20:40:58 dtroyer I re-write release notes before a release to make then have at least a similar voice
20:41:15 dtroyer ok, if you're going to do a follow-up I'll +W these now
20:41:23 smcginnis Great. Often overlooked, but I think that makes them much easier to consume when projects do that.
20:43:32 dtroyer in the v1 change, is importing from cinderclient.v3 going to be a problem for v2 commands?
20:45:19 dtroyer smcginnis: basically I just want to be sure that importing v3 but not setting microversions keeps us at v2-compat?
20:45:23 mordred smcginnis: never copy from me :)

Earlier   Later