15:06:33 #startmeeting openstack-helm 15:06:35 Meeting started Tue Sep 25 15:06:33 2018 UTC and is due to finish in 60 minutes. The chair is portdirect. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:06:36 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:06:36 o/ 15:06:38 The meeting name has been set to 'openstack_helm' 15:07:09 so this week is pretty light on the agenda: https://etherpad.openstack.org/p/openstack-helm-meeting-2018-09-25 15:07:19 feel free to add to it :) 15:07:32 #topic rollcall 15:07:35 o/ 15:07:47 o/ 15:07:55 o/ 15:08:09 o/ 15:09:05 #topic Docs Repo 15:09:30 so I'm a bit behind on this, but I'll be getting a ps up to infra today/tomorrow to kick of the docs repo 15:09:31 o/ 15:09:48 great news 15:09:51 and then the work can begin :) 15:10:01 nice 15:10:20 jay is not here today but I'm hoping to get another name for the korean editors 15:10:39 portdirect: did you ask ianychoi ? 15:10:42 and both mattmceuen and srwilkers 's expert eyes will initially take care of the engish side 15:10:57 he would be great help with the knowledge of korean + zanata 15:10:57 evrardjp: that is an EXCELLENT idea 15:11:06 I'll hound him straight after this 15:11:32 probably at the end of your day too, as he might be sleeping during those hours 15:11:36 #action portdirect to pester ianychoi about becoming a documentation editor 15:11:38 ++ 15:12:12 ok - so i think the path is clear here? any further comments? 15:12:18 sorry I didn't want to enroll him without asking him, I just mean he could be a great person/asset in this case 15:12:44 evrardjp: all good, I'm just being opportunistic ;) 15:14:16 #topic Gates 15:14:46 so we have made a tiny bit of progress on the gates 15:15:13 but i wonder if this week we may want to grab some of the low hanging fruit 15:15:29 and without changing the gate too much 15:15:43 get some of the horrible ansible rats nest un check 15:16:02 so I am sorry on that part 15:16:09 i made a quick wip here: https://review.openstack.org/#/c/602682/ 15:16:10 I said I wanted to work on that this week 15:16:27 evrardjp: no worries dude 15:16:32 I realise with my upcoming holidays and my current work I couldn't help (yet!) 15:16:52 now your just being mean, what are these holidays of which you speak? 15:17:24 anything else to add on this? 15:17:27 If you're visiting saint louis for any reason we have an office + desk you can visit >:-) 15:17:42 :O 15:17:47 haha 15:18:07 evrardjp: they told me the same thing. Its a trap! 15:18:08 I will review this patch and suggest things, but this is indeed a good start 15:18:23 portdirect: duely noted 15:18:25 portdirect: i mean, i wasnt going to be the one to say it 15:18:42 ok - move on? 15:18:46 yup 15:18:58 oh 15:19:01 #topic Mariadb, the saga continues 15:19:04 next time don't hesitate to add me to reviews 15:19:17 for these kind of things -- and ping. I don't mind :) 15:19:28 will do 15:19:41 so I've finally got round to having a look at the mariadb chart 15:19:59 and ended up pretty much completely redoing it: https://review.openstack.org/#/c/604556/ 15:20:14 was nice to write my 1st python again in two years 15:20:32 it uses a configmap to store state of the cluster 15:20:59 its pretty nifty - no complaints thus far 15:21:09 https://www.irccloud.com/pastebin/e9lXRUCY/ 15:21:46 and ive been hammering it with mysqlslap 15:21:52 that's awesome 15:21:59 theres a few more things i need to account for 15:22:14 * setup vars for timers and set sane nyquest ratios between them 15:22:14 * get xtrabackup back up 15:22:14 * deal with potential for split brains (in follow up ps) 15:22:14 * deal with chart upgrade senario 15:22:14 * deal with chart removal and redeploy senario 15:22:14 * add sigterm handler 15:22:28 but i think its ready for some gentle test rides and reviews 15:23:09 great work 15:23:11 dealing with the potential for split brains will require some work on the proxy infront of the cluster 15:23:17 so i think that will come as a follow up 15:25:03 i know there is a wip on it, but my python is so rusty - feel free to provide any course correction 15:25:21 and with that 15:25:37 #topic open discussion 15:27:08 I have a topic for open discussion 15:27:21 the floor is yours 15:28:21 should we care about reducing the packages installed on host? If I am the only one to care, I can deal with it differently. 15:29:05 evrardjp: we certainly should 15:29:09 ok 15:29:10 for doing the kubeadm-based install / gates, or something else evrardjp? 15:29:39 I am assuming everywhere we do things on hosts. 15:29:40 ^^ by packages i assume you mean python ones for kubeadm playbooks? 15:29:56 (and the support for them) 15:29:59 I should not have said packages as this is confusing 15:30:10 let me rephrase 15:30:36 In gates we have to do what we have to do -- i.e. setting k8s up, and maybe set storage up with ceph. 15:31:04 I assume this can be done as "gating" functions, and convenience for users 15:31:21 so shouldn't the rest be contained, or limited? 15:31:46 My point would be reducing the writes to /tmp, reducing the pip packages installed, and others I have yet to see 15:32:09 ah gotcha 15:32:10 if we say it's a guideline of something we must avoid in the future, we can regularily clean things up when something shows up 15:32:25 yeah I hope that improved docs will go a long way towards this 15:32:25 it has a positive impact on host maintenance and security 15:32:38 as our docs essentially only describe what we do in the gates atm 15:32:47 correct 15:32:58 and we have nothing that covers a 'production' deployment 15:33:25 I would never deploy OSH as we desribe today in a real senario 15:33:28 I think that's what gates should be testing :D 15:33:40 agreed - to a point 15:33:43 that is interesting and I'd like to discuss this in the channel 15:33:51 we need the gates to both cover basic functional testing 15:34:01 and richer ones that bring up realistic deployment 15:34:19 my point in this open discussion was to know the alignment on the "avoid installing things on host" 15:34:20 where "richer" = "bigger"? :) 15:34:48 mattmceuen: not always :) I;m thinking more using armada to decalre the deployment 15:34:48 portdirect: agreed there -- maybe I should have said testing. 15:34:55 and having things like tls in place 15:34:55 gotcha 15:35:22 what im getting out of this 15:35:23 but we are generally in agreement, so the technical details can go into each review 15:35:29 ++ 15:35:58 should we get an etherpad to jot down this, so by next meeting we can dicuss a path forward? 15:36:17 i think we are all aligned, just need to work out how to articulate it 15:36:58 yeah it doesn't matter it can be in the docs and we'll slowly move towards it, we can keep that in mind in reviews 15:37:21 wfm 15:37:49 thanks 15:38:01 any other topics? 15:38:13 srwilkers: you scare me when you are quite 15:38:19 >:) 15:38:46 ok to wrap up 15:39:16 thanks everyone, dont spend the next 21 mins to recklessly 15:39:17 #endmeeting