Wednesday, 2017-10-04

*** bobh has joined #openstack-sdks00:01
*** bobh has quit IRC00:02
*** bobh has joined #openstack-sdks00:04
*** rajathagasthya has quit IRC00:07
*** flanders_ has quit IRC00:19
*** bobh has quit IRC00:20
*** bobh has joined #openstack-sdks00:36
*** rajathagasthya has joined #openstack-sdks00:41
*** bobh has quit IRC00:53
*** bobh has joined #openstack-sdks00:55
*** markvoelker has joined #openstack-sdks01:01
*** Kevin_Zheng has joined #openstack-sdks01:27
*** bobh has quit IRC01:34
*** ragasthya has joined #openstack-sdks01:37
*** gouthamr has quit IRC01:37
*** rajathagasthya has quit IRC01:38
*** fzdarsky_ has joined #openstack-sdks01:47
*** fzdarsky has quit IRC01:50
*** erlon has quit IRC03:01
*** ragasthya has quit IRC03:28
*** Kevin_Zheng has quit IRC03:37
*** boris_42_ has quit IRC03:44
*** gildub has joined #openstack-sdks03:48
*** markvoelker has quit IRC05:20
*** cfriesen has quit IRC06:04
*** rm_work has quit IRC06:11
*** rm_work has joined #openstack-sdks06:14
*** annp has joined #openstack-sdks06:24
*** edmondsw has joined #openstack-sdks06:33
*** edmondsw has quit IRC06:37
*** jgriffit1 has joined #openstack-sdks06:44
*** markvoelker has joined #openstack-sdks07:21
*** gildub has quit IRC07:30
slaweqbriancurtin: hello, can You take a look once again at
slaweqbriancurtin: Your W+1 disappeared probably because of zuul v2 <--> v3 migrations07:33
*** flanders_ has joined #openstack-sdks07:40
*** fzdarsky_ has quit IRC07:45
*** ralonsoh has joined #openstack-sdks07:47
*** markvoelker has quit IRC07:55
*** jpich has joined #openstack-sdks07:55
*** fzdarsky has joined #openstack-sdks08:08
*** edmondsw has joined #openstack-sdks08:21
*** edmondsw has quit IRC08:26
slaweqhi, when will be some new version of openstacksdk released?08:47
slaweqI need one feature from it to make properly patch
slaweqand I will also need one more patch from SDK for OSC later08:48
slaweqis there any schedule of releases for openstack sdk?08:49
*** dfflanders has joined #openstack-sdks08:50
*** markvoelker has joined #openstack-sdks08:52
flanders_slaweq: you'll want to chat with the API-SIG over on #openstack-api09:01
slaweqflanders_: ok, thx09:01
slaweqI will talk there09:01
flanders_slaweq: ask for edleafe09:02
*** e0ne has joined #openstack-sdks09:22
*** markvoelker has quit IRC09:26
slaweqok, thx for tip flanders_09:31
*** sdague has joined #openstack-sdks09:38
*** edmondsw has joined #openstack-sdks10:09
*** edmondsw has quit IRC10:13
*** fzdarsky has quit IRC10:21
*** markvoelker has joined #openstack-sdks10:23
*** annp has quit IRC10:24
*** jkilpatr has quit IRC10:35
*** fzdarsky has joined #openstack-sdks10:42
*** dfflanders has quit IRC10:49
*** cdent has joined #openstack-sdks10:54
*** markvoelker has quit IRC10:55
*** fzdarsky_ has joined #openstack-sdks10:55
*** dave-mccowan has joined #openstack-sdks11:01
*** jkilpatr has joined #openstack-sdks11:10
*** dave-mcc_ has joined #openstack-sdks11:11
*** dave-mccowan has quit IRC11:13
*** fzdarsky_ has left #openstack-sdks11:15
briancurtinslaweq: not sure what he’s talking about, this is the right place. i’ll take a look at what else has been merged and i can put together a release11:18
briancurtinslaweq: i just w+1’ed it so it should be merged soon11:20
*** dtantsur|afk is now known as dtantsur11:22
openstackgerritMerged openstack/python-openstacksdk master: Add support for network quota details command
slaweqbriancurtin: thx a lot11:28
slaweqbriancurtin: in fact I will need for OSC patches also this patch which You just w+1'ed :)11:29
*** markvoelker has joined #openstack-sdks11:53
*** ralonsoh has quit IRC12:02
*** edmondsw has joined #openstack-sdks12:16
*** edmondsw_ has joined #openstack-sdks12:17
*** edmondsw has quit IRC12:21
*** markvoelker has quit IRC12:26
*** markvoelker has joined #openstack-sdks12:27
*** e0ne has quit IRC12:31
*** e0ne has joined #openstack-sdks12:32
*** lbragstad has joined #openstack-sdks13:05
mordredbriancurtin: sorry for the delay, yesterday was a bit hectic ...13:08
*** flanders_ has quit IRC13:09
mordredbriancurtin: I'm not anticipating much moving or shaking this week what with all the zuul v3 stuff flying around this week.13:10
mordredbriancurtin:  that said, there was never any intention of removing any existing cores, so I don't think there shouldn't be any time-related issues for getting that in13:12
*** chlong_ has joined #openstack-sdks13:22
*** ralonsoh has joined #openstack-sdks13:32
*** cleong has joined #openstack-sdks13:44
*** gouthamr has joined #openstack-sdks13:53
*** stephenfin has quit IRC14:00
*** stephenfin has joined #openstack-sdks14:01
*** edmondsw_ is now known as edmondsw14:07
*** d0ugal has quit IRC14:10
*** bobh has joined #openstack-sdks14:11
*** d0ugal has joined #openstack-sdks14:13
*** d0ugal has quit IRC14:13
*** d0ugal has joined #openstack-sdks14:13
*** cfriesen has joined #openstack-sdks14:38
*** sdague has quit IRC14:50
*** bobh has quit IRC14:56
*** edleafe- has joined #openstack-sdks15:03
*** edleafe has quit IRC15:06
*** sdague has joined #openstack-sdks15:14
*** rajathagasthya has joined #openstack-sdks15:15
*** erlon has joined #openstack-sdks15:24
*** ragasthya has joined #openstack-sdks15:48
*** rajathagasthya has quit IRC15:50
*** edleafe- is now known as edleafe15:52
*** bobh has joined #openstack-sdks15:56
*** bobh has quit IRC16:01
*** jpich has quit IRC16:32
*** jgriffith is now known as Guest7311116:39
*** jgriffit1 is now known as jgriffith16:39
*** jgriffith_ has joined #openstack-sdks16:39
*** e0ne has quit IRC16:40
*** dtantsur is now known as dtantsur|afk16:47
*** efried is now known as efried_nomnom17:25
*** ralonsoh has quit IRC17:30
*** markvoelker has quit IRC17:30
*** markvoelker has joined #openstack-sdks17:30
*** lbragstad has quit IRC17:34
*** jgriffith has quit IRC17:45
*** jgriffith_ is now known as jgriffith17:45
*** lbragstad has joined #openstack-sdks17:57
*** edmondsw has quit IRC18:20
*** edmondsw has joined #openstack-sdks18:23
*** e0ne has joined #openstack-sdks18:25
*** edmondsw has quit IRC18:28
*** efried_nomnom is now known as efried18:32
openstackgerritHongbin Lu proposed openstack/python-openstackclient master: Added AddNetwork command to server
*** edmondsw has joined #openstack-sdks18:48
*** cdent has quit IRC18:55
*** gouthamr has quit IRC18:58
*** gouthamr_ has joined #openstack-sdks18:58
*** edmondsw has quit IRC19:06
*** edmondsw has joined #openstack-sdks19:06
*** chlong_ has quit IRC19:16
*** lbragstad has quit IRC19:35
*** ragasthya has quit IRC19:39
*** bobh has joined #openstack-sdks19:41
*** flanders_ has joined #openstack-sdks20:26
*** lbragstad has joined #openstack-sdks20:27
*** jkilpatr has quit IRC20:44
*** cleong has quit IRC20:45
*** gouthamr_ has quit IRC20:46
*** mriedem has joined #openstack-sdks20:52
mriedemso apparently the openstack python sdk doesn't have any support for flavor extra specs20:52
mriedemwhich is pretty basic if you're using nova20:52
mriedemdoes anyone know if someone is already working on this?20:52
mriedemno you don't know, or no no one is working on it?20:54
briancurtinno, i didn’t get around to implementing that in my free time and i am not working on it nor will i be.20:56
briancurtinit’s pretty basic though20:56
mriedemok, yeah, should be - i've just never done any sdk coding, so wanted to ask before spending any time on it20:57
mriedemfor now i sent someone to novaclient20:57
flanders_Have you looked at python shade SDK mriedem ?20:59
mriedemi really don't venture outside of novaclient21:00
flanders_No worries.21:00
flanders_Good luck.21:00
mriedemflanders_: so i've heard you have some gap analysis charts21:00
mriedemwould that be so detailed to the point of knowing some of these major gaps in the compute api in the openstacksdk?21:01
flanders_Analysis was usability study on getting started quickly with each of the sdks21:01
flanders_Shade is the easiest, in short.21:02
flanders_Worth talking with chairs of API-SIG for feedback via #openstack-api21:02
briancurtinmriedem: i doubt anyone knows such a thing, but yeah, someone could look at the docs, look at the code, and implement what’s not there. same for just about everything ever.21:02
mriedemto get started, but not the most feature complete21:02
briancurtinAPI-SIG and openstack-api has nothing to do with this project.21:03
mriedemflanders_: ^21:03
briancurtinyeah it’s not the most feature complete because people building it weren’t on the server-side projects and no one on the server-side projects cared about SDK, so we built what we knew and what we were using21:03
flanders_My bad briancurtin - mea culpa21:03
mriedembriancurtin: tbc, i was replying to flanders_ about shade21:04
edleafeflanders_: FWIW, we hang out here, not #openstack-api21:04
flanders_Duly noted edleafe21:05
mriedemhells bells it's edleafe21:05
*** xarses has joined #openstack-sdks21:08
mordredmriedem: we've got flavor extra specs in shade - I expect we'll add support for it to sdk as we work on getting the shade layer and the sdk layer integrated with each other21:09
mriedemmordred: so if i worked on extra specs in the sdk, that would ultimately benefit shade?21:10
mriedemand the sdk21:10
mordredmriedem: sure nuff21:12
xarsesto echo the conversation that was going on in #openstack-dev "<xarses> Given the openstack python sdk, how is one expected to CRUD flavor properties? Seems to have no clue, and flavor_create took kwargs from me that it did nothing with (I initially figured that sending properties would have done it, but its ignored) "21:18
*** e0ne has quit IRC21:18
xarsesAPI is:
*** e0ne has joined #openstack-sdks21:19
briancurtinxarses: create_flavor would take any of the names on, so create_flavor(disk=blah, ram=blah, ephemeral=False, …) and calling that does what?21:19
*** e0ne has quit IRC21:19
*** e0ne has joined #openstack-sdks21:20
mordredadding extra specs to a flavor is an additional call - it's not part of the create_flavor flow21:20
*** e0ne has quit IRC21:20
briancurtinsure, but create_flavor shouldn’t be doing nothing21:20
mordredonce you have a flavor, you POST to /flavors/{id}/os-extra_specs21:20
mordredbriancurtin: agreed21:21
*** e0ne has joined #openstack-sdks21:21
xarsesf = {'property': {'hw:cpu_policy': 'dedicated', 'hw:cpu_sockets': 1, 'hw:cpu_threads': 2, 'cost': 148.5, 'hw:cpu_cores': 8, 'hw:cpu_thread_policy': 'prefer'}, 'vcpus': 16, 'ram': 32256, 'name': 'm32-c16-d320-as', 'disk': 320, 'id': 'e2193116-f4f6-4db1-9191-33ef7d958895'}21:22
*** e0ne has quit IRC21:22
xarsesreturns the flavor object21:22
*** e0ne has joined #openstack-sdks21:22
xarsesno info about that keys where ignored21:22
*** e0ne has quit IRC21:23
*** e0ne has joined #openstack-sdks21:23
briancurtinyeah, should probably output that and/or fail. i believe there was a ticket to output a warning with the ignored keys21:23
xarsesI see two problems, it took extra keys21:23
briancurtineverything you pass has to match up with something on the associated resource21:23
*** e0ne has quit IRC21:23
xarsesand that there is no interface in sdk.compute to set os-extra_specs21:23
briancurtinyeah well someone has the add the later21:24
briancurtinim also not sure how you figured you could just send an arbitrary list of keys21:24
briancurtin(that’s horribly worded…it’s not a list. arbitrary keyword arguments)21:25
xarsesby sending them and it just returning the result that I sort-of expected and moving on21:25
xarsesthen accidentally reviewing the output of `openstack flavor list --long` and seeing they where missing21:25
xarsesI get the most frustrated when the sdk objects don't resemble what you get back on the CLI (like keys are wholly renamed)21:26
briancurtinthat’s a feature of the SDK, as there are several naming formats across openstack REST responses, including keys which cannot be python names21:27
briancurtinfor example, most of what you tried to send21:28
*** jkilpatr has joined #openstack-sdks21:28
briancurtinpeople want (wanted?) one place to do all of this, one format, one thing to install, consistency all around. a bunch of things get renamed in the process to make it usable for the masses, but yeah, if you’re looking at what are probably database column names or something, they don’t always match up 1-1 with the names in openstacksdk. on purpose.21:31
*** edmondsw has quit IRC21:32
*** edmondsw has joined #openstack-sdks21:32
*** edmondsw has quit IRC21:37
openstackgerritDean Troyer proposed openstack/osc-lib master: --os-profile option suddenly causes trouble in unit tests
*** gouthamr has joined #openstack-sdks22:27
*** lbragstad has quit IRC22:38
*** edmondsw has joined #openstack-sdks22:41
*** edmondsw has quit IRC22:46
*** bobh has quit IRC22:51
*** xarses has quit IRC22:57
*** sdague has quit IRC23:00
*** edmondsw has joined #openstack-sdks23:13
*** edmondsw has quit IRC23:35

Generated by 2.15.3 by Marius Gedminas - find it at!