Earlier  
Later
New Search
Posted Nick Remark
#openstack-sdks - 2018-05-03
14:18:55 dtantsur mordred: o/ to be honest, os_ironic_node is a bit of a mess.. I don't quite get why the same command does provisioning and setting maintenance :) anyway, is it possible to attach VIFs with it? and overall, are you open to developing something more high-level there?
14:19:45 mordred dtantsur: I have no idea why it is how it is - and yes, if you want to make something better and/or more high level ABSOLUTELY
14:20:01 mordred dtantsur: I'll happily accept it upstream and add you to the maintainers list for it
14:20:39 dtantsur heh, okay :) I'll see what I can do. It won't be quick though - I have a bit of prototyping ahead first.
14:21:28 mordred umbSublime: otherwise, we'd need to add a Resource for aggregates in openstack/compute/v2 - like probably openstack/compute/v2/aggregate.py - and then some methods in openstack/compute/v2/_proxy.py to go along with it
14:21:44 mordred umbSublime: it shouldn't be too hard to add if you feel like making a patch
14:22:18 umbSublime mordred: yah I'm getting more and more familiar with the code base every day. I'll consider it for sure
14:23:30 mordred cool. in the mean time, you should be able to just make direct rest calls when you hit things without direct support
14:30:42 umbSublime indeed that works as intented !
14:40:02 mordred \o/
14:41:14 mordred cmurphy: I think what pooja_jadhav might have been getting at is that keystoneauth has a set of config options and registration methods that can be used to add them to oslo.config things
14:42:02 mordred like register_adapter_conf_options
14:43:10 mordred so if nova, for instance, wanted to set the split_loggers option on an Adapter they're using, currently all of that flows through the nova.ini file - and if we don't have a split_loggers option in register_*_conf_options, then it gets awkward to set
14:43:41 mordred I think it might want to be in register_session_conf_options actually
15:24:12 openstackgerrit Merged openstack/cliff master: Remove travis.yml https://review.openstack.org/566010
16:01:12 elmiko dtantsur: ping
16:01:18 dtantsur o/
16:48:52 edleafe elmiko: dtantsur: ready for review https://etherpad.openstack.org/p/api-sig-newsletter
16:50:07 edleafe <homer> Mmmm... fried brain </homer>
16:52:48 edleafe dtantsur: https://www.youtube.com/watch?v=dc77--BjFYQ
16:52:57 dtantsur hehe
17:00:09 elmiko edleafe: lgtm
17:02:58 edleafe sent
17:06:21 elmiko thanks edleafe, heads up, i'll be out next week
17:06:26 elmiko dtantsur|afk: ^^
17:25:11 edleafe elmiko: ack
17:31:31 jroll fwiw, I did some graphql in the time I spent away from openstack. super awesome for quickly iterating on a product, especially the separation between front and back end
17:31:57 jroll also, pretty neat on the backend, in terms of only building the response you need and such, in general writing the code was pleasant
17:32:27 jroll that said, the python tooling for graphql backends is absolutely terrible, and if we started using it I highly suspect we'd end up writing our own
17:32:42 mordred jroll: awesome
17:35:01 mordred jroll: yah - it seems like a thing like oaktree would be an excellent place (especially since doing joins across things like servers, networks, subnets and ports is a legit thing)
17:36:06 jroll ++
17:46:26 _alastor_ I'm trying to add some Cinder v3 APIs to the openstacksdk, but I'm running into an issue where the "Body" resource I've defined on a "Resource" type is not getting populated
17:46:37 _alastor_ Example: http://paste.openstack.org/show/720311/
17:47:38 _alastor_ The resulting object does not have the 'extra_specs' body attribute populated and the '_body' attribute is empty
17:48:24 _alastor_ But from the debug curl call, you can see that the data was received
17:51:41 edleafe jroll: hope you can join our discussion in Vancouver!
17:52:27 elmiko jroll: i think your comments on this email thread would be most welcome, http://lists.openstack.org/pipermail/openstack-dev/2018-April/129987.html
17:53:08 jroll edleafe: I cannot :(
17:53:38 jroll elmiko: I've been following along, was waiting to see where it went for a bit
17:56:24 edleafe heh, jaypipes already poo-pooed the idea. <shock!>
18:39:24 elmiko jroll: ++
18:48:06 openstackgerrit Monty Taylor proposed openstack/os-client-config master: Allow monkeypatching CONFIG_FILES https://review.openstack.org/566139
18:53:39 openstackgerrit Monty Taylor proposed openstack/os-client-config master: Allow monkeypatching CONFIG_FILES https://review.openstack.org/566139
19:22:53 _alastor_ nevermind, looks like I needed to define a custom list function similar to this one for Server_IPs: https://github.com/openstack/openstacksdk/blob/master/openstack/compute/v2/server_ip.py#L37
20:19:29 _alastor_ I can't find any examples for simple operations with the SDK. Creation/Listing examples exist, but no example for how to modify an SDK resource
20:19:41 _alastor_ For example, how do I go about changing the name of a volume using the SDK?
20:20:54 _alastor_ vol = conn.block_storage.get_volume('some-vol-id')
20:21:02 _alastor_ vol.name = "my-new-name"
20:21:07 _alastor_ then what?
20:22:30 _alastor_ Or maybe vol.update(conn.session, name="my-new-name")?
20:25:47 _alastor_ Maybe objects are look-but-don't-touch once created?
20:28:59 openstackgerrit Monty Taylor proposed openstack/keystoneauth master: Implement service_type alias lookups https://review.openstack.org/462218
20:29:00 openstackgerrit Monty Taylor proposed openstack/keystoneauth master: Add methods to get all of the version data https://review.openstack.org/559154
20:29:01 openstackgerrit Monty Taylor proposed openstack/keystoneauth master: Make VersionData class https://review.openstack.org/564469
20:29:02 openstackgerrit Monty Taylor proposed openstack/keystoneauth master: Turn normalize_status into a class https://review.openstack.org/564110
20:29:03 openstackgerrit Monty Taylor proposed openstack/keystoneauth master: Infer version from old versioned service type aliases https://review.openstack.org/564299
20:29:54 openstackgerrit Monty Taylor proposed openstack/keystoneauth master: Use Status variables in tests https://review.openstack.org/564258
20:30:02 openstackgerrit Monty Taylor proposed openstack/keystoneauth master: Reference class variable in Status https://review.openstack.org/564262
#openstack-sdks - 2018-05-04
03:09:30 pooja_jadhav mordred: Hi
10:03:57 frickler seems there is a regression in os-client-config==1.31.0 breaking shade amongst other things https://bugs.launchpad.net/os-client-config/+bug/1768813
10:03:57 openstack Launchpad bug 1768813 in os-client-config "config.get_cache_expiration_time() function missing in 1.31.0 release" [Undecided,New]
10:03:59 frickler mordred: ^^
13:03:49 openstackgerrit David Shrewsbury proposed openstack/os-client-config master: Add these calls back to OCC https://review.openstack.org/566308
13:04:15 openstackgerrit David Shrewsbury proposed openstack/os-client-config master: Add cache API methods back to OCC https://review.openstack.org/566308
13:04:53 Shrews mordred: 566308 should add the cache API calls back, but it seems our tests are now testing openstacksdk and not os-client-config APIs
13:05:18 Shrews mordred: since we make those calls in occ tests and they apparently work
13:05:24 Shrews not sure how to correct that
13:05:34 Shrews frickler: ^^
13:27:31 pooja_jadhav cmurphy : Hi
13:43:22 openstackgerrit Artem Goncharov proposed openstack/os-client-config master: fix link to openstacksdk in deprecation block https://review.openstack.org/566318
13:50:55 mordred Shrews: looking
13:51:21 mordred Shrews: also the sdk functional tests keep hitting flapping errors related to floating ips - so I'm trying to clean that up
13:51:36 Shrews yay
13:52:33 openstackgerrit David Shrewsbury proposed openstack/os-client-config master: Add cache API methods back to OCC https://review.openstack.org/566308
13:52:35 frickler Shrews: hmm, I think you are patching the wrong location, the issue for me is with config.OpenStackConfig() and not cloud_config.Config()
13:53:03 mordred AH
13:53:04 Shrews pooja_jadhav: ah, Closes-Bug. couldn't remember it and couldn't find it any docs (it's all shuffled since last i looked)
13:53:07 mordred that makes more sense to me
13:53:14 frickler Shrews: also yes, would be good to have tests for that
13:55:06 pooja_jadhav Shrews: Hi, I am not getting what you are trying to say
13:55:21 openstackgerrit Monty Taylor proposed openstack/openstacksdk master: Clean up floating ip tests https://review.openstack.org/566320
13:55:58 Shrews pooja_jadhav: ooh, sorry. that was meant for someone else
13:56:38 pooja_jadhav shrews: ohk
13:57:29 openstackgerrit Merged openstack/os-client-config master: fix link to openstacksdk in deprecation block https://review.openstack.org/566318
13:58:07 Shrews ok, i'm confused since those calls originally existed in CloudConfig
13:58:07 openstackgerrit Artem Goncharov proposed openstack/openstacksdk master: close files after open in unit/base https://review.openstack.org/566321
13:59:45 frickler Shrews: this is the code sample I posted on the bug report which is broken with the new release https://github.com/ansible/ansible/blob/devel/contrib/inventory/openstack.py#L193-L204
14:00:03 openstackgerrit Monty Taylor proposed openstack/os-client-config master: Allow monkeypatching CONFIG_FILES https://review.openstack.org/566139
14:00:04 openstackgerrit Monty Taylor proposed openstack/os-client-config master: Add cache methods back to OpenSackConfig https://review.openstack.org/566322
14:00:12 mordred Shrews: there were two sets of them
14:00:28 Shrews mordred: oh. well that's not confusing
14:00:34 mordred yah - it was terrible
14:00:37 mordred the CloudConfig ones originally called the OpenStackConfig ones
14:01:32 mordred BUT - if you're just working with CloudConfig objects that's awkward - so CloudConfig got fixed to not need the OpenStackConfig methods anymore - and in sdk OpenStackConfig doens't have the methods because they're silly
14:01:53 mordred and I totally missed keeping them for backwards compat in the occ patch
14:02:27 Shrews i'm not clear on the fix then
14:02:47 mordred adding them back to OpenStackConfig so that occ users who were using them don't break
14:10:25 Shrews mordred: how do you get from occ.OpenStackConfig to the osdk.CloudRegion where those calls are defined?
14:10:49 Shrews those calls seem like they should be region independent

Earlier   Later