14:00:49 #startmeeting tripleo 14:00:50 Meeting started Tue Apr 9 14:00:49 2019 UTC and is due to finish in 60 minutes. The chair is jaosorior. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:00:51 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:00:53 The meeting name has been set to 'tripleo' 14:00:54 #topic agenda 14:00:56 o/ 14:00:59 o/ 14:01:02 * Review past action items 14:01:03 o/ 14:01:04 * One off agenda items 14:01:05 o/ 14:01:06 * Squad status 14:01:08 * Bugs & Blueprints 14:01:08 o/ 14:01:09 o/\o 14:01:10 * Projects releases or stable backports 14:01:12 * Specs 14:01:14 * open discussion 14:01:14 o/ 14:01:14 o/ 14:01:16 Anyone can use the #link, #action and #info commands, not just the moderatorǃ 14:01:18 Hey folks! who's around? 14:01:22 o/ 14:01:26 Ronelle Landy proposed openstack-infra/tripleo-ci master: WIP: Add rocky standalone job https://review.openstack.org/651247 14:01:30 0/ 14:01:33 o/ 14:01:34 o/ 14:03:22 #topic review past action items 14:03:26 None. 14:03:31 #topic one off agenda items 14:03:35 #link https://etherpad.openstack.org/p/tripleo-meeting-items 14:04:00 The first topic is from beagles : working towards making scenario010-standalone (octavia) voting 14:04:16 o/ 14:04:39 Alex Schultz proposed openstack/tripleo-common master: Modify roles to remove unused services https://review.openstack.org/642032 14:04:39 hi all, octavia has been around for a bit but we've not had voting CI jobs for it 14:05:08 +2 14:05:27 cause they aren't passing 14:05:47 o/ 14:05:47 let's get them green and we can switch them to voting 14:05:55 as such things tend to get broken and unnoticed 14:06:16 yeah. multinode probably needs to be voting as well because it is catching issues standalone is not 14:07:31 quesitons that come to mind, do we need both - and if so, might be more of a priority to get multinode voting stable and voting first 14:07:36 If multinode goes back to voting it might catch things standalone doesn't, but if history is a lesson, then I think the cost would be less reliable CI. 14:07:39 (catches more stuff) 14:08:01 (tripleo ci team should say though) 14:08:05 o/ 14:08:08 so the concern with adding a multinode is resources 14:08:12 fultonj: good point 14:08:17 we could just run the multinode against mistral projects 14:08:17 «o/ 14:08:30 we've worked really hard to eliminate multinode as much as possible 14:09:07 mwhahaha: I wonder if there would be advantages to be careful about what triggers what 14:10:06 maybe keep both? 14:10:14 and only run the multinode on mistral specific code 14:10:24 +1 14:10:44 this is one of those extra services that we can kinda cover upstream but the multinode should probably be tested downstream due to resource constraints 14:11:05 since octavia is an extra and not core service i'm not sure we should use the resources upstream for it 14:12:23 o/ 14:14:06 mwhahaha: +1 14:14:20 I've also been thinking about backports - would be good to get that up and voting as well but for that it would be multinode 14:14:33 mwhahaha: +1 14:14:40 but I'm getting ahead of myself 14:14:43 at least that was my experience with ceph once 14:14:50 lets get the jobs fixed up and have the conversation then 14:14:55 e.g. a downstream testing had to catch something multinode 14:15:06 +1 to standalone version going forward being voting 14:15:08 not ideal but resources are limited and downstream testing was sufficient 14:15:31 k 14:17:43 the next topic is from rfolco: stein branching: we're watching tripleo channel to make sure stein jobs will run successfully. 14:18:12 yep, the jobs should run as soon as we branch tripleo projects, ci bits are in place 14:18:15 did the blockers to branching get resolved, /me needs to look 14:18:27 EmilienM mentioned a few last week 14:19:02 when do we want to branch stein? this week? 14:19:08 maybe we could branch tripleoclient first 14:19:19 wait to see how CI works etc 14:19:33 and in few weeks we branch the rest 14:19:41 that's how we do usually 14:19:52 tripleoclient or tripleo-common? 14:20:01 well they need each other 14:20:03 client iirc 14:20:16 k lets get it started i guess 14:20:35 ra ra sisk boom bah 14:21:37 mwhahaha, +1 we definitely need tripleo-common otherwise we will not test all changes 14:21:45 please don't sing 14:21:55 I was cheerleading thank you very much 14:22:16 mwhahaha: you want me to propose the patch? 14:22:22 yes plz 14:22:32 #action EmilienM to branch tripleoclient stable/stein this week 14:23:19 EmilienM, I offer support for watching jobs and making sure they run well 14:24:19 #topic Squad status 14:24:24 ci 14:24:26 #link https://etherpad.openstack.org/p/tripleo-ci-squad-meeting 14:24:28 upgrade 14:24:30 #link https://etherpad.openstack.org/p/tripleo-upgrade-squad-status 14:24:32 containers 14:24:34 #link https://trello.com/b/S8TmOU0u/tripleo-podman 14:24:36 integration 14:24:38 #link https://etherpad.openstack.org/p/tripleo-integration-squad-status 14:24:40 cli 14:24:42 #link https://etherpad.openstack.org/p/tripleo-ui-cli-squad-status 14:24:44 validations 14:24:46 #link https://etherpad.openstack.org/p/tripleo-validations-squad-status 14:24:48 networking 14:24:50 #link https://etherpad.openstack.org/p/tripleo-networking-squad-status 14:24:52 edge 14:24:54 #link https://etherpad.openstack.org/p/tripleo-edge-squad-status 14:24:56 Any squad wanting to bring up their status, or a topic for the general public? 14:25:01 Validations: we still need a ton of reviews. 14:25:04 #link https://trello.com/c/k96ySxA0/18-review-migrating-validations-playbooks-to-their-own-ansible-role 14:25:08 please-please-please :) 14:25:46 please don't sing 14:25:58 mwhahaha: https://review.openstack.org/651253 14:26:10 weshay: bah, sun's shining here. 14:26:36 weshay: as long as I'm not "singing under the rain", "it's alright, it's ok" :D 14:27:07 EmilienM, we would also need to do branching for tripleo in RDO as well 14:27:19 thought we already branched rdo? 14:27:31 or did you folks just ask about it and not do it 14:27:53 mwhahaha, not branched yet, current status: https://review.rdoproject.org/etherpad/p/stein-release-preparation 14:27:55 L 111 14:28:12 if you can propose branching, builds will be automatic by bot 14:28:14 k 14:29:48 #topic bugs & blueprints 14:29:54 #link https://launchpad.net/tripleo/+milestone/stein-rc1 14:29:56 For Stein we currently have 2 (for stein-rc1) blueprints open in Launchpad. 14:29:58 Bugs: 221 (+9) stein-rc1, 288 (-1) train-1 in Launchpad. 104 (0) open Storyboard bugs. 14:30:00 #link https://storyboard.openstack.org/#!/project_group/76 14:30:55 #topic projects releases or stable backports 14:32:20 #topic specs 14:32:26 #link https://review.openstack.org/#/q/project:openstack/tripleo-specs+status:open 14:32:28 Any specs folks want to bring attention to? 14:32:37 yeah 14:32:49 we still need some reviews on https://review.openstack.org/645508 - note it's for Train already 14:33:14 but that one, the sooner we're OK with it, the sooner work can start. It will be long :) 14:34:05 ack 14:36:01 #topic open discussion 14:36:05 Anything else that folks want to bring up to the meeting? 14:36:44 I got a quick one, baha and I uploaded this rdo patch yesterday to move our ppc64le container build job to the zuul playbooks used by tripleo-ci. If anyone can take a look at the patch we'd really appreciate some feedback. https://review.rdoproject.org/r/#/c/20031/ 14:38:50 s/zuul playbooks/playbooks 14:41:29 Quique Llorente proposed openstack-infra/tripleo-ci master: Make scenario000 multinode upgrades job voting https://review.openstack.org/651258 14:43:12 #endmeeting