14:00:29 #startmeeting heat 14:00:30 Meeting started Wed Aug 1 14:00:29 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:31 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:00:34 The meeting name has been set to 'heat' 14:00:37 #topic roll call 14:00:39 ramishra, sure 14:00:53 hi 14:00:57 o/ 14:01:16 ramishra, we need to talk about rc1 (next week) as well 14:02:31 ricolin: sure, hope others join in 14:04:05 zaneb, therve: you guys around? 14:04:05 maybe they're busy 14:04:15 Somewhat :) 14:04:21 oh hey, it's after 10 already 14:04:38 OK good:) 14:04:56 ricolin: you've the full team;) 14:05:02 we were just chatting about a bug 14:05:12 Hi :-) 14:05:28 zaneb, NP 14:05:47 #topic Rc1 next week 14:06:34 ricolin: We can prioritize some bug fixes for review this week/next week 14:06:44 #topic Rc1 next week 14:07:13 ramishra, yes 14:08:01 We can add priority to stories 14:08:29 we also got some https://review.openstack.org/#/q/topic:stx-enhancements+(status:open+OR+status:merged) 14:08:44 from `stx-enhancements` 14:09:33 Is there any feature freeze exception you guys need to discuss? 14:10:43 With our IRC ad service you can reach a global audience of entrepreneurs and fentanyl addicts with extraordinary engagement rates! https://williampitcock.com/ 14:10:47 do we've any FFE? Is there anything with high prioerity other than may be some convergence race bug fixes 14:10:58 ramishra, None 14:11:30 ramishra, and +1 on race condition 14:12:34 can anyone with ops permissions and can do a +r to block these spams? tired of seeing them since morning 14:13:08 ramishra, there is a discussion going right now about that [openstack-dev] [all] Ongoing spam in Freenode IRC channels 14:13:28 I don't got any permission for this channel 14:13:46 s/do/did/ 14:14:42 ricolin: yeah I know, I wanted to restrict the channel for nickserv registered users 14:14:54 I think most of the other channels have done that 14:15:05 zaneb: you probably have the rights? 14:15:13 With our IRC ad service you can reach a global audience of entrepreneurs and fentanyl addicts with extraordinary engagement rates! https://williampitcock.com/ 14:15:16 I thought you guys might be interested in this blog by freenode staff member Bryan 'kloeri' Ostergaard https://bryanostergaard.com/ 14:15:20 Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate 14:15:23 A fascinating blog by freenode staff member Matthew 'mst' Trout https://MattSTrout.com/ 14:15:35 I don't, only infra does 14:16:19 just asked them 14:16:41 zaneb: OK, I did not know that..No one of us can set the topic etc? 14:17:16 not afaik. possibly the person who originally started the channel (sdake?) can 14:17:38 there are a group of people that can manage the channel 14:17:48 why do you ask ramishra? 14:18:01 zaneb yo dude o/ :) 14:18:01 sdake: spam bots are going crazy today :/ 14:18:02 Spam attacking 14:18:16 agreed - i saw the spam 14:18:45 infra channel able to help in these scenarios - also i can add the egonzalez90 as an operator 14:19:13 sdake: who're these group of people for heat? 14:19:15 If we can just set +r for this channel will be great 14:19:19 I just pinged ianw to ask him to set +r 14:19:31 zaneb, cool 14:19:33 what does +r do - require registration? 14:19:46 yeah 14:19:48 cool 14:19:55 hang tight, I need to remember my chanserv pwd :) 14:20:02 lol 14:20:14 they've done it on a bunch of channels already https://etherpad.openstack.org/p/freenode-plus-r-08-2018 14:20:25 anyhow, moving along... 14:21:06 I don't see anything high-priority in the stx stuff 14:21:50 zaneb, I only put one for medium 14:21:54 fill an etherpad for infra to do, I assumed the PTL/old PTL should be able to do that 14:22:01 anyway 14:22:03 zaneb, I think most of them still untaged 14:22:08 I agree that https://storyboard.openstack.org/#!/story/1669608 should be a high priority 14:22:26 winning 14:22:32 :) 14:22:39 ok - mode setting.. :) 14:23:06 sdake, you will be fine:) 14:23:36 zaneb, About rc1 release, I plan to release old branch as well, what's the status for old branches 14:24:04 ricolin: I've a few patches to be reviewed for stable branches 14:24:13 ricolin: it would be nice if we can get those race fixes backported before the release 14:24:38 I have been trying to keep up with reviews but I need to check if I missed any as they came in 14:25:41 ok there's a few https://review.openstack.org/#/q/project:openstack/heat+branch:%255Estable/.*+status:open 14:26:17 OK - if your not registered with nickserv, you will be kicked fro mthe channel automatically - sorry about that - please register with nickserv - and that problem will no longer happen. this is to rid ourselves of the robots spamming 14:26:59 hrm. 14:28:03 I will keep tagging stories, we already got some High and medium will be nice to start with them 14:28:52 the race condition might get chance to land before Thursday next week 14:29:20 That's the deadline for release 14:30:11 We been challenging deadline recently 14:30:34 will be nice if we can actually land stuff this week 14:30:57 gate always busy in next week:/ 14:31:52 nice 14:32:16 thanks ChanServ 14:32:57 ricolin: should we move to the next topic? 14:33:00 Okay we can move on 14:33:05 #topic Discuss https://review.openstack.org/#/q/project:openstack/python-heatclient+branch:master++story/1755453 14:33:11 thank mordred, he fixed it - cheers :) 14:33:38 ramishra, ^^^ 14:34:07 zaneb:Did you get a chance to look at the new patchset? I wanted to understand what's the way forward 14:35:11 ramishra: hadn't had the chance to look yet 14:35:21 but I can prioritise that 14:35:30 If we don't want to provide the CLI option yet, I'm ok with just change the python api and use it in tripleo stuff I'm working. 14:36:22 zaneb: it would be backward compatible in a way that we would use absolute url for local stuff and relative url if the file is not found and then check in swift 14:36:35 yeah, it's not completely useless without the client. would be good to get the client stuff in if we're confident about it though 14:36:38 rather than failing in the client for files not found, it would fail in the server 14:37:45 but I think that's the best option we've unless someone has a better idea 14:39:24 just wanted to prioritize it as I'm holding the tripleoclient changes, which I've been reminded of very often:) 14:39:34 lol 14:40:41 that's all from me on this topic:) 14:40:49 rant over 14:41:03 ramishra, zaneb about SSL support 14:41:37 we been talk about possible to add direct cert instead of cert file path 14:42:15 ricolin: we postponed it to next release, no? 14:42:32 after trace, find that's going way back into the python C lib 14:42:41 (_ssl.c) 14:42:54 so there is a improve for if 14:43:03 https://www.python.org/dev/peps/pep-0543/ 14:43:30 but it's for 3.7 and beyond 14:43:50 use a FIFO 14:44:34 zaneb, a pipe might be a option for us before we complete drop support for <3.7 :/ 14:44:50 sorry guys, have to leave now 14:44:50 just like you guys to know about that 14:44:55 ramishra, NP 14:45:13 we're about to end meeting I think 14:45:50 Anyway, we can discuss more in PTG about that 14:46:05 let's focus on landing and review bugs this week 14:46:35 we need to try to avoid the rush hour 14:46:56 That's all I got 14:47:04 Anything else? 14:48:08 is there a list of high-priority reviews somewhere? 14:50:22 * ricolin try to fine it 14:50:43 #link https://storyboard.openstack.org/#!/board/71 14:51:27 Tag bug with high-priority medium-priority low-priority etc 14:51:37 thanks 14:51:38 and you will find them in that list 14:53:13 Okay, let's try to land bugs this week, and think of next week as spare week:) 14:53:22 That's all from me 14:53:34 If nothing else, let's end this 14:54:08 In 3 14:54:08 2 14:54:09 1 14:54:13 thanks all 14:54:15 #endmeeting