| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-sdks - 2019-04-18 | |||
| 16:07:31 | edleafe | Do you have any idea? | |
| 16:07:58 | elmiko | edleafe: i agree about Akihiro's comment, thanks for taking that on | |
| 16:08:05 | dtantsur | edleafe: I don't see a dup, let's approve it.. | |
| 16:08:46 | edleafe | I just posted a reply to the dupe patch a few minutes ago. There's no rush, so if there is no good answer by next week, let's approve it then | |
| 16:09:49 | elmiko | edleafe: agreed | |
| 16:10:57 | edleafe | That's all I had on my plate to discuss | |
| 16:11:26 | elmiko | edleafe ++ | |
| 16:17:26 | edleafe | https://review.openstack.org/#/c/651222 has been frozen | |
| 16:17:41 | elmiko | thanks edleafe | |
| 16:19:01 | dtantsur | w00t! | |
| 16:19:09 | openstackgerrit | Ed Leafe proposed openstack/api-sig master: Added Placement to the liaisons file https://review.openstack.org/645223 | |
| 16:19:14 | edleafe | dtantsur: elmiko: ^^ Fixed the ordering | |
| 16:19:23 | edleafe | Either of you want to fast-approve that? | |
| 16:19:38 | elmiko | edleafe: looking now | |
| 16:19:50 | edleafe | Nobody will ask such a dumb question. We already know the answer is yes | |
| 16:20:26 | efried | Does the API SIG deal with things like adoption of OpenStack SDK? | |
| 16:20:49 | dtantsur | efried: it borders with our responsibilities, at least | |
| 16:20:53 | elmiko | ++ | |
| 16:20:53 | efried | not to interrupt; feel free to come back to me when you reach an appropriate spot in the agenda | |
| 16:21:04 | edleafe | efried: not specifically, but we do say things like "yes, that's a good thing to do" | |
| 16:21:07 | elmiko | no real agenda, this is just open office hours | |
| 16:21:25 | elmiko | dtantsur edleafe , +wf on the liaison file | |
| 16:21:39 | edleafe | elmiko: kewl | |
| 16:21:42 | dtantsur | efried: I think it's a good topic for right now, but what exactly do you have in mind? | |
| 16:21:57 | efried | Okay, so this is mostly FYI: I'm kind of involved in / leading a charge to make nova use the sdk. | |
| 16:22:07 | dtantsur | if you need some to do some work, we have mordred to appoint | |
| 16:22:07 | elmiko | nice | |
| 16:22:13 | elmiko | LOL | |
| 16:22:22 | efried | https://blueprints.launchpad.net/nova/+spec/openstacksdk-in-nova | |
| 16:22:26 | dtantsur | because we don't do work here, it's not the goal of API SIG | |
| 16:22:27 | efried | mordred has already done some work. | |
| 16:22:43 | dtantsur | oh? | |
| 16:22:45 | elmiko | dtantsur ++ | |
| 16:22:47 | edleafe | We pride ourselves on convincing others to do the work | |
| 16:22:56 | elmiko | XD | |
| 16:23:05 | efried | there's this: https://review.openstack.org/643601 which needs to be cleaned up and have UT added | |
| 16:23:14 | efried | but has been integration-tested and works. | |
| 16:23:28 | dtantsur | efried: I'd really like to get to switching ironic-inspector to use SDK for talking to ironic and swift | |
| 16:23:33 | efried | tl;dr: lets you set up Connection with oslo.config ksa opts instead of clouds.yaml | |
| 16:23:34 | dtantsur | I mean, get to it in Train | |
| 16:23:53 | dtantsur | efried: I'm very much in favor of that. very. | |
| 16:23:55 | efried | ...so we can make the transition transparent to operators initially. | |
| 16:24:24 | efried | and then there's this: https://review.openstack.org/#/c/643664/ which introduces the plumbing for sdk in nova | |
| 16:24:42 | efried | and the patch on top of it https://review.openstack.org/#/c/642899/ which starts the process of swapping out calls into ironicclient. | |
| 16:24:56 | efried | idea being to stack several of those ^ up until we can rip out ironicclient entirely. | |
| 16:25:09 | efried | (from nova) | |
| 16:25:38 | efried | I've got a new guy helping out with the nova things | |
| 16:25:45 | efried | but could use some help on the sdk side | |
| 16:25:58 | efried | there's the patch noted above, already started, could use closure | |
| 16:26:00 | mordred | yeah. I'll definitely be digging in to help | |
| 16:26:14 | mordred | and I need to finish that patch as soon as I can finish up all the meetings I've been stuck in this week | |
| 16:26:15 | efried | and then there's a need for a fixture to facilitate testing on the nova side | |
| 16:26:30 | efried | mordred: Totally understood, I was actually fishing for other volunteers to help :) | |
| 16:26:57 | dtantsur | efried: note that future openstacksdk 0.26 will add patch_node for ironic, which will substantially simplify transition (no need to get rid of patcher right away) | |
| 16:26:58 | efried | here's a story for the fixtures: https://storyboard.openstack.org/#!/story/2005475 | |
| 16:27:12 | efried | dtantsur: ack, good to know. | |
| 16:27:36 | efried | So | |
| 16:27:49 | efried | besides soliciting help if possible for the sdk items noted above | |
| 16:28:03 | efried | it would be nice if the API SIG (or whoever) could lend support to this idea in general. | |
| 16:28:16 | efried | because nova cores are old and crusty and afraid of change | |
| 16:28:23 | efried | and sdk is shiny and new and fancy | |
| 16:28:39 | efried | Any questions, comments, etc? | |
| 16:29:14 | dtantsur | efried: what kind of support would you imagine? | |
| 16:29:38 | dtantsur | esp. around making old nova cores a bit less crusty? | |
| 16:29:47 | efried | I dunno. Looking for opportunities to tell key people that this is a good idea? | |
| 16:30:00 | edleafe | efried: Sure, I'm sure that my opinion will sway the Nova cores. It *always* does! | |
| 16:30:06 | efried | heh | |
| 16:30:13 | efried | well actually | |
| 16:30:16 | dtantsur | we should have had a Forum session | |
| 16:30:27 | mordred | yeah | |
| 16:30:37 | efried | it sort of dovetails with the (ill-fated) community goal for osc. | |
| 16:30:40 | mordred | well - tim bell has consistently raised his hands in support of this | |
| 16:30:46 | mordred | iirc | |
| 16:30:53 | mordred | so - I think we just say "tim bell says it's a good idea" | |
| 16:31:00 | dtantsur | ++ should work | |
| 16:31:02 | mordred | because nobody wants to argue with tim bell | |
| 16:31:21 | efried | Using sdk over python-*client or even raw ksa in $project could be a community goal. | |
| 16:31:23 | mordred | I mean - *I* don't want to argue with tim and I like arguing with anybody | |
| 16:31:38 | dtantsur | heh | |
| 16:31:42 | elmiko | efried: fwiw, i think the api sig could definitely help with moving the discussions forward and provide solid support in that respect. as the others have noted, i'm not sure how much we could lend in terms of coding or contributions to nova. | |
| 16:31:43 | mordred | efried: yeah - but I'd honestly still focus it on using sdk - even if people just want to use raw ksa | |
| 16:31:57 | openstackgerrit | Ed Leafe proposed openstack/api-sig master: Add document describing consuming version discovery https://review.openstack.org/459405 | |
| 16:31:58 | mordred | largely because it'll help us align on operator-centric config | |
| 16:32:08 | edleafe | elmiko: dtantsur: ^^ rebase the version discovery doc | |
| 16:32:15 | dtantsur | many thanks edleafe! | |
| 16:32:23 | mordred | efried: and if people don't want to use the object layer of sdk in their code - that's fine ... they can still just do things like conn.compute.get('/servers') | |
| 16:32:40 | efried | mordred: ack, that's been my thinking. I alluded to that in the nova blueprint | |
| 16:32:47 | mordred | ++ | |
| 16:32:52 | elmiko | edleafe: ack, thanks | |
| 16:32:56 | efried | e.g. I don't think placement has any object model code in sdk, right? | |
| 16:33:04 | mordred | nope, not to my knowledge | |
| 16:33:17 | mordred | so I think nova would just be using conn.placement.get('/things') | |
| 16:33:28 | dtantsur | I think the biggest reason to NOT use ironicclient is that we largely screwed microversioning there :) | |
| 16:33:30 | efried | but we ought to be able to swap out the ksa adapter with Connection.placement and not have to do much else except some fixture stuff. | |
| 16:33:31 | efried | yes. | |
| 16:33:38 | mordred | efried: exactly | |
| 16:34:03 | dtantsur | and this is also my argument against recommending people to use raw ksa: microversioning requires careful handling.. | |
| 16:34:04 | efried | during transition, operators can continue using ksa oslo.config opts, but can cut over to clouds.yaml any time they want | |
| 16:34:49 | efried | okay, dtantsur and mordred these arguments are going to be helpful. | |
| 16:35:10 | efried | Because we "just" (queens) got done converting (almost) everything to ksa. | |