17:00:33 #startmeeting murano 17:00:34 Meeting started Tue Nov 22 17:00:33 2016 UTC and is due to finish in 60 minutes. The chair is kzaitsev_mb. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:00:35 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 17:00:37 The meeting name has been set to 'murano' 17:01:01 #topic rollcall 17:03:08 o/ 17:05:33 hi there ) 17:06:58 hi 17:08:48 #topic Core Reviewers update 17:09:41 so I'm adding Felipe Monteiro (not sure if I know his irc handle) and removing Filip Blaha & Ekaterina Chernova as per my emails =) 17:09:58 if you guys have any 2d thoughts — now's the time to voice them ) 17:10:16 +1 for for addition and exclusion 17:11:41 aaaaaand 17:11:42 done 17:12:39 going to send the letters in a few minutes ) 17:13:10 I still haven't implemented the alternating meeting time T_T 17:13:26 #action kzaitsev_mb implement alternating meetings 17:13:35 should be a pretty straightforward commit 17:13:44 just need to find some time to send it for review 17:13:50 k. 17:13:55 #topic Open Discussion 17:14:11 ativelkov: StanLagun: do you guys have any important announcements =) 17:14:17 or maybe paches that need attention? 17:14:54 nothing important from my side 17:14:58 freerunner: have you had a chance to look at murano-agent gate failures? Seems like we're still getting those 17:15:24 not much from my side, just a notice that we have to revert a patch https://review.openstack.org/#/c/385519/ by zhurong 17:15:52 And to do the thing properly we have to remove the depencency 17:16:02 of murano engine on keystone_authtoken cfg section 17:16:16 I've filed a bug on this particular issue 17:16:41 https://bugs.launchpad.net/murano/+bug/1643583 17:16:41 Launchpad bug 1643583 in Murano "Murano Engine uses keystone_authtoken configuration section" [Undecided,New] - Assigned to Alexander Tivelkov (ativelkov) 17:17:01 we may consider marking it as a low hanging fruit since it is quite a straitforward thing to do 17:17:21 (so probably I need to unassign it from myself) 17:18:41 ativelkov: yep, please unassign, mark the thing as lhf and explain how to fix it (if there is any explanation needed) 17:18:53 ativelkov: StanLagun: do you guys thing we need to make a release? 17:18:57 I mean 17:19:13 we've switched to a different release model and we're at O-1 time. 17:19:28 so we might want to request a release here 17:19:43 would probably be 3.1.0 for murano/murano-dashboard 17:20:09 We probably need to do a realease of yaql, but that's a different story 17:20:17 since it is not under the big tent 17:21:14 ativelkov: yeah. well big tent or not — I would advertise to use releases repo for releasing things 17:21:36 kzaitsev_mb: can we use releases for non big-tenty things? 17:21:52 theirs infra is really really neat and makes everything pretty straightforward 17:22:24 ativelkov: let's ask release team on next release team meeting? =) 17:22:30 they're on fridays ) 17:22:51 Thanks, I'll try 17:23:00 ativelkov: well, after all say, reno is not big tent 17:23:14 but it's uses releases repo, I believe 17:23:42 Moreover, I'd suggest to move yaql to big tent at some point: it is used by 3 different openstack projects, is mature enough etc, so I think it could be benefitial for all 17:23:46 ativelkov: https://github.com/openstack/releases/blob/master/deliverables/_independent/reno.yaml 17:23:49 like this 17:24:08 they have this independent folder 17:24:09 ativelkov: 4 17:24:10 =) 17:24:21 oh, forgot about mistral ) 17:24:30 then yes, 4 ) 17:24:37 #link https://releases.openstack.org/independent.html 17:24:43 thanks 17:25:15 the upside would be that yaql would be available through ^^^ 17:26:14 sounds like an overall good idea to me =) 17:26:54 StanLagun: any opinion on this? 17:27:35 I have a mixed feeling about it 17:28:40 StanLagun: why so? =) 17:28:42 yaql is not related to OpenStack even though it is used in OpenStack. Making yaql a big tent OpenStack project doesn't seem to be logical 17:29:02 StanLagun: nobody is talking about making yaql big tent 17:29:25 * ativelkov does 17:29:30 oh 17:30:51 nah, I'm not sure that it is even possible to big tent yaql %) 17:30:59 I was talking about re-using infra 17:31:13 since we're using openstack infra for yaql anyway 17:34:03 OK, let's do the release management 17:34:15 we may come back to big tent idea in the next cycle :) 17:34:46 I know very little about release procedure so I have no objections as long as it just a technical decision and doesn't affect project positioning and who control it 17:39:22 OK, so let's do it for the next yaql release 17:40:18 #agreed to use openstack/releases for next yaql release 17:40:58 cool 17:41:23 if there is nothing more to discuss — I'm going to end the meeting in 5-10 mins ) 17:47:41 ok, thanks for joining =) 17:47:48 #endmeeting