Wednesday, 2018-10-03

*** markvoelker has quit IRC00:17
*** markvoelker has joined #openstack-sdks00:17
*** markvoelker has quit IRC00:21
*** Qiming has quit IRC01:06
*** Qiming has joined #openstack-sdks01:09
*** openstackgerrit has joined #openstack-sdks01:30
openstackgerritMerged openstack/python-openstackclient master: Add metavar for name parameter in subnet create
*** dave-mccowan has joined #openstack-sdks01:56
*** markvoelker has joined #openstack-sdks02:18
openstackgerritAndriy Shevchenko proposed openstack/python-openstackclient master: fix tox python3 overrides
*** markvoelker has quit IRC02:51
*** dave-mccowan has quit IRC03:08
*** markvoelker has joined #openstack-sdks03:48
*** markvoelker has quit IRC04:21
*** gkadam has joined #openstack-sdks04:32
*** gkadam has quit IRC04:32
*** markvoelker has joined #openstack-sdks05:18
*** markvoelker has quit IRC05:52
*** dims has quit IRC06:24
*** e0ne has joined #openstack-sdks06:24
*** dims has joined #openstack-sdks06:26
*** dims has quit IRC06:34
*** dims has joined #openstack-sdks06:35
*** tosky has joined #openstack-sdks07:03
*** Horrorcat has quit IRC07:19
*** jroll has quit IRC07:19
*** dmellado has quit IRC07:19
*** odyssey4me has quit IRC07:19
*** amotoki has quit IRC07:23
*** olivierb has joined #openstack-sdks07:24
*** Horrorcat has joined #openstack-sdks07:32
*** jroll has joined #openstack-sdks07:32
*** dmellado has joined #openstack-sdks07:32
*** odyssey4me has joined #openstack-sdks07:32
*** jpich has joined #openstack-sdks07:35
*** gkadam has joined #openstack-sdks07:44
*** amotoki has joined #openstack-sdks07:52
*** amotoki has quit IRC07:52
*** amotoki has joined #openstack-sdks07:53
*** amotoki has quit IRC07:57
*** Horrorcat has quit IRC08:13
*** jroll has quit IRC08:13
*** dmellado has quit IRC08:13
*** odyssey4me has quit IRC08:13
*** markvoelker has joined #openstack-sdks08:18
*** amotoki has joined #openstack-sdks08:25
*** Horrorcat has joined #openstack-sdks08:27
*** jroll has joined #openstack-sdks08:27
*** dmellado has joined #openstack-sdks08:27
*** odyssey4me has joined #openstack-sdks08:27
*** amotoki_ has joined #openstack-sdks08:27
*** amotoki has quit IRC08:28
*** cdent has joined #openstack-sdks08:31
*** ttsiouts has joined #openstack-sdks08:51
*** Horrorcat has quit IRC08:51
*** jroll has quit IRC08:51
*** dmellado has quit IRC08:51
*** odyssey4me has quit IRC08:51
*** markvoelker has quit IRC08:51
*** ttsiouts has quit IRC08:53
*** ttsiouts has joined #openstack-sdks08:53
*** ttsiouts has quit IRC08:58
*** ttsiouts has joined #openstack-sdks09:00
*** Horrorcat has joined #openstack-sdks09:05
*** jroll has joined #openstack-sdks09:05
*** dmellado has joined #openstack-sdks09:05
*** odyssey4me has joined #openstack-sdks09:05
*** ttsiouts has quit IRC09:07
*** ttsiouts has joined #openstack-sdks09:07
*** ttsiouts_ has joined #openstack-sdks09:10
*** ttsiouts has quit IRC09:12
*** gildub has joined #openstack-sdks09:15
*** ttsiouts_ has quit IRC10:07
*** pepijn has joined #openstack-sdks10:17
*** gkadam has quit IRC10:24
*** markvoelker has joined #openstack-sdks10:49
*** ttsiouts has joined #openstack-sdks11:02
*** amotoki_ is now known as amotoki11:07
*** markvoelker has quit IRC11:22
*** gildub has quit IRC11:38
*** pepijn has quit IRC11:59
*** pepijn has joined #openstack-sdks12:03
*** e0ne has quit IRC12:04
*** ttsiouts has quit IRC12:05
*** ttsiouts has joined #openstack-sdks12:07
openstackgerritMonty Taylor proposed openstack/openstacksdk master: Split advanced networking services into a job
*** ttsiouts has quit IRC12:11
mlam I able to trigger a recheck myself or do you have to reset the workflow?12:13
mordredml: you can - but hold off for now- the issue that's happening is the test node running out of memory12:13
mordredml: I'm trying to fix with - if it fixes it, I'll probably just squash it into your patch and merge it that way12:14
mlalright, I'll keep an eye on this change. thanks for your work12:15
*** e0ne has joined #openstack-sdks12:16
*** dave-mccowan has joined #openstack-sdks12:20
*** pepijn has quit IRC12:25
*** ttsiouts has joined #openstack-sdks12:31
*** ttsiouts has quit IRC12:33
*** ttsiouts has joined #openstack-sdks12:34
*** pepijn has joined #openstack-sdks12:36
*** rosmaita has joined #openstack-sdks12:46
*** rosmaita has left #openstack-sdks12:46
*** pepijn has quit IRC13:05
*** smcginnis has joined #openstack-sdks13:23
*** rosmaita has joined #openstack-sdks13:30
rosmaitacdent: have an api question for you when you have a few minutes13:31
cdentrosmaita: i've got time, for you, right now13:33
rosmaitacdent: thanks! can you take a look at /13:34
rosmaita(meant that to be a ? at the end)13:34
* cdent looks13:34
*** mriedem has joined #openstack-sdks13:37
cdentrosmaita: okay, I think I'm caught up on the text of the spec and the comments13:41
cdentwhat's the main issue you're concerned with?13:42
rosmaitacdent: whether i'm right about us having to introduce a new json-patch mime type for this13:42
rosmaitaand whether that's a good idea13:43
smcginnisMimes are never a good idea.13:43
rosmaitasmcginnis: i can't hear you13:43
cdentyou both need to go sit on the naughty step13:44
cdentrosmaita: I'd say the issue here is that the validation_data is being marked out as a separate in the representation. If checksum, os_hash_algo, and os_hash_value are legit members of the representation of the 'locations' attribute, then just pass those and _in_code_ be aware that they are validation bits13:47
cdentotherwise you are not truly doing a replace operation (from a json-patch standpoint)13:47
rosmaitacdent: tjat13:47
rosmaitathat's the key issue, we aren't doing a replace13:48
cdentit sure looks like you are :)13:48
rosmaitathe locations attribute has a 'metadata' property, which is a json object iirc, but it doesn't have individual checksum, os_hash_* properties13:49
rosmaitaand we don't really want to leave 'checksum' as a location metadata item, we want there to be only one true checksum, as an image property13:50
*** tosky__ has joined #openstack-sdks13:51
*** tosky has quit IRC13:51
rosmaitacdent: but that's probably too much detail.  i guess the key thing is that a json-patch replace operation should actually replace stuff or fail (and not do weird side-effect stuff like we're proposing)13:51
*** tosky__ is now known as tosky13:52
cdentyou say in one of your initial comments " because the "validation_data" object does not exist in the image/location schema; it's sort of an instruction, really, that produces a side effect (the population of other properties on that image)". Can you just populate those properties?13:52
cdentyes: if you're using json-patch replace, it should do json-patch replace, not some special glance-only magic13:52
rosmaitacdent: yes, that's the alternative (but those properties are currently read-only in the schema, which is a sticking point)13:52
rosmaitathe issue is that we only want these properties to be settable under one specific circumstance, and never at any other time13:53
cdentmaking them writable during certain states is probably OK13:53
cdentrosmaita: Have I helped or just made it worse?13:58
rosmaitacdent: thinking!13:58
rosmaitacdent: last question ... if we make these writable under one tiny circumstance, then we have to remove readOnly: true from the schema for them, right?13:59
cdentI think that depends on how you are using and publishing the schema. In my mind schema are a validation tool used indepdently for each method:resource pair, not a contract in an of themselves14:01
*** olivierb_ has joined #openstack-sdks14:02
rosmaitacdent: thanks, that is helpful and will give us something to think about14:03
cdentyou're welcome14:03
*** olivierb has quit IRC14:03
*** adriant has quit IRC14:03
*** adriant has joined #openstack-sdks14:04
*** bobh has joined #openstack-sdks14:04
*** ttsiouts has quit IRC14:30
*** ttsiouts has joined #openstack-sdks14:40
*** Shrews has quit IRC14:45
*** slaweq has quit IRC14:48
*** Shrews has joined #openstack-sdks14:53
*** bobh has quit IRC14:54
*** slaweq has joined #openstack-sdks14:55
*** bobh has joined #openstack-sdks15:31
*** ttsiouts has quit IRC15:31
*** Luzi has joined #openstack-sdks15:47
*** bobh has quit IRC16:02
*** slaweq has quit IRC16:09
*** slaweq has joined #openstack-sdks16:09
*** ttsiouts has joined #openstack-sdks16:12
*** ttsiouts has quit IRC16:15
*** ttsiouts has joined #openstack-sdks16:16
*** ttsiouts has quit IRC16:20
*** dims has quit IRC16:28
*** olivierb_ has quit IRC16:29
*** dims_ has joined #openstack-sdks16:35
Luzimordred are you there?16:37
mordredLuzi: *sortof* - I'm at a conference so I'm in and out16:37
Luziokay, short question: it is planned to use openstacksdk in more projects right?16:38
Luzilike nova and cinder maybe?16:38
smcginnisNothing active that I've seen, but not out of the question.16:39
mordredLuzi: yes - it's already in use in heat, senlin and masakari16:42
mordredLuzi: once the 1.0 is cut, I'll start poking at making patches for folks to make that possible16:42
mordredLuzi: I don't know that the various services have agreed that they want such a migration yet - but from my/sdk point of view, once 1.0 is out it's a great idea16:43
smcginnismordred: Forum topic?16:43
Luzimordred, thank you for now :)16:44
smcginnisToo late now to be proposed, but we may be able to find a time for it if there is interest/need.16:44
*** mhen has joined #openstack-sdks16:44
*** e0ne has quit IRC16:47
mordredsmcginnis: yah. I was supposed to talk to nova about it in denver - but I missed the irc ping16:50
*** Luzi has quit IRC17:02
*** bobh has joined #openstack-sdks17:14
*** jpich has quit IRC17:32
*** olivierb has joined #openstack-sdks17:41
*** e0ne has joined #openstack-sdks18:02
*** imacdonn has quit IRC18:21
*** imacdonn has joined #openstack-sdks18:21
*** cdent has quit IRC18:33
openstackgerritMonty Taylor proposed openstack/openstacksdk master: Split advanced networking services into a job
*** e0ne has quit IRC18:45
*** e0ne has joined #openstack-sdks18:48
*** e0ne has quit IRC19:10
kmallocmordred: how far is SDK away from being ... usable say, in lieu of keystoneclient?19:35
kmallocmordred: i kindof want to leap early towards dropping ksc to the curb (new stuff only in SDK)19:36
* kmalloc is asking your opinion and will make a personal assessment.19:36
mordredkmalloc: we're very close to a 1.019:37
mordredkmalloc: as soon asI can get the tests to stop OOMing19:37
kmallocmordred: re-stating what i said in -keystone19:38
kmallocmordred: because i want to jump early like we did for OSC as the cli19:38
kmallocmordred: i would love to draw the line in the sand this release and say "all new stuff goes in SDK, ksc is deprecated and will see no new changes except for compat/security if an API is materially changed [see security reasons]"19:39
kmallocmordred: specifically... for new things like oslo.limit19:39
kmallocmordred: so.. yay!19:39
kmallocmordred: and boo OOMing19:39
mordredkmalloc: yes - I tihnk we're in a good place for that19:40
mordredkmalloc: I don't know that we're at feature parity for the existing thing19:40
kmalloccool. I'll make my -1 a little less soft on forklifting in ksc into oslo.limit19:41
kmallocand say "lets use SDK"19:41
kmalloc(referencing this convo)19:42
kmalloc if you want to weigh in19:44
kmalloccommented on it saying it's better to add support to SDK if needed than lean on ksc at this point.19:44
kmallocit's a super small set of API calls.19:44
kmallocwe use there.19:44
mordredkmalloc: I _certainly_ think it's valuable to start new dev that way. adding comment now19:44
mordredkmalloc: well, and you can just use the rest layer worst case19:45
kmallocyeah, i said in my initial comment, use KSA not KSC.19:45
kmallocbut figured I should talk here before firming up the -119:45
kmallocnow i'm saying "SDK"19:45
kmalloci will also push hard that all new stuff will be in SDK vs in KSC.19:45
kmallocit does mean we'll need to look at how hard it will be to re-write our ksc-plugin for OSC under SDK.19:46
kmallocshould be... doable19:46
kmallocif we can make our plugin SDK, then i know everything else could lean on SDK and be 90% parity19:46
kmallocand 90% is good enough imo to deprecate (freeze) ksc.19:47
kmallocand that saves us the headache of fixing ksc's weird session stuff that is there for compat19:48
kmallocmordred: in the interest in sharing eyebleeding patches... because... well we can19:50
kmallocmordred: ::will make your eyes bleed::19:50
kmallocmordred: but that is the worst forklift of keystone -> flask19:51
*** gildub has joined #openstack-sdks20:06
*** slaweq has quit IRC20:10
*** slaweq has joined #openstack-sdks20:11
*** gildub has quit IRC20:15
*** olivierb has quit IRC20:47
*** bobh has quit IRC20:51
*** bobh has joined #openstack-sdks20:56
dtroyerkmalloc: it's very easy to change commands to use the SDK, have a look at the network commands for how to use it directly, specifically security groups which handle both neutron and nova-net show how to hop between two at the same time21:05
kmallocYep. Was looking at it just now21:06
kmallocAbout to embark on a "strip ksc from osc" crusade :)21:06
dtroyerthere are also some uses of sdk-network in the compute server commands IIRC21:06
kmallocIf osc is on SDK for keystone, I can make the case ksc can die a slow death of bit rot.21:07
kmallocAnd all new things go sdk (carrot) for keystone.21:07
kmallocSimilar to how ksc command line did a while back.21:07
dtroyersecond verse same as the first…21:08
* dtroyer now has Herman's Hermits singing away in his head21:10
*** slaweq has quit IRC21:30
*** rosmaita has left #openstack-sdks21:35
kmallocwoo, just got a new mechanical keyboard, and loving it22:04
kmallocyay cherry silver switches22:04
kmalloc(and my other one for my workstation is cherry clears)22:04
* kmalloc has a mechanical keyboard problem.22:05
*** bobh has quit IRC22:07
*** slaweq has joined #openstack-sdks22:11
*** slaweq has quit IRC22:16
*** tosky has quit IRC22:24
*** mriedem has quit IRC23:51

Generated by 2.15.3 by Marius Gedminas - find it at!