Earlier  
Later
New Search
Posted Nick Remark
#openstack-sdks - 2017-10-04
20:53:22 briancurtin no.
20:54:23 mriedem no you don't know, or no no one is working on it?
20:56:45 briancurtin no, 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:53 briancurtin it’s pretty basic though
20:57:12 mriedem ok, yeah, should be - i've just never done any sdk coding, so wanted to ask before spending any time on it
20:57:19 mriedem for now i sent someone to novaclient
20:57:24 briancurtin great
20:59:54 flanders_ Have you looked at python shade SDK mriedem ?
21:00:11 mriedem nope
21:00:19 mriedem i really don't venture outside of novaclient
21:00:31 flanders_ No worries.
21:00:46 flanders_ Good luck.
21:00:56 mriedem flanders_: so i've heard you have some gap analysis charts
21:01:08 mriedem would that be so detailed to the point of knowing some of these major gaps in the compute api in the openstacksdk?
21:01:54 flanders_ Analysis was usability study on getting started quickly with each of the sdks
21:02:05 flanders_ Shade is the easiest, in short.
21:02:46 flanders_ Worth talking with chairs of API-SIG for feedback via #openstack-api
21:02:47 briancurtin mriedem: 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:49 mriedem to get started, but not the most feature complete
21:03:01 briancurtin API-SIG and openstack-api has nothing to do with this project.
21:03:10 mriedem flanders_: ^
21:03:36 briancurtin yeah 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 using
21:03:56 flanders_ My bad briancurtin - mea culpa
21:04:09 mriedem briancurtin: tbc, i was replying to flanders_ about shade
21:04:13 edleafe flanders_: FWIW, we hang out here, not #openstack-api
21:05:05 flanders_ Duly noted edleafe
21:05:19 mriedem hells bells it's edleafe
21:09:51 mordred mriedem: 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 other
21:10:11 mriedem mordred: so if i worked on extra specs in the sdk, that would ultimately benefit shade?
21:10:28 mriedem and the sdk
21:12:51 mordred mriedem: sure nuff
21:18:17 xarses to echo the conversation that was going on in #openstack-dev " Given the openstack python sdk, how is one expected to CRUD flavor properties? https://developer.openstack.org/sdks/python/openstacksdk/users/proxies/compute.html 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:38 xarses API is: https://developer.openstack.org/api-ref/compute/#flavors-extra-specs-flavors-os-flavor-extra-specs
21:19:51 briancurtin xarses: create_flavor would take any of the names on https://developer.openstack.org/sdks/python/openstacksdk/users/resources/compute/v2/flavor.html#openstack.compute.v2.flavor.Flavor, so create_flavor(disk=blah, ram=blah, ephemeral=False, …) and calling that does what?
21:20:24 mordred adding extra specs to a flavor is an additional call - it's not part of the create_flavor flow
21:20:43 briancurtin sure, but create_flavor shouldn’t be doing nothing
21:20:53 mordred once you have a flavor, you POST to /flavors/{id}/os-extra_specs
21:21:04 mordred briancurtin: agreed
21:22:08 xarses f = {'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:17 xarses create_flavor(**f)
21:22:23 xarses returns the flavor object
21:22:42 xarses no info about that keys where ignored
21:23:22 briancurtin yeah, should probably output that and/or fail. i believe there was a ticket to output a warning with the ignored keys
21:23:29 xarses I see two problems, it took extra keys
21:23:34 briancurtin everything you pass has to match up with something on the associated resource
21:23:51 xarses and that there is no interface in sdk.compute to set os-extra_specs
21:24:03 briancurtin yeah well someone has the add the later
21:24:43 briancurtin im also not sure how you figured you could just send an arbitrary list of keys
21:25:10 briancurtin (that’s horribly worded…it’s not a list. arbitrary keyword arguments)
21:25:37 xarses by sending them and it just returning the result that I sort-of expected and moving on
21:25:57 xarses then accidentally reviewing the output of `openstack flavor list --long` and seeing they where missing
21:26:49 xarses I get the most frustrated when the sdk objects don't resemble what you get back on the CLI (like keys are wholly renamed)
21:27:48 briancurtin that’s a feature of the SDK, as there are several naming formats across openstack REST responses, including keys which cannot be python names
21:28:10 briancurtin for example, most of what you tried to send
21:31:58 briancurtin people 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:37:29 mordred ++
22:16:23 openstackgerrit Dean Troyer proposed openstack/osc-lib master: --os-profile option suddenly causes trouble in unit tests https://review.openstack.org/509662
#openstack-sdks - 2017-10-05
01:09:50 openstackgerrit OpenStack Proposal Bot proposed openstack/osc-lib master: Updated from global requirements https://review.openstack.org/509448
01:12:02 openstackgerrit OpenStack Proposal Bot proposed openstack/python-openstackclient master: Updated from global requirements https://review.openstack.org/509460
02:25:48 openstackgerrit Hongbin Lu proposed openstack/python-openstackclient master: Added AddNetwork command to server https://review.openstack.org/509209
02:41:57 openstackgerrit OpenStack Proposal Bot proposed openstack/osc-lib master: Updated from global requirements https://review.openstack.org/509448
02:43:59 openstackgerrit OpenStack Proposal Bot proposed openstack/python-openstackclient master: Updated from global requirements https://review.openstack.org/509460
02:44:35 openstackgerrit Merged openstack/python-openstackclient master: Support creating unaddress neutron port https://review.openstack.org/504817
02:57:57 openstackgerrit OpenStack Proposal Bot proposed openstack/osc-lib master: Updated from global requirements https://review.openstack.org/509448
02:59:51 openstackgerrit OpenStack Proposal Bot proposed openstack/python-openstackclient master: Updated from global requirements https://review.openstack.org/509460
03:13:45 openstackgerrit OpenStack Proposal Bot proposed openstack/osc-lib master: Updated from global requirements https://review.openstack.org/509448
03:15:40 openstackgerrit OpenStack Proposal Bot proposed openstack/python-openstackclient master: Updated from global requirements https://review.openstack.org/509460
03:34:02 openstackgerrit OpenStack Proposal Bot proposed openstack/osc-lib master: Updated from global requirements https://review.openstack.org/509448
03:35:57 openstackgerrit OpenStack Proposal Bot proposed openstack/python-openstackclient master: Updated from global requirements https://review.openstack.org/509460
04:03:41 openstackgerrit OpenStack Proposal Bot proposed openstack/osc-lib master: Updated from global requirements https://review.openstack.org/509448
04:05:37 openstackgerrit OpenStack Proposal Bot proposed openstack/python-openstackclient master: Updated from global requirements https://review.openstack.org/509460
04:19:53 openstackgerrit OpenStack Proposal Bot proposed openstack/osc-lib master: Updated from global requirements https://review.openstack.org/509448
04:21:49 openstackgerrit OpenStack Proposal Bot proposed openstack/python-openstackclient master: Updated from global requirements https://review.openstack.org/509460
05:30:33 openstackgerrit shogoadachi proposed openstack/python-openstackclient master: Accept 0 for --min-disk and --min-ram https://review.openstack.org/507345
06:11:34 openstackgerrit OpenStack Proposal Bot proposed openstack/osc-lib master: Updated from global requirements https://review.openstack.org/509448
06:13:38 openstackgerrit OpenStack Proposal Bot proposed openstack/python-openstackclient master: Updated from global requirements https://review.openstack.org/509460
13:51:41 openstackgerrit OpenStack Proposal Bot proposed openstack/python-openstackclient master: Updated from global requirements https://review.openstack.org/509460
16:35:58 elmiko lol, i am just now seeing last weeks newsletter
16:36:08 elmiko calling me out as a blabbermouth... XD
16:39:26 cdent naw mate, that’s calling you out as the social glue
16:43:26 elmiko haha =)
16:43:37 edleafe yes, elmiko is very sticky
16:52:30 elmiko cdent, edleafe, https://etherpad.openstack.org/p/api-sig-newsletter
16:53:16 cdent “Firstly,”
16:53:43 elmiko First and foremost?
16:54:32 cdent too
16:54:33 cdent many
16:54:34 cdent notes
16:54:39 elmiko oh fine...
16:55:24 elmiko i can't suppress my folksiness, sorry
16:57:17 cdent even though it is not a guideline, may as well link ed’s changes (i’ve done it)
16:57:42 edleafe reasonable bending of the rules
16:58:03 elmiko +1, thanks
16:58:25 edleafe ok, I'm good with it
16:58:39 cdent me too
17:00:14 elmiko are we still limiting distribution to the dev-ml?
17:02:20 edleafe yeah
17:03:43 cdent I suppose eventually we should ask ourselves if/when we include api-consumers
17:04:09 elmiko that's kinda what i was wondering, just wanted to make sure we hadn't change it yet
17:04:11 cdent not getting any traffic yet, though

Earlier   Later