Earlier  
Posted Nick Remark
#openstack-sdks - 2019-07-16
16:20:43 openstackgerrit Dmitry Tantsur proposed openstack/openstacksdk master: Correct endpoint_override discovery for service with dashes in their type https://review.opendev.org/671104
16:20:53 dtantsur mordred: I think I've figured out what causes troubles with inspector ^^
16:22:51 mordred dtantsur: headdesk
16:43:08 dtantsur yep
22:41:13 openstackgerrit Merged openstack/cliff master: Add Python 3 Train unit tests https://review.opendev.org/669445
#openstack-sdks - 2019-07-17
08:45:12 dtantsur gtema: morning, could you check https://review.opendev.org/#/c/671104/ please?
08:45:40 gtema dtantsur: morgen. Sure
08:45:45 gtema how was your exam?
08:47:03 gtema dtantsur: I would ask also you to do a review for me - https://review.opendev.org/#/c/659841/
08:47:52 dtantsur gtema: subjectively went well, still no results (takes 4-6 weeks)
08:48:03 gtema cool
09:05:58 stingrayza gtema, would you mind re-checking https://github.com/ansible/ansible/pull/57120 please? there's been an update since your last shipit :)
09:06:32 stingrayza mordred: you too please :) ^^
10:07:37 openstackgerrit Merged openstack/openstacksdk master: Correct endpoint_override discovery for service with dashes in their type https://review.opendev.org/671104
10:11:02 dtantsur mordred: could you make a release with ^^ please?
11:23:36 priteau Hi mordred. You approved an Ansible bugfix two weeks ago (https://github.com/ansible/ansible/pull/57364), I've now created pull requests for backports to 2.8 and 2.7
11:23:39 priteau https://github.com/ansible/ansible/pull/59107
11:23:41 priteau https://github.com/ansible/ansible/pull/59108
11:39:37 mordred dtantsur: remote: https://review.opendev.org/671244 Release 0.31.2 of openstacksdk
11:39:47 dtantsur thx!
12:23:27 ITD27M01_ mordred: Hello! We have added the version_added key to https://github.com/ansible/ansible/pull/51401 Could you check and review? If you have a minute for this.
12:38:47 mordred ITD27M01_: done. Shrews - wanna re-look?
12:39:33 Shrews sure
12:40:19 mordred Shrews: something something "approve changes" click click scroll click scroll click click emoji
12:42:44 Shrews mordred: have i ever mentioned how much i loathe GH interface?
12:43:24 mordred Shrews: it's so hard to use
12:48:31 Shrews mordred: that reminds me, i dont think sdk has an ansible test for the inventory plugin
12:48:51 Shrews or probably any of the newer modules
12:49:20 Shrews we should probably start requesting those for new modules
12:49:59 Shrews i can look at doing the inventory one when i have a second arm again
12:51:06 mordred Shrews: have you considered a robot arm?
12:51:07 Shrews (which im hoping is this evening after the dr appt)
12:53:39 Shrews if we arent requesting tests for new modules, then we may as well not have any
12:56:29 Shrews but i dont know how that workflow should go. cant have a test w/o the module. but adding an untested module before the test can also be bad
13:02:04 Shrews i guess a proper depends-on would work there
13:47:22 mordred Shrews: I think maybe we should finally figure out how to put the tests themselves into the ansible repo (we can make ansible-test tests that require a certain set of creds so the normal ansible runs won't try to run them) - and then update the devstack job in zuul to run ansible-test feeding it the devstack login information
13:47:38 mordred Shrews: there's enough work there that I haven't actually dug in to doing it yet
#openstack-sdks - 2019-07-18
16:00:10 edleafe Welcome to the API-SIG Office Hour!
16:01:00 elmiko \o/
16:01:27 edleafe elmiko: did you bring the balloons and party hats?
16:01:56 elmiko indeed!
16:05:54 elmiko it's been too quiet in here
16:06:20 dtantsur \o
16:06:33 dtantsur sorry for being so inactive recently - too many things happening around
16:08:02 edleafe dtantsur: There really hasn't been much going on here, so you didn't miss much :)
16:09:46 dtantsur I cannot also promise for it to become better soon..
16:12:43 elmiko edleafe: lol
16:13:12 elmiko ++ to what edleafe is saying, it's been slow recently but no worries dtantsur =)
16:59:51 elmiko take care edleafe dtantsur cdent , if i don't see ya before then, have a good weekend =)
17:00:13 edleafe ciao, elmiko!
17:00:28 dtantsur \o
#openstack-sdks - 2019-07-19
12:26:29 tobiash mordred: I've a question about the fault info on server objects. This is missing when fetching the server via get_server (event with details enabled) while it is present when fetching it via get_server_by_id
12:26:45 tobiash I didn't find out why that's the case
12:27:46 tobiash I've a change in nodepool that is related to this (https://review.opendev.org/671704) where I need to re-request a server to get that additional information
12:45:12 mordred tobiash: huh. that seems very weird to me. I'll have to dig in a bit - it's certainly not _intentional_ that those return different things
12:46:29 mordred tobiash: maybe nova doesn't return fault info in the server listing but does return it on the direct server fetch?
12:47:04 mordred if that's the case, then doing a second fetch in nodepool is probably the right choice, since we don't _normally_ want to do direct fetches because of scale
12:47:28 mordred and the cost of doing it when a server is at fault shoudl be an exception case ... still, I'll dig in and see what I can learn
13:07:40 tobiash thanks
15:45:29 openstackgerrit Dean Troyer proposed openstack/python-openstackclient master: Add host and hypervisor_hostname to create servers https://review.opendev.org/669609
17:27:59 openstackgerrit Merged openstack/python-openstackclient master: Fix BFV server list handling with --name-lookup-one-by-one https://review.opendev.org/668255
#openstack-sdks - 2019-07-22
14:27:28 openstackgerrit Andreas Jaeger proposed x/promstat master: Remove publishing to docs.openstack.org https://review.opendev.org/672058
18:48:05 openstackgerrit Andreas Jaeger proposed openstack/openstacksdk master: Update api-ref location https://review.opendev.org/672131
18:53:36 openstackgerrit Andreas Jaeger proposed openstack/os-service-types master: Update api-ref location https://review.opendev.org/672136
18:56:13 openstackgerrit Andreas Jaeger proposed openstack/python-openstackclient master: Update api-ref location https://review.opendev.org/672138
18:57:02 openstackgerrit Andreas Jaeger proposed openstack/service-types-authority master: Update api-ref location https://review.opendev.org/672139
#openstack-sdks - 2019-07-23
00:03:32 openstackgerrit Riccardo Pittau proposed openstack/openstacksdk master: Add set-boot-device to baremetal https://review.opendev.org/672190
01:24:26 openstackgerrit Merged openstack/python-openstackclient master: Update api-ref location https://review.opendev.org/672138
01:32:33 openstackgerrit Merged openstack/python-openstackclient master: Add host and hypervisor_hostname to create servers https://review.opendev.org/669609
09:05:22 openstackgerrit Riccardo Pittau proposed openstack/openstacksdk master: Add basic node traits support to baremetal https://review.opendev.org/672233
09:43:55 openstackgerrit Riccardo Pittau proposed openstack/openstacksdk master: Add set-boot-device to baremetal https://review.opendev.org/672190
11:04:37 openstackgerrit Riccardo Pittau proposed openstack/openstacksdk master: Add basic node traits support to baremetal https://review.opendev.org/672233
13:12:35 openstackgerrit Riccardo Pittau proposed openstack/openstacksdk master: Add basic node traits support to baremetal https://review.opendev.org/672233
14:05:32 openstackgerrit Merged openstack/service-types-authority master: Update api-ref location https://review.opendev.org/672139
14:05:48 openstackgerrit Merged openstack/os-service-types master: Update api-ref location https://review.opendev.org/672136
14:20:40 openstackgerrit OpenStack Proposal Bot proposed openstack/os-service-types master: Updated from OpenStack Service Type Authority https://review.opendev.org/672295
14:22:36 BlackDex hello there. With the openstack dynamic inventory, is there a way to force a specific IP address as the accessIP(v4) ???
14:22:46 BlackDex now it seems to just pick the first one in the line (seems to be sorted by network id)
15:16:56 mordred BlackDex: you can configure the network that such an IP should come from - one sec, lemme get a link
15:17:47 mordred BlackDex: https://docs.openstack.org/openstacksdk/latest/user/config/network-config.html see default_interface
17:36:03 Shrews mordred: got a sec for a rax related question?
17:39:54 mordred Shrews: sure!
17:39:59 mordred Shrews: am I going to like it?
17:40:43 Shrews mordred: well, gimme a moment... gotta organize a log paste for you
17:48:46 Shrews nm. maybe later when i unconfuse myself
18:04:33 Shrews mordred: ok, different question
18:05:33 Shrews mordred: keep seeing this error in nodepool logs: http://paste.openstack.org/show/754765/
18:07:06 Shrews mordred: i totally don't get the organization of sdk these days, but _IMAGE_OBJECT_KEY is waaaaay down in the base proxy class (because not sure why) and referenced way up in the image mixin. I don't see Connection deriving from the proxy class???
18:09:03 Shrews oh, wow. ok, there are all sorts of Proxy() classes
18:18:30 mordred Shrews: yah - the sdk layer has a Proxy() for each service
18:19:28 mordred Shrews: then on the Connection there shoudl be an instance of each one - so conn.image should be an instance of openstack.image.v2._proxy.Proxy
18:24:11 Shrews mordred: the Connection derives from ImageCloudMixin which, it looks like based on the (self reference to that attribute), assumes to be an instance of that Proxy, yet it is not. It's confusing to me
18:24:29 Shrews oops, extra ()'s there for some reason
18:25:11 mordred Shrews: it shouldn't - it should have a proxy, not is-a proxy - I think that's likely just a bug from pushing logic down into the proxy layer
18:26:11 mordred Shrews: the idea was to move as much logic from the shade layer into the proxy layer as made sense, so that all the basics would work no matter which layer you use - and so that the shade layer could then be business logic on top of a robust and working proxy layer
18:26:50 mordred Shrews: image was one of the first things to transition - so it looks like something got borked - and also that that something doesn't have good test coverage
18:32:13 Shrews well, i have a suspicion there might be other issues, but that seems to be the simplest at this point
18:32:52 Shrews we have a lot of Conflict exceptions on uploading that i don't ever recall seeing
18:33:32 Shrews across multiple providers
18:33:55 Shrews and some leaked images, so maybe some sort of relation there that I'm attempting to figure out

Earlier   Later