Friday, 2018-10-12

*** bobh has joined #openstack-sdks01:24
*** zigo has quit IRC02:29
*** zigo has joined #openstack-sdks02:31
*** lbragstad has joined #openstack-sdks02:45
*** bobh has quit IRC03:02
*** bobh has joined #openstack-sdks03:05
*** dave-mccowan has quit IRC03:05
openstackgerritYang JianFeng proposed openstack/openstacksdk master: Add support for octavia's resuorces quota
*** bobh has quit IRC03:16
*** dayou has quit IRC04:06
*** smcginnis has quit IRC04:06
*** dayou has joined #openstack-sdks04:06
*** lbragstad has quit IRC04:21
*** gildub_ has quit IRC05:13
*** olivierb has joined #openstack-sdks05:30
*** Luzi has joined #openstack-sdks07:29
*** tosky has joined #openstack-sdks07:45
*** jpich has joined #openstack-sdks07:46
openstackgerritMerged openstack/openstacksdk master: Add functional tests for clustering
*** e0ne has joined #openstack-sdks07:59
*** d0ugal has quit IRC08:07
*** d0ugal has joined #openstack-sdks08:08
*** ttsiouts has joined #openstack-sdks08:19
*** ttsiouts has quit IRC08:22
*** ttsiouts_ has joined #openstack-sdks08:22
*** ttsiouts_ has quit IRC08:42
*** ttsiouts has joined #openstack-sdks08:42
*** e0ne has quit IRC08:44
*** e0ne has joined #openstack-sdks08:46
*** slaweq has quit IRC08:46
*** ttsiouts has quit IRC08:47
*** ttsiouts has joined #openstack-sdks08:56
*** e0ne has quit IRC09:13
*** ttsiouts has quit IRC09:16
*** e0ne has joined #openstack-sdks09:16
*** ttsiouts has joined #openstack-sdks09:16
*** ttsiouts_ has joined #openstack-sdks09:18
*** ttsiouts has quit IRC09:21
*** dtantsur|afk is now known as dtantsur09:33
*** ttsiouts_ has quit IRC09:37
*** ttsiouts has joined #openstack-sdks09:39
openstackgerritVishakha Agarwal proposed openstack/python-openstackclient master: Modify the help message for 'registered limit set'
*** ttsiouts has quit IRC09:53
*** imacdonn has quit IRC09:53
*** imacdonn has joined #openstack-sdks09:53
*** Luzi has quit IRC09:55
*** slaweq has joined #openstack-sdks09:56
*** ttsiouts has joined #openstack-sdks09:57
*** ttsiouts has quit IRC10:01
*** e0ne has quit IRC10:34
*** jpena|off has quit IRC10:41
*** jpena|off has joined #openstack-sdks10:42
*** ttsiouts has joined #openstack-sdks11:08
*** dayou has quit IRC11:09
*** dayou has joined #openstack-sdks11:14
*** ttsiouts has quit IRC11:16
*** ttsiouts has joined #openstack-sdks11:17
*** ttsiouts has quit IRC11:21
*** ttsiouts has joined #openstack-sdks11:23
*** e0ne has joined #openstack-sdks11:27
*** ttsiouts has quit IRC11:27
openstackgerritMatthias Lisin proposed openstack/openstacksdk master: Implement FWaaS wrapper methods.
*** dave-mccowan has joined #openstack-sdks11:38
*** ttsiouts has joined #openstack-sdks11:39
*** bobh has joined #openstack-sdks12:01
*** ttsiouts has quit IRC12:03
*** ttsiouts has joined #openstack-sdks12:03
*** ttsiouts has quit IRC12:08
*** bobh has quit IRC12:09
*** ttsiouts has joined #openstack-sdks12:11
*** e0ne has quit IRC12:16
*** e0ne has joined #openstack-sdks12:17
openstackgerritDmitry Tantsur proposed openstack/openstacksdk master: Switch bare metal NIC actions in OpenStackCloud to baremetal Proxy calls
*** mriedem has joined #openstack-sdks12:58
dtantsurShrews: hi, if you have a minute:
*** bobh has joined #openstack-sdks13:06
*** dtantsur is now known as dtantsur|afk13:07
*** markvoelker has quit IRC13:15
Shrewsdtantsur|afk: sure, will take a look in a little bit13:16
*** ttsiouts has quit IRC13:20
*** ttsiouts has joined #openstack-sdks13:22
*** mriedem is now known as hansmoleman13:22
*** lbragstad has joined #openstack-sdks13:23
*** munimeha1 has joined #openstack-sdks13:23
*** munimeha1 has quit IRC13:38
*** stephenfin is now known as finucannot13:41
mordredoh my god the discovery patch landed13:43
*** irclogbot_0 has joined #openstack-sdks13:44
edleafemordred: ?? Which patch?13:46
mordrededleafe: Merged openstack/openstacksdk master: Use discovery instead of config to create proxies
mordrededleafe: sdk is now fully discovery driven13:46
mordredwith config values only used for override13:47
edleafemordred: ah. For a second there, I thought you were referring to
mordrededleafe: bah. like we'll ever finish that. it's too hard :)13:48
edleafenah, we have dtantsur|afk on it.13:48
mordredgood point13:49
*** irclogbot_0 has quit IRC13:49
Shrewsmordred: good grief. i +A'd that DAYS ago13:49
mordredmnaser: do you know who a good person is to ping about the broken magnum job for sdk?13:49
Shrewsi assumed it merged already13:49
mordredShrews: there was an oslo.messaging release which broke bifrost which broke the sdk bifrost gate13:50
Shrewssee... this is why we should test in a silo13:50
mnasermordred: I think spyros (PTL) is usually pretty good about that stuff. I can’t recall his IRC nick off the top of my head13:50
mnasermordred: strigazi13:51
mordredawesome- thanks!13:51
mordredmnaser: openstack-magnum doesn't seem to be their irc channel ...13:51
*** irclogbot_0 has joined #openstack-sdks13:53
hansmolemandtroyer: i was just reminded of this bug i opened for osc!/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
hansmolemanthere 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
hansmolemanor make --read-only imply --wait?13:55
hansmolemanoh nvm, i guess there is no --wait option for volume create13:56
hansmolemanthat's on server create13:56
hansmolemanwelp, 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 osc13:56
*** irclogbot_0 has quit IRC13:59
*** irclogbot_0 has joined #openstack-sdks13:59
mnasermordred: #openstack-containers is the one to look at14:04
*** irclogbot_0 has quit IRC14:18
*** lbragstad is now known as elbragstad14:25
openstackgerritChuck Short proposed openstack/os-client-config master: Change python3.5 job to python3.7 job on Stein+
*** markvoelker has joined #openstack-sdks14:41
mordredhansmoleman: does the volume have to be in ready state to have its readonly attribute set?14:42
hansmolemanyeah it has to be available14:43
mordredhow fun14:43
hansmoleman$ openstack volume create --size 1 --read-only read-only-vol114:43
hansmolemanFailed 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
mordredwell - I'd certainly support --read-only implying --wait14:43
mordredbecause otherwise it's a pretty useless flag14:43
hansmolemaneither that or that option just needs to die because it never worked14:43
hansmolemanand was clearly not tested when it was added14:44
openstackgerritChuck Short proposed openstack/os-client-config master: Change python3.5 job to python3.7 job on Stein+
mordredhansmoleman: I say add a wait, make --read-only imply it, and don't worry about backwards compat bcaues the previous thing never worked14:44
hansmolemanthere 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 wait14:44
hansmolemanor that14:44
hansmolemanok that wfm14:45
* mordred is helpful today14:47
openstackgerritMerged openstack/openstacksdk master: cloud: rename with deprecation validate_node -> validate_machine
*** e0ne has quit IRC14:58
*** e0ne has joined #openstack-sdks15:06
*** irclogbot_0 has joined #openstack-sdks15:15
* edleafe checks the alignment of the planets 15:16
*** irclogbot_0 has quit IRC15:21
*** irclogbot_0 has joined #openstack-sdks15:21
*** ttsiouts has quit IRC15:31
*** e0ne has quit IRC15:37
*** e0ne has joined #openstack-sdks15:40
*** e0ne has quit IRC15:40
*** irclogbot_0 has quit IRC15:50
*** markvoelker has quit IRC15:51
*** markvoelker has joined #openstack-sdks15:52
*** finucannot is now known as stephenfin16:01
*** bobh has quit IRC16:12
*** jpich has quit IRC16:17
*** hansmoleman is now known as mriedem_away16:18
*** bobh has joined #openstack-sdks16:23
*** e0ne has joined #openstack-sdks17:28
*** olivierb has quit IRC18:21
*** e0ne has quit IRC18:37
*** kmalloc is now known as needscoffee18:48
*** pooja-jadhav has joined #openstack-sdks19:03
*** pooja_jadhav has quit IRC19:05
*** pooja_jadhav has joined #openstack-sdks19:10
*** pooja-jadhav has quit IRC19:13
openstackgerritSean McGinnis proposed openstack/python-openstackclient master: Handle not having cinderclient.v1 available
*** smcginnis has joined #openstack-sdks19:51
smcginnismordred 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:52
dtroyersmcginnis: I'll have a look in a bit19:53
smcginnisThanks dtroyer!19:54
*** needscoffee is now known as kmalloc20:20
dtroyersmcginnis: around?  now that I see both commands I have a question…20:31
dtroyerI had assumed 'volume backend capability' and 'volume backend pool' were your resource names20:31
dtroyeryou added 'volume backend' to commands.rst20:32
dtroyermaybe that should be the resource name and —capability and —pool are attributes?  dunno, trying to sort out how to thing about these20:32
smcginnisI think that may be confusing. Thinking though...20:33
dtroyerit isn't obvious to me, but I don't have the data models around the backends in my head either20:34
smcginnisI 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
smcginnisDoesn't really sit right with me though.20:35
dtroyerwill there ever be other verbs for this/these resources?20:35
dtroyermaybe it feels like capabilities are attributes but pools are resources20:35
smcginnisWhat would be the expected behavior of not providing a flag. List both capabilities and pools?20:35
dtroyerso let's go with what you have… and just update commands.rst to list ehm both separately20:35
smcginnisI don't think there will be any other verbs. At least nothing on the horizon that I can tell.20:36
dtroyerok, yeah, that seals it, too ambiguous20:36
smcginnisYeah, I kind of like how unambiguous this turned out after changing directions from where I started off.20:36
smcginnisSo I should update commands.rst to have each one separately?20:36
smcginnisAnd it would just be "openstack volume backend capability" and "openstack volume backend pool", no verbs, right?20:37
dtroyerright… I'm leaving comments20:38
smcginnisOK, 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:39
smcginnisGuess that's what I get for using one of Monty's release notes as a template. :D20:40
dtroyerthat works for me, they both had tweaks needed  :)20:40
smcginnisWill get that going right now...20:40
dtroyerI re-write release notes before a release to make then have at least a similar voice20:40
dtroyerok, if you're going to do a follow-up I'll +W these now20:41
smcginnisGreat. Often overlooked, but I think that makes them much easier to consume when projects do that.20:41
dtroyerin the v1 change, is importing from cinderclient.v3 going to be a problem for v2 commands?20:43
dtroyersmcginnis: basically I just want to be sure that importing v3 but not setting microversions keeps us at v2-compat?20:45
mordredsmcginnis: never copy from me :)20:45
smcginnisdtroyer: No, the base v3.0 is identical to v2. It's only after additional microversions (>=3.1) that things start to diverge.20:45
smcginnismordred: ;)20:45
dtroyerok, good20:45
dtroyeras soon as an SDK 1.0 hits we can start playing with microversions with gusto20:46
smcginnisI thought of going with v2 as the default, but since they are the same and we eventually someday maybe would like to get down to one version, I thought v3 would be best.20:46
mordreddiscovery landed today20:46
mordredso I'm thinking of cutting an rc next week20:46
mordredalthough I just started hitting the existing sdk glance code with a giant stick20:46
dtroyerjust when I'm tied up with releasing stx…20:46
smcginnisGreat, I was going to ask about mv support. We have a bunch of cinder commands I would like to add but they are for microversioned things.20:46
mordredbut - you know - we'll be 1.0 enough for osc :)20:46
mordredsmcginnis: dtantsur|afk has been doing a decent amount with mv and ironic in sdk - so not only do we support discovering/configuring them - we've even got some examples of doing something with them :)20:47
mordredand - of course - the joy that is live-migrate20:47
smcginnisPerfect, maybe I can take a look at that work and try to contribute some for cinder.20:48
mordredspeaking of - I actually have something in a glance patch i should do for cinder too20:48
*** bobh has quit IRC20:48
mordrednamely - adding support for a base proxy class that has shared code - so for places where it's all the same we don't have to duplicate as much20:49
mordredI think that'll be nice for cinder v2/v320:49
mordredI may put in the basics and then ask for your eyes on that?20:49
*** mriedem_away is now known as mriedem20:51
dtroyerfwiw, I explicitly did not do that in OSC so we would never have to decide which version that shared code might affect.  I _think_ that is still a good decision, maybe the effects are different at that level…20:52
smcginnismordred: Perfect, I love reducing code.20:52
dtroyeralso, we'll remove cinder v1 with mostly a git rm20:52
smcginnisI think that should be OK here with cinder v2/v3. If they are not the same without microversions, then we messed up.20:53
dtroyersomeday when I'm old(er)20:53
mordreddtroyer: yah - I think for the most part it's clearer to read when it's just separate20:53
smcginnisIf we can have v2 just duplicate off of v3, then removal should be quick and easy if we ever get to that point.20:53
smcginnisEither way.20:53
dtroyeranyway, enough from me, back to setting up docs for the flock-o-birds20:53
mordreddtroyer: the specific case where I added a base class was so I could do create_image - which is super complex and has logic that applies regardless of version - and then forking logic per-version20:53
dtroyermordred: ah, makes sense in cases like that20:54
mordredto handle that, I made a BaseImageProxy - and then had image.v1.Proxy and image.v2.Proxy both subclass it20:54
mordreddtroyer: speaking of - when we start ripping out glanceclient - I have a some very shiny image upload code we can take care of20:55
openstackgerritSean McGinnis proposed openstack/python-openstackclient master: Address issues from volume backend commands
mordredandby shiny, I mean dirty dirty dirty nasty dirty20:55
smcginnisdtroyer: Good luck with the release.20:56
* mordred hands dtroyer a bunny rabbit of luck20:56
*** dave-mccowan has quit IRC20:57
dtroyerthanks guys, we've got 12 days so no crunching sounds from behind… yet…20:57
smcginnisdtroyer: It's probably completely different than what we've got here, but let me know if you run into anything I can help with.20:58
dtroyersmcginnis: not completely different, I didn't want to invent new, mostly we're just not doing a bunch of things.  But I'm finding I may regret choosing 'r/' for the release branch prefix.  Many of the exiting tools assume 'stable/'21:00
dtroyerlike we don't publish anything other than docs, the final release is really just the tags in git.  but the docs… whee!  I'm learning a LOT21:02
smcginnisHeh, yeah. I think it's sprinkled everywhere assuming stable/21:02
dtroyerI'm trying to decide if it is too late to change.  Maybe for this release it is but it's also basically an alpha release.  MAybe for the one in MArch we will change it…21:03
smcginnisYou may end up having changed enough by that point not to, but if we ever think there may be some convergence point in the future between these, it might make sense to try to stay with stable.21:04
smcginnisNot sure if that's a realistic thing or not.21:04
smcginnisBut at least picking up future release automation changes from openstack, it might make it easier if there's less to tweak in adopting it.21:05
dtroyerhonestly the convergence I see is possibly taking a project or two and making them look even more like OpenStack projects, they might be useful for your average Joe Cloud too…21:06
smcginnisYeah, hopefully that's the case.21:07
dtroyerI am stealing^H^H^H^Hborrowing as much as I can, thanks for all the fish!21:07
openstackgerritMonty Taylor proposed openstack/openstacksdk master: Add stackviz processing to functional tests
smcginnisI would definitely do the same.21:15
samueldmqhi, is there a description of what each one of SDK's gate jobs does?21:22
samueldmqmordred: ^21:22
samueldmqit's not too hard to have an idea with the job name, but I was wondering if I could confirm that somehow21:23
openstackgerritMerged openstack/os-client-config master: Change python3.5 job to python3.7 job on Stein+
smcginnissamueldmq: You should be able to take a look at the logs to see what commands the jobs are running.21:39
smcginnissamueldmq: Or search for the job name in to track down its definition.21:40
*** tosky has quit IRC22:02
*** mriedem is now known as mriedem_away22:05
openstackgerritMerged openstack/python-openstackclient master: Add volume backend capability show command
openstackgerritMerged openstack/python-openstackclient master: Add volume backend pool list command
openstackgerritMerged openstack/python-openstackclient master: Allow endpoint filtering on both project and project-domain
*** elbragstad has quit IRC22:56
*** elbragstad has joined #openstack-sdks23:15
*** elbragstad has quit IRC23:15
samueldmqsmcginnis: Awesome. Thanks23:19
*** slaweq has quit IRC23:32

Generated by 2.15.3 by Marius Gedminas - find it at!