14:00:20 <jaosorior> #startmeeting tripleo
14:00:20 <openstack> Meeting started Tue Mar 26 14:00:20 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:21 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
14:00:23 <openstack> The meeting name has been set to 'tripleo'
14:00:25 <jaosorior> #topic agenda
14:00:33 <jaosorior> * Review past action items
14:00:35 <jaosorior> * One off agenda items
14:00:37 <jaosorior> * Squad status
14:00:39 <jaosorior> * Bugs & Blueprints
14:00:41 <jaosorior> * Projects releases or stable backports
14:00:43 <jaosorior> * Specs
14:00:45 <jaosorior> * open discussion
14:00:47 <jaosorior> Anyone can use the #link, #action and #info commands, not just the moderatorǃ
14:00:49 <jaosorior> Hey folks! who's around?
14:01:12 <dpeacock> o/
14:01:13 <dprince> hi
14:01:15 <rfolco> o/
14:01:17 <mwhahaha> hi2u
14:01:20 <ksambor> o/
14:01:20 <bogdando> o'
14:01:34 <pkopec> o/
14:01:39 <chandankumar> sshnaidm|rover: I think so, it should be there, let me pull the logs
14:01:43 <Tengu> \o/
14:01:53 <marios_|ruck> o/
14:02:15 <fultonj> o/
14:02:21 <mschuppert> o/
14:02:22 <mjturek> o/
14:02:24 <baha> o/
14:02:31 <chandankumar> \o//
14:02:49 <jfrancoa> o/
14:03:07 <fmount> o/
14:03:42 <rlandy> o/
14:03:56 <jaosorior> plenty of folks today
14:03:59 <jaosorior> #topic review past action items
14:04:05 <jaosorior> None.
14:04:10 <jaosorior> #topic one off agenda items
14:04:15 <jaosorior> #link https://etherpad.openstack.org/p/tripleo-meeting-items
14:04:29 <jaosorior> first topic: ( rfolco ): stein branching follow-up: CI team is creating stein jobs for promotion and upstream. Just checking if any updates from last week on branching tripleo projects.
14:04:57 <rfolco> just checking if any updates from last meeting. If any plans for branching stein this week.
14:04:59 <mwhahaha> do we have stein containers yet? it was blocking puppet openstack stuff
14:05:34 <rfolco> mwhahaha, we going to try pushing master ones to test
14:05:44 <mwhahaha> k
14:06:01 <marios_|ruck> mwhahaha: i was out yesterday so probably missed something do you mean buildcontainers for stein i will catch up with rfolco sounds like he was looking at that
14:06:10 <beagles> o/
14:06:39 <quiquell> o/
14:06:44 <rfolco> marios_|ruck, actually weshay_pto said he was going to build, but he is on pto, so zbr is going to take a look
14:07:09 <marios_|ruck> rfolco: ack lets talk in the ci community call next
14:07:14 <rfolco> k
14:08:13 <rfolco> jaosorior, that's it from my side.
14:08:20 <jaosorior> rfolco: ack; thanks
14:08:28 <jaosorior> The next topic is: ( Tengu ): need reviews on validation patches
14:08:33 <jaosorior> #link https://trello.com/c/k96ySxA0/18-review-migrating-validations-playbooks-to-their-own-ansible-role
14:08:37 <Tengu> all is said :)
14:08:50 <jaosorior> that's a lot of patches
14:09:03 <Tengu> we really need ppl to get on that topic and make the whole bunch of patches. There are about 35 patches (32 in that card, plus some others in other cards)
14:09:07 <jaosorior> alright folks! If you have a chance, please review!
14:09:32 <Tengu> they are mostly trivial patches in addition, anyone should be able to get a hand on them :)
14:09:41 <jaosorior> Tengu: might wanna use this topic https://review.openstack.org/#/q/topic:bp/validation-framework+(status:open)
14:09:59 <Tengu> jaosorior: indeed :)
14:10:37 <Tengu> oh, just beware, they are all stacked together, at least the ones from the tripleo-validations package
14:10:44 <Tengu> order does matter :)
14:10:54 <Tengu> anyway. end of communication on my side. Thanks!
14:12:09 <jaosorior> #topic Squad status
14:12:15 <jaosorior> ci
14:12:17 <openstackgerrit> Ronelle Landy proposed openstack/tripleo-quickstart-extras master: Add build-test to virthost bm  https://review.openstack.org/647580
14:12:18 <jaosorior> #link https://etherpad.openstack.org/p/tripleo-ci-squad-meeting
14:12:20 <jaosorior> upgrade
14:12:22 <jaosorior> #link https://etherpad.openstack.org/p/tripleo-upgrade-squad-status
14:12:24 <jaosorior> containers
14:12:26 <jaosorior> #link https://trello.com/b/S8TmOU0u/tripleo-podman
14:12:28 <jaosorior> integration
14:12:30 <jaosorior> #link https://etherpad.openstack.org/p/tripleo-integration-squad-status
14:12:32 <jaosorior> cli
14:12:34 <jaosorior> #link https://etherpad.openstack.org/p/tripleo-ui-cli-squad-status
14:12:36 <jaosorior> validations
14:12:38 <jaosorior> #link https://etherpad.openstack.org/p/tripleo-validations-squad-status
14:12:40 <jaosorior> networking
14:12:42 <jaosorior> #link https://etherpad.openstack.org/p/tripleo-networking-squad-status
14:12:45 <jaosorior> security
14:12:46 <jaosorior> #link https://etherpad.openstack.org/p/tripleo-security-squad
14:12:48 <jaosorior> edge
14:12:50 <jaosorior> #link https://etherpad.openstack.org/p/tripleo-edge-squad-status
14:12:52 <jaosorior> Any squad wanting to bring up their status, or a topic for the general public?
14:13:28 <fultonj> integration -> ceph we're working on getting nautilus working in rdo . details in https://review.rdoproject.org/r/#/c/18721/
14:13:32 <fultonj> fmount: ^
14:13:37 <fultonj> just an fyi
14:14:25 <jaosorior> thanks for bringing it up
14:14:27 <fmount> we're trying to have a clean job with latest nautilus containers
14:15:11 <marios_|ruck> jaosorior: i have one related to rocky containers build job. we are trying to merge a new periodic based on the upstream as we have for master. basically we are using a hack for --exclude containers sed like https://review.openstack.org/#/c/645562/4/playbooks/tripleo-buildcontainers/templates/build.sh.j2@7 and we are planning on doing those https://review.openstack.org/#/q/topic:cherrypick-excludes-containers-build and removing the sed c
14:15:35 <marios_|ruck> mwhahaha: we spoke about that briefly last week the --excludes i mean. we need it for grafana in rocky case (it was failing with it)
14:15:49 <mwhahaha> marios_|ruck: we build grafana?
14:15:56 <marios_|ruck> mwhahaha: well looks like it
14:15:57 <marios_|ruck> :D
14:16:01 <mwhahaha> we shouldn't be excluding things
14:16:04 <mwhahaha> that means we need to fix it
14:16:24 <marios_|ruck> mwhahaha: well we're excluding a few things esp for f28 but also centos
14:16:31 <mwhahaha> wat
14:16:34 <marios_|ruck> mwhahaha: opendaylight for dcentos
14:16:35 <mwhahaha> we shouldn't be excluding anything
14:16:36 <marios_|ruck> sec
14:16:50 <mwhahaha> that means the default build is a failure
14:17:07 <mwhahaha> f28 we know because we don't have packages but for centos everything should build
14:17:11 <marios_|ruck> mwhahaha:  here https://github.com/openstack-infra/tripleo-ci/blob/92b2ac6fdda534586bbf1890718a30c42d6f03a2/playbooks/tripleo-buildcontainers/vars/common.yaml#L11
14:17:20 <marios_|ruck> mwhahaha: so we can take this to cmmunity call after this if you're available?
14:17:30 <mwhahaha> maybe
14:17:38 <marios_|ruck> mwhahaha: right now though our priority is to get a run for that rocky periodic cos rocky promotions blocked on it
14:17:47 <marios_|ruck> mwhahaha: and rocky is the only one that didn't promote last week
14:18:33 <openstackgerrit> Natal Ngétal proposed openstack/python-tripleoclient master: Replace print by log.  https://review.openstack.org/639344
14:20:40 <mwhahaha> we'll chat about this after
14:20:42 * mwhahaha pokes jaosorior
14:21:04 <jaosorior> mwhahaha: o/
14:21:32 <mwhahaha> we can likely continue now?
14:21:46 <jaosorior> probably; was just waiting in case anybody else wanted to chime in with something else
14:21:50 <jaosorior> anyway
14:21:53 <jaosorior> #topic bugs & blueprints
14:21:57 <jaosorior> #link https://launchpad.net/tripleo/+milestone/stein-3
14:22:00 <jaosorior> For Stein we currently have 18 (for stein-3) blueprints open in Launchpad.
14:22:02 <jaosorior> Bugs: 208 (+9) stein-rc1, 290 (-1) train-1 in Launchpad. 104 (0) open Storyboard bugs.
14:22:03 <openstack> bug 208 in Baz (deprecated) "build fails on gcc4" [Medium,Fix released] https://launchpad.net/bugs/208
14:22:04 <jaosorior> #link https://storyboard.openstack.org/#!/project_group/76
14:23:10 <jaosorior> #topic projects releases or stable backports
14:23:21 <openstackgerrit> Natal Ngétal proposed openstack/python-tripleoclient master: Replace print by log.  https://review.openstack.org/639344
14:24:39 <jaosorior> #topic specs
14:24:46 <jaosorior> #link https://review.openstack.org/#/q/project:openstack/tripleo-specs+status:open
14:24:49 <jaosorior> Any specs folks want to bring attention to?
14:24:52 <Tengu> yep
14:25:06 <Tengu> a spec that would allow to manage certificate with certmonger from ansible instead of puppet: https://review.openstack.org/#/c/645508/
14:25:09 <Tengu> well.
14:25:11 <Tengu> #link https://review.openstack.org/#/c/645508/
14:26:03 <jaosorior> Tengu: while I like that spec; I think it would be more appropriate for Train
14:26:26 <marios_|ruck> :qa
14:26:43 <Tengu> jaosorior: maybe? we might implement the ansible role in stein, use it in train and create the proper module in //
14:27:37 <Tengu> jaosorior: I'm in touch with Security about that topic.
14:27:43 <jaosorior> Tengu: right; I think targetting the spec for Train would make more sense, even if some work (such as creating the initial role) is started already in Stain.
14:27:45 <jaosorior> * Stain
14:27:48 <jaosorior> uugh
14:27:50 <jaosorior> Stein
14:28:08 <Tengu> ok. so that would be the first one for Train then, right?
14:28:23 <jaosorior> yep :D
14:28:33 <Tengu> will create the tree first then :).
14:28:54 * Tengu is used to it now
14:30:19 <jaosorior> Tengu: thanks for bringing it up
14:30:23 <jaosorior> #topic open discussion
14:30:49 <openstackgerrit> Cédric Jeanneret proposed openstack/tripleo-specs master: Create Train specs placeholder  https://review.openstack.org/647753
14:31:10 <mjturek> hey, I've got one
14:31:14 * mjturek grabs paste
14:31:29 <mjturek> Not confident that this is the best spot to bring this up, but wanted to bring some attention here. https://lists.rdoproject.org/pipermail/dev/2019-March/009042.html baha Vorrtex and I have been working to  introduce ppc64le container images to RDO. We'd actually like to get them published to Dockerhub and we were wondering if anyone here had anything to add to the discussion of how we handle the uploads
14:31:50 <openstackgerrit> David Peacock proposed openstack/tripleo-docs master: WIP - DNM - Update container docs with podman commands replacing docker  https://review.openstack.org/644683
14:32:01 <openstackgerrit> Cédric Jeanneret proposed openstack/tripleo-specs master: Create Train specs placeholder  https://review.openstack.org/647753
14:32:40 <mjturek> or is this  a better discussion for the community call?
14:33:14 <jaosorior> mjturek: maybe it's better for the community call in #rdo
14:33:49 <mjturek> jaosorior: is that just an IRC meeting? Or is it an actual voice chat?
14:34:01 * Vorrtex is curious as well
14:34:03 <marios_|ruck> mjturek: o/ sure we can discuss there . have you though about how you'll tag images. for the master container build job we are tagging with the delorean hash from the tripleo-ci-testing repo. that is then used during the deploy to pull the right containers
14:34:33 <openstackgerrit> Merged openstack/tripleo-validations master: Add repos validations role.  https://review.openstack.org/640036
14:34:38 <marios_|ruck> mjturek: we can at least point you to how we do the push for rdo registry container images we are building
14:35:11 <marios_|ruck> mjturek: but yeah rdo is probably the place to bring that discussion
14:36:03 <jaosorior> mjturek: IRC AFAIK
14:36:14 <mjturek> marios_|ruck: We'd like to keep it as close to what is currently done for x86. I think Vorrtex has some good opinions here for properly setting manifest values. We'd like to also push to dockerhub
14:36:26 <Vorrtex> marios_|ruck the running idea (and strong desire from us) is to have manifest list images be the default tag, and individual images use the same tag that it was built with, but appending an architecture specific to that image.  The "consumer" workflow doesn't change, meaning anything pulling the image would still grab from the same tag structure that's currently available, but the image retrieved would be arch specific.  In
14:36:26 <Vorrtex> this case, x86_64 or ppc64le
14:38:15 <marios_|ruck> Vorrtex: yeah that would work so "tag_x86_64" for example and same tag with ppc. it would need some changes in ci code too i mean we'd need to include that information in the containers prepare tag used during the deploy but yeah that sounds reasonable.
14:38:46 <Vorrtex> marios_|ruck exactly, exactly.  So still a conversation for tomorrow's RDO meeting, then?
14:38:54 <zbr> rfolco: yep, i am on stein, but i need help with few a review re stein
14:39:06 <marios_|ruck> Vorrtex: well, yes, but there is also a ci community call next after this
14:39:18 <marios_|ruck> Vorrtex: rdo is who you need to talk to about pushing images there
14:39:49 <marios_|ruck> Vorrtex: but you might want to see if others in tripleo-ci have thoughts about it or just ot introduce the topic (its a voice bluejeans call rfolco will advertise it in a minute)
14:39:58 <mjturek> cool marios_|ruck we'll all join that as well (baha)
14:40:14 <openstackgerrit> Cédric Jeanneret proposed openstack/tripleo-specs master: New spec: manage certmonger with ansible instead of puppet  https://review.openstack.org/645508
14:40:23 <baha> mjturek: +1
14:41:43 <Vorrtex> marios_|ruck yep, thanks for the information
14:42:14 <marios_|ruck> ack Vorrtex thanks
14:42:25 <zbr> rfolco: marios_|ruck : stein release configs, made few minor changes https://review.openstack.org/#/c/643963/9
14:43:01 <rfolco> CI community meeting (office hours) starts now at https://bluejeans.com/4113567798 - agenda: https://etherpad.openstack.org/p/tripleo-ci-squad-meeting
14:43:16 <rfolco> mjturek, baha Vorrtex ^
14:43:35 <mjturek> awesome rfolco, joining :)
14:43:43 <marios_|ruck> rfolco: s/now/after this meeting :D
14:43:49 <baha> Thank you!
14:43:50 <mjturek> oh!
14:43:59 * mjturek waits until top of the hour
14:44:42 <jaosorior> Alright! I guess we can finish this meeting now
14:44:49 <jaosorior> Thanks for joining everyone!
14:44:52 <jaosorior> #endmeeting