14:00:24 <mwhahaha> #startmeeting tripleo
14:00:24 <openstack> Meeting started Tue May 21 14:00:24 2019 UTC and is due to finish in 60 minutes.  The chair is mwhahaha. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:00:24 <mwhahaha> #topic agenda
14:00:24 <mwhahaha> * Review past action items
14:00:24 <mwhahaha> * One off agenda items
14:00:24 <mwhahaha> * Squad status
14:00:25 <mwhahaha> * Bugs & Blueprints
14:00:25 <mwhahaha> * Projects releases or stable backports
14:00:26 <mwhahaha> * Specs
14:00:26 <mwhahaha> * open discussion
14:00:26 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
14:00:27 <mwhahaha> Anyone can use the #link, #action and #info commands, not just the moderatorǃ
14:00:27 <mwhahaha> Hi everyone! who is around today?
14:00:28 <openstack> The meeting name has been set to 'tripleo'
14:00:44 <beagles> o/
14:00:50 <ekultails> o/
14:01:09 <jrist> o/
14:01:09 <marios_|ruck> o/
14:01:15 <Tengu> «o/
14:01:34 <fultonj> o/
14:01:35 <rf0lc0> o/
14:01:41 <fmount> o/
14:01:56 <rh-jelabarre> o/
14:03:50 <mwhahaha> alright looks like we've got a few people here
14:03:59 <mwhahaha> and a light agenda so let's go
14:04:00 <mwhahaha> #topic review past action items
14:04:05 <chandankumar> \o/
14:04:07 <mwhahaha> None.
14:04:25 <dpeacock> o/
14:04:44 <jfrancoa> o/
14:04:47 <mwhahaha> #topic one off agenda items
14:04:52 <mwhahaha> #link https://etherpad.openstack.org/p/tripleo-meeting-items
14:04:57 <mwhahaha> (fmount|fultonj) ceph-dashboard blueprint: we have the blueprint and the first PRs merged on ceph-ansible
14:05:03 <mwhahaha> #link https://blueprints.launchpad.net/tripleo/+spec/ceph-dashboard/
14:05:24 <panda|rover> o/
14:05:30 <gchamoul> o/
14:05:35 <ksambor_> o/
14:05:40 <fmount> hi, we have the first ceph-ansible code merged, so I think we can review the ceph-dashboard bp to move forward
14:05:42 <redrobot> \o
14:05:44 <fmount> fultonj: ^
14:05:50 <fultonj> can the blueprint be approved?
14:06:31 <mwhahaha> i'll take a look today
14:06:42 <fmount> mwhahaha: ok thx
14:06:45 <arxcruz> o/
14:07:02 <bogdando> o/
14:07:35 <fmount> mwhahaha: if you have question about the bp ping me and let's discuss about it
14:07:39 <mwhahaha> k
14:07:44 <fmount> (or anyone ^)
14:07:55 <mwhahaha> fultonj: so did you add the question abotu the ansible bits?
14:07:59 <mwhahaha> i think it depends on what it looks like
14:08:23 <fultonj> on what the embeded ansible looks like :)
14:08:24 <fultonj> ?
14:08:29 <mwhahaha> yea
14:08:42 <fultonj> https://review.opendev.org/#/c/657166/1/deployment/ceph-ansible/ceph-mon.yaml
14:09:03 <fultonj> mwhahaha: before we dive into the embded ansible...
14:09:12 <fultonj> is that a pattern we want to move to?
14:09:31 <mwhahaha> you mean using a role?
14:09:32 <mwhahaha> yes
14:09:35 <fultonj> scale down tasks and wanting simple re-use is driving this
14:09:45 <openstackgerrit> Chandan Kumar (raukadah) proposed openstack/tripleo-quickstart master: [fs017]Remove member role from auth.tempest_roles overrides  https://review.opendev.org/660351
14:09:52 <fultonj> and i see a pattern similar to how we're using validations
14:10:05 <fultonj> mwhahaha: but we ship validations ansible as a package
14:10:15 <fultonj> tripleo-ansible isn't installed by default AFAICT
14:10:25 <mwhahaha> i'm not sur eit's packaged yet?
14:10:31 <mwhahaha> i think that's something we can try and get to this cycle
14:10:33 <fultonj> mwhahaha: yeah, it's probably not
14:10:38 <mwhahaha> it should just be a dep for the undercloud
14:10:41 <mwhahaha> or THT
14:11:38 <mwhahaha> well it should be packaged
14:11:40 <mwhahaha> https://bugzilla.redhat.com/show_bug.cgi?id=1645311
14:11:40 <openstack> bugzilla.redhat.com bug 1645311 in Package Review "Package review: tripleo-ansible - Ansible project for TripleO" [Unspecified,Closed: rawhide] - Assigned to jpena
14:11:41 <fultonj> gfidente: ^ fyi
14:12:07 <mwhahaha> https://github.com/rdo-packages/tripleo-ansible-distgit
14:13:02 <fultonj> yay it's packaged
14:13:15 <fultonj> ' yum install tripleo-ansible' "just works"
14:13:18 <mwhahaha> though looking at the contents, it seems to be a module
14:13:40 <mwhahaha> i think the original intent of that repo was for like day2 ops stuff
14:13:53 <mwhahaha> tripleo-common might be the best bet for any roles (i hate saying this)
14:14:38 <fultonj> https://github.com/openstack/tripleo-common/tree/master/playbooks/roles
14:14:43 <jrist> ha
14:15:17 <fultonj> so i can make a ceph dir and get started
14:15:33 <bogdando> mwhahaha: having tripleo-ansible and keeping piling ansible stuff into tripleo-common would be a weird strategy
14:15:46 <fultonj> just wanted to ask before i got started if i was heading in the right general direction
14:15:50 <fmount> so we can populate playbooks/roles in tripleo-common?
14:16:07 <mwhahaha> yea but if you look at the layout of tripleo-ansible, it doesn't really seem like a great place to put roles
14:16:07 <fmount> bogdando: agree
14:16:35 <mwhahaha> the original goal was to use the ansible-role-tripleo-* things for these types of thing
14:16:40 <fultonj> so i can make a ceph dir and get started (in tripleo-common)
14:16:44 <fultonj> i meant common
14:16:45 <mwhahaha> but in this case it's like a tripleo-ceph role that's needed
14:16:55 <weshay> o/
14:17:19 <fultonj> it's for deployments but will have day2 overlap
14:17:23 <fultonj> right now it's more deployments leaning
14:17:31 <mwhahaha> yea that's the awkwardness
14:18:16 <mwhahaha> I'm tempted to say we start using tripleo-ansible
14:18:23 <mwhahaha> though not sure what that layout should be
14:18:31 <owalsh> fultonj: I guess the cache mgmt ansible is similar... could we just restructure tripleo-ansible?
14:18:45 <fultonj> owalsh: right, i assume you'll hit this question too
14:19:39 <fmount> fultonj: this could be a good opportunity to restructure tripleo-ansible
14:19:59 <fmount> mwhahaha: wdyt ^
14:20:03 <mwhahaha> sure
14:20:26 <fultonj> AFAICT tripleo-ansible isn't really used. e.g. it's not shipped by default.
14:20:30 <fultonj> it was going to be
14:20:37 <fultonj> so now what do we do with it
14:20:38 <fultonj> ?
14:21:07 <fultonj> slagle: ^ ?
14:21:13 <bogdando> ship it ?
14:21:28 <mwhahaha> it had podman related modules
14:21:34 <mwhahaha> which we might actually want to use at some point
14:21:40 <EmilienM> which isn't used anywhere nor tested
14:22:04 <Tengu> (molecule is needed for testing :D)
14:22:06 <bogdando> and we could as well collaps ansible-role-tripleo-* things into it
14:22:46 <mwhahaha> if someone wants to do the work, let's do it
14:22:55 <mwhahaha> i would like to eventually look at replacing paunch the cli with an ansible version
14:23:05 <mwhahaha> so maybe that could be handled in tripleo-ansible as well
14:23:11 <fultonj> sounds to me like, unless someone's going to restructure tripleo-ansible the place today would be common.
14:23:35 <owalsh> also what if we want to backport any of the ansible stuff?
14:24:06 <fultonj> are roles in tripleo-common include_role'd in tht already?
14:24:10 <fultonj> does that pattern exist?
14:24:19 <fultonj> we could punt the move until later
14:24:37 <mwhahaha> i think they are
14:24:39 <mwhahaha> would need to check the THT
14:24:59 <mwhahaha> techincally we have two sets of roles in tripleo-common
14:25:04 <mwhahaha> the octavia stuff and https://opendev.org/openstack/tripleo-common/src/branch/master/roles
14:26:38 <fultonj> do we want to do the move during train OR put new stuff in common and differ the move to post-train?
14:27:33 <bogdando> it seems that pretty all roles importes/includes in tht are from the tripleo-common
14:27:36 <EmilienM> fultonj: yes include_role is used already
14:27:54 <EmilienM> (at least for tripleo-containers-rm)
14:27:55 <bogdando> so let's keep it as is perhaps
14:28:54 <fultonj> perhaps for train it would be too much to make this change and it sounds like i can use an existing pattern without messing with the existing deployment framework
14:29:01 <openstackgerrit> Merged openstack/tripleo-ci master: Add another nodepool provider ID  https://review.opendev.org/660138
14:29:24 <fultonj> and if backports wanted as per owalsh it would work from there
14:29:26 <fultonj> thanks
14:29:34 <owalsh> ack
14:30:23 <fmount> fultonj: +1
14:30:31 <mwhahaha> k so i guess propose in tripleo-common and we'll punt on the tripleo-ansible bits for now
14:31:49 <fultonj> thanks all, next topic?
14:31:58 <openstackgerrit> mathieu bultel proposed openstack/tripleo-heat-templates master: Force ansible serial to 1 for the controller  https://review.opendev.org/658814
14:32:49 <chandankumar> If there is no any other topic in queue I want to discuss about this blueprint https://blueprints.launchpad.net/tripleo/+spec/os-client-config-switch
14:33:15 <mwhahaha> meh
14:33:42 <mwhahaha> so we already partially implemented that for standalone
14:33:48 <chandankumar> since we have added support for clouds.yaml for standalone and undercloud
14:33:54 <mwhahaha> we'd need to create a workflow for generating that for the overcloud
14:34:00 <chandankumar> I am about to start working on overcloud
14:34:07 <mwhahaha> I would just generate both for now
14:34:15 <mwhahaha> and we can remove the *rc files in a later release
14:34:30 <chandankumar> but the question is https://opendev.org/openstack/tripleo-heat-templates/src/branch/master/extraconfig/post_deploy current code and tht stuff resides here
14:34:52 <chandankumar> can we move the same https://opendev.org/openstack/tripleo-heat-templates/src/branch/master/extraconfig/post_deploy/clouds_yaml.py script to python-tripleoclient
14:35:02 <mwhahaha> it wouldn't be tripleoclient
14:35:05 <mwhahaha> it would be in tripleo-common
14:35:09 <mwhahaha> and tripleoclient
14:35:23 <chandankumar> and generate the clouds.yaml for stdanlone overcloud and undercloud
14:35:25 <mwhahaha> you'll want to find the existing stackrc generation and either modify it or duplicate it
14:35:41 <mwhahaha> the undercloud would be using the post_deploy method
14:35:43 <mwhahaha> the overcloud is different
14:35:55 <mwhahaha> there was a bug about the fact we generate this info in like 3 places
14:36:47 <chandankumar> is it this one https://bugs.launchpad.net/tripleo/+bug/1801927
14:36:48 <openstack> Launchpad bug 1801927 in tripleo "[RFE] Set up clouds.yaml in undercloud stack user" [Medium,Fix released] - Assigned to Harald Jensås (harald-jensas)
14:36:49 <chandankumar> ?
14:36:53 <mwhahaha> https://opendev.org/openstack/tripleo-common/src/branch/master/workbooks/deployment.yaml#L720
14:37:15 <mwhahaha> no different one
14:37:58 <mwhahaha> https://bugs.launchpad.net/tripleo/+bug/1719369
14:37:59 <openstack> Launchpad bug 1719369 in tripleo "multiple methods for generating openrc files" [High,Triaged]
14:39:08 <mwhahaha> anyway feel free to workon that
14:39:33 <mwhahaha> just do it with the existing openrc files in place and we can deprecate those
14:39:35 <chandankumar> ok, then we need to make changes in the tripleo-common and trigeer clouds.yaml step just after rc file generation
14:40:44 <chandankumar> mwhahaha: one more question, if it is a multinode deployment, do we used a single clouds.yaml file for storing undercloud and overcloud os_cloud name?
14:41:01 <mwhahaha> we would need to
14:41:15 <mwhahaha> which makes this all the trickier :D
14:41:26 <chandankumar> ok, then I will work on that, thanks :-)
14:41:31 <chandankumar> that's it from my side
14:41:34 <mwhahaha> alright moving on
14:41:42 <mwhahaha> #topic Squad status
14:41:42 <mwhahaha> ci
14:41:42 <mwhahaha> #link https://etherpad.openstack.org/p/tripleo-ci-squad-meeting
14:41:42 <mwhahaha> upgrade
14:41:42 <mwhahaha> #link https://etherpad.openstack.org/p/tripleo-upgrade-squad-status
14:41:43 <mwhahaha> edge
14:41:43 <mwhahaha> #link https://etherpad.openstack.org/p/tripleo-edge-squad-status
14:41:44 <mwhahaha> integration
14:41:44 <mwhahaha> #link https://etherpad.openstack.org/p/tripleo-integration-squad-status
14:41:45 <mwhahaha> validations
14:41:45 <mwhahaha> #link https://etherpad.openstack.org/p/tripleo-validations-squad-status
14:41:46 <mwhahaha> networking
14:41:46 <mwhahaha> #link https://etherpad.openstack.org/p/tripleo-networking-squad-status
14:41:49 <mwhahaha> any status things to highlight?
14:44:27 <fultonj> Tengu: are we still planning to have integrated step validations in train?
14:44:50 <mwhahaha> we talked about it, i think so
14:44:59 <Tengu> fultonj: well the code for that is already present, so yes.
14:45:33 <marios|ruck|call> Tengu: didn't you already activate some on a few jobs the simple containerd/service ones?
14:45:33 <fultonj> ack
14:45:58 <Tengu> marios|ruck|call: it's not in the tripleo-validations, it's still in tripleo-quickstart-extras
14:46:01 <marios|ruck|call> Tengu: oh step validations... sorry that is diffferent
14:46:16 <Tengu> :)
14:46:50 <mwhahaha> alright if there are no more status related things, moving on
14:47:30 <mwhahaha> #topic bugs & blueprints
14:47:30 <mwhahaha> #link https://launchpad.net/tripleo/+milestone/train-1
14:47:30 <mwhahaha> For Train we currently have 20 blueprints and 490 (+2) open Launchpad Bugs. 488 train-1, 2 train-2.  104 open Storyboard bugs.
14:47:30 <mwhahaha> #link https://storyboard.openstack.org/#!/project_group/76
14:47:49 <openstackgerrit> Bogdan Dobrelya proposed openstack/tripleo-specs master: Add a spec for K8s Metal3 baremetal operator  https://review.opendev.org/659288
14:47:54 <mwhahaha> any bugs to highlight?
14:50:12 <openstackgerrit> Merged openstack/tripleo-heat-templates stable/stein: Set arp_notify to match ndisc_notify  https://review.opendev.org/660209
14:50:32 <mwhahaha> sounds like nope
14:50:38 <mwhahaha> #topic projects releases or stable backports
14:50:47 <mwhahaha> we EOL'd pike last week
14:50:48 <mwhahaha> just fyi
14:50:52 <mwhahaha> so there was a final release for that
14:51:11 <mwhahaha> I need to sync up with the release folks and get them to EOL ocata as well as I don't think it was ever completed for us
14:51:17 <mwhahaha> any backports that need reviewing?
14:53:09 <ksambor_> https://review.opendev.org/#/c/658745/ PTAL (backport to stein)
14:54:04 <mwhahaha> k
14:54:06 <mwhahaha> done
14:54:13 <mwhahaha> #topic specs
14:54:14 <mwhahaha> #link https://review.openstack.org/#/q/project:openstack/tripleo-specs+status:open
14:54:20 <mwhahaha> please take a moment to review teh specs
14:54:30 <mwhahaha> we want to get them reviewed/merged by M! which is coming up in a few weeks
14:54:34 <mwhahaha> also M1
14:54:51 <bogdando> https://blueprints.launchpad.net/tripleo/+spec/undercloud-minion there is an idea to extend this to a particular Ironic Conductor deployment role not limited to UC
14:55:08 <ksambor_> mwhahaha, thanks
14:55:24 <mwhahaha> any spec related items?
14:55:30 <bogdando> mwhahaha: ^^
14:55:46 <bogdando> can we design it the way it won't be UC limited
14:55:47 <bogdando> ?
14:55:57 <mwhahaha> that is not the goal
14:56:05 <mwhahaha> so no
14:56:12 <mwhahaha> we're not working on an standalone ironic
14:56:15 <bogdando> well, I was thinking a role can be applied to a node you know...
14:56:26 <mwhahaha> we already have an ironic conductor role
14:56:27 <bogdando> not necessary to undercloud
14:56:33 <bogdando> ok got it
14:56:36 <mwhahaha> so the undercloud minion is it's own seperate thing
14:56:51 <mwhahaha> it'll have just heat-engine and ironic-conductor roles that can be enabled/disabled
14:56:59 <mwhahaha> but it has to talk to an undercloud (for db/messaging)
14:57:05 <bogdando> do you think allowing that existing Ironic conductor role to be used as a minion may fit that spec scope?
14:57:15 <mwhahaha> it's already in the reviews
14:57:22 <bogdando> not UC minion, just a minion
14:57:27 <mwhahaha> no
14:57:30 <bogdando> :(
14:57:53 <mwhahaha> maybe i'm not understanding the target architecture
14:58:01 <mwhahaha> ironic-conductor is not a standalone thing
14:58:04 <mwhahaha> what would it talk to?
14:58:41 <bogdando> the case is doing pretty same, but not against undercloud. But some deployed-server to co-locate the Ironic conductor and assisting undercloud as a minion
14:58:56 <bogdando> that's would be the overcloud compute
14:58:59 <bogdando> just pre-deployed
14:59:06 <bogdando> think of it as undercloud minion :)
14:59:11 <mwhahaha> ...
14:59:11 <bogdando> just mixed roles
14:59:25 <mwhahaha> no because you have to wire up the endpoint against the undercloud
14:59:30 <mwhahaha> you can't mix under/overcloud roles
14:59:34 <bogdando> lesigh
14:59:37 <bogdando> ok then
15:00:00 <mwhahaha> #topic open discussion
15:00:11 <mwhahaha> alright we have like 0 time left, any other items?
15:01:12 <openstackgerrit> Emilien Macchi proposed openstack/tripleo-common stable/stein: fix 404 when requesting empty tripleo container image catalog  https://review.opendev.org/660418
15:01:18 <mwhahaha> alright thanks everyone
15:01:19 <mwhahaha> #endmeeting