14:00:28 #startmeeting heat 14:00:29 Meeting started Wed Mar 28 14:00:28 2018 UTC and is due to finish in 60 minutes. The chair is ricolin. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:00:30 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:00:32 The meeting name has been set to 'heat' 14:00:34 #topic roll call 14:01:20 hi 14:01:24 o/ 14:01:24 hi o/ 14:01:28 o/ 14:01:48 o/ 14:02:08 kiennt26, we got the rolling upgrade tag now 14:02:29 ricolin: yeah, hurray! 14:02:31 cheers 14:02:47 #topic adding items to agenda 14:02:49 o/ 14:02:53 #link https://wiki.openstack.org/wiki/Meetings/HeatAgenda#Agenda_.282018-03-28_1400_UTC.29 14:03:01 strigazi, hi 14:04:14 #topic trustor user gone issue 14:04:17 strigazi, ^^^ 14:04:21 hi all 14:04:34 here is the bug 14:04:36 #link https://bugs.launchpad.net/heat/+bug/1752347 14:04:37 Launchpad bug 1752347 in OpenStack Heat "trustor user should be updated on stack update" [Medium,In progress] - Assigned to Rico Lin (rico-lin) 14:05:01 ricolin: I would like some help to start working on it 14:05:14 not sure where I can start 14:05:15 i would like to ask something that related to heat dashboard 14:05:29 is it the right place and right time? 14:05:45 ruven, we're in meeting now maybe you can add it to agenda and we go to it later? 14:05:58 #link https://wiki.openstack.org/wiki/Meetings/HeatAgenda 14:06:09 ricolin: if you take it, I can help in testing 14:06:46 strigazi, so I try to put a patch for that 14:06:47 #link https://review.openstack.org/#/c/557337/ 14:07:50 it getting complicate when it works with reauthentication_auth_method 14:08:32 ricolin: I'll have a look. It is not in working state now, right? 14:08:53 for cases without reauthentication_auth_method it works 14:09:06 current one not work with reauthentication_auth_method 14:09:19 when reauthentication_auth_method is used? 14:10:38 it's used when we add that flag to config, it will allow load credential directly from DB 14:11:29 strigazi: that's an option to use trusts for long running tasks where the keystone token is expected to expire 14:12:23 ramishra: eg when using the heat agent? 14:12:48 ramishra: and want to update a stack after let's say a week or two? 14:13:35 strigazi: no, for when it takes like 5 hours to deploy a stack 14:13:57 #link https://docs.openstack.org/heat/pike/admin/auth-model.html#authorization-model-configuration 14:14:00 ^^^ 14:14:01 strigazi, 14:14:53 strigazi: anything where heat/other services need to re-authenticate with keystone, nothing to do with agents 14:15:53 the issue I'm seeing is when reauthenticate is on, we use stored context, but it's not authorize to use keystone client when we try to use keystone to operate trust 14:16:12 ricolin: I've not looked at the patch yet, but not sure why it should be an issue though to geneate a new trust_id for update 14:16:37 trust can't create trust 14:16:57 or I'm missing something 14:17:03 ricolin: we should use the new user's credentials to create a new trust and reset it 14:17:03 that's true 14:17:24 but we don't do that for reauthentication now, so I don't see the difference 14:18:04 the truster changes and the trustee remains the same 14:18:12 ramishra, yeah, so we have to figure out a proper way to use two different context(one that stored and the one that provided by user) 14:19:29 anyway, I suppose we can further discuss that in the review or the bug 14:20:16 ramishra, sure, anyway I just start working on that today, so needs more though about the design 14:20:18 thanks guys, me and slunkad will test it through magnum 14:20:45 strigazi, so I assume magnum don't use reauthentication_auth_method right? 14:21:05 ricolin: no 14:21:06 s/don't/didn't/ 14:22:04 btw I change that bug to medium because it seems affect to user 14:22:22 ricolin: wait, is it on by default? 14:22:33 strigazi, off 14:22:53 ok 14:22:57 disable by default 14:24:39 if no more specific topic we can move to open discussion 14:25:30 #topic Open discussion 14:25:54 Anything needs to raise?:) 14:27:21 my Etcd patch is nearly done(still need time to add unit tests) 14:27:35 will push it soon 14:28:20 Since we still needs more work to adopt tooz, my current patch use etcd3gw directly 14:28:40 ricolin: what is it for? is there a bug/bp for it? 14:29:05 strigazi, oh for heat stack lock 14:29:31 https://etherpad.openstack.org/p/heat-rocky-ptg-syncpoint-dlm-backend 14:29:37 #link https://etherpad.openstack.org/p/heat-rocky-ptg-syncpoint-dlm-backend 14:29:49 ricolin: thx 14:29:53 ricolin: for Blazar support patch, now asking Blazar team to review again. After getting their +1, will ask Heat cores to review it again. 14:30:13 https://review.openstack.org/#/c/534576/ 14:30:16 kazsh, cool! 14:30:22 #link https://review.openstack.org/#/c/534576/ 14:30:34 yep :) that's one 14:31:16 Anyway that's all from me, rest stuff still WIP 14:31:32 Any others?:) 14:32:39 oops, just drop the line for a while 14:33:10 so let's end this?:) 14:33:19 :) 14:33:51 #endmeeting