05:30:13 #startmeeting senlin 05:30:14 Meeting started Fri Nov 30 05:30:13 2018 UTC and is due to finish in 60 minutes. The chair is dtruong. Information about MeetBot at http://wiki.debian.org/MeetBot. 05:30:15 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 05:30:17 The meeting name has been set to 'senlin' 05:30:29 all right, time for the senlin meeting 05:30:44 anybody here to join? 05:35:09 ok, let's get started 05:35:22 #topic berlin summit recap 05:36:01 At the Berlin Summit, I held the Senlin project update. 05:36:23 The video was recorded but it has not yet been posted. 05:37:05 There weren't any questions but I did get some feedback from a Senlin user after the session 05:37:54 Their feedback was that they were doing POCs with Senlin and looking to use it. 05:38:18 He also said he liked the proposed additions to the health policy for URL based checks. 05:38:36 Hopefully we can get some bug reports/feature requests from them. 05:39:18 Yes. I told him to contact us in the IRC channel if he has any questions. 05:39:50 The other relevant session at the Berlin Summit was Autoscaling forum. 05:40:04 It was a joined discussion with the Heat team. 05:41:00 Also present was the Magnum PTL to give their perspective. 05:42:01 Due to the short time frame of the session, we were not able to have any detailed discussions. 05:43:02 The main outcome was that we all agreed that Heat and Senlin should collaborate more going forward. 05:43:28 So it was decided to create a new Autoscaling SIG. 05:44:55 Other feedback I got from an operator who is using Heat autoscaling was that Senlin was not being considered by them at this point because it is not vulnerability managed. 05:47:25 This is referrring to the Openstack Vulnerability Management program 05:47:29 #link https://governance.openstack.org/tc/reference/tags/vulnerability_managed.html 05:48:22 Since this seems to be requirement for some operators, we should consider getting Senlin under that process as well. 05:48:42 Ok, moving on. 05:48:48 #topic Autoscaling SIG 05:49:14 As mentioned before, there is a proposal in the mailing list to create the new Autoscaling SIG 05:49:34 #link http://lists.openstack.org/pipermail/openstack-discuss/2018-November/000284.html 05:49:54 If you have any input, please reply to the email with your thoughts. 05:50:43 #topic blueprints 05:51:05 No changes on the status of the existing blueprints since the last meeting 05:51:22 But we have a new blueprint submitted for action update 05:51:38 #link https://blueprints.launchpad.net/senlin/+spec/action-update 05:51:56 any update on the status of that blueprint, judecross? 05:52:13 Very close, have a patch set up right now that needs review. 05:52:28 and testing. 05:52:39 I will be updating the openstack sdk 05:52:55 and the senlin client 05:53:00 to account for this change. 05:53:15 Sounds good. Thanks. 05:53:20 #link https://review.openstack.org/#/c/618907/ 05:53:41 Please help review the his patch set ^ 05:54:00 #topic meeting time and frequency 05:54:36 We discussed a few weeks ago about changing the meeting time to a different time on alternating weeks 05:54:55 At the Berlin summit, I met a couple users based in the US that were interested in Senlin. 05:55:48 Plus the fact that 3 of our core reviewers are located in the US, I would like to propose holding every other meeting during US daytime. 05:56:02 I was thinking Thursday at 11am PST 05:56:12 Judecross: any thoughts on that> 05:56:43 I am 100% for that 05:57:03 11:00am PST sounds perfect 05:57:11 Ok, I'll send out an email to the mailing list to propose that. 05:58:15 Last topic is open reviews 05:58:19 #Reviews 05:58:45 We have judecross's patch set that needs review: https://review.openstack.org/#/c/618907/ 05:59:16 I also have a patch set that has been reviewed but needs workflow: https://review.openstack.org/#/c/614885/ 05:59:48 Any help to look at those would be great. 06:00:00 can we schedule it at, for example, 17:00pm pst? 06:00:26 it would be 9:00 am in Beijing 06:00:31 That's fine for me too. 06:00:46 I am ok with that time as well 06:00:49 11:00 am is 03:00 am in beijing 06:01:22 My proposal is to keep the current time slot for every other week so that people in Asia can join. 06:01:42 I see 06:02:54 The only concern with 17:00pm PST is that if anybody from US east coast or from Europe wants to join, it would be late for them. 06:04:03 us east would be night time, bad time slot for europe, ... 06:04:14 anyway, just a suggestion 06:05:15 11:00 am pst is it then 06:05:23 ok, sounds good. 06:05:35 I'll send it out to mailing list to get more feedback from otheres 06:06:07 and if the majority prefers a different time slot for alternating meeting time, we can definitely change it 06:06:38 #topic open discussion 06:06:50 that's all i have for today. 06:07:00 anybody want to discuss anything? 06:07:15 thanks for the update, dtruong 06:09:18 No problem. If you have any feedback on the Autoscaling SIG, please reply to the email thread, qiming. 06:09:45 sure 06:10:59 I would like to see the new SIG document the current status of autoscaling and then describe the different use cases before any decision is made on a common autoscaling solution. 06:11:55 me too 06:13:52 Sounds good then. 06:14:01 Judecross: do you have anything to add? 06:14:17 Nope 06:14:27 ok, let's end the meeting then 06:14:34 thanks for attending everyone 06:14:43 #endmeeing 06:14:52 sorry about being late :) 06:15:03 np 06:15:13 #endmeeting