14:03:00 <spotz> #startmeeting RDO meeting - 2020-06-24
14:03:00 <openstack> Meeting started Wed Jun 24 14:03:00 2020 UTC and is due to finish in 60 minutes.  The chair is spotz. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:03:01 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
14:03:03 <openstack> The meeting name has been set to 'rdo_meeting___2020_06_24'
14:03:10 <spotz> #topic Roll Call
14:03:13 <mjturek> o/
14:03:26 <spotz> #chair mjturek
14:03:27 <openstack> Current chairs: mjturek spotz
14:04:33 <amoralej> o/
14:04:40 <spotz> mjturek: We'll give folks a few minutes
14:04:44 <spotz> @chair amoralej
14:05:03 <jcapitao> o/
14:05:04 <spotz> #chair amoralej
14:05:04 <openstack> Current chairs: amoralej mjturek spotz
14:05:17 <spotz> #chair jcapitao
14:05:17 <openstack> Current chairs: amoralej jcapitao mjturek spotz
14:06:11 <spotz> #topic New faces in multiarch support
14:06:21 <spotz> mjturek: If you'd like to start
14:06:24 <mjturek> sure!
14:06:54 <mjturek> just wanted to call out Vorrtex and jfreud who will be helping with the ppc64le containers and images jobs
14:07:24 <mjturek> if you have questions on a patch or anything related to that effort, feel free to ping us
14:08:25 <amoralej> good to see new faces around :)
14:08:37 <rdogerrit> Eric Harney proposed openstack/os-brick-distgit rpm-master: Add %check unit tests  https://review.rdoproject.org/r/19338
14:08:37 <mjturek> agreed!
14:09:20 <amoralej> i will be happy to help them if they need some support during onboarndig
14:09:28 <mjturek> thank you amoralej :)
14:09:35 <spotz> +1
14:09:40 <mjturek> and spotz :)
14:10:15 <rdogerrit> Chandan Kumar proposed rdo-jobs master: [WIP] new container build push to testingmaster  https://review.rdoproject.org/r/28194
14:10:21 <spotz> And you had one more thing
14:11:37 <mjturek> oh! right, baha will be moving on but will be around for questions need be!
14:11:54 <mjturek> thanks for everything baha!
14:12:09 <spotz> Thanks baha!
14:12:41 <spotz> Anything else on changes in multiarch support?
14:12:50 <baha> Of course =) It was great working on this.
14:13:00 <mjturek> nope that's it for now!
14:13:14 <spotz> Don't be a stranger:)
14:13:29 <spotz> #topic RDO Test Days
14:13:34 <amoralej> thanks baha!
14:13:47 <spotz> #link  http://rdoproject.org/testday/victoria/milestone1/
14:14:37 <spotz> So according to that link the next 2 days are supposed to be test days. Nothing is actually on the events calendar. So just wanted to see if this was still taking place and what we might need to do to support it
14:15:20 <spotz> And I wanted to make sure we had somethings for the agenda:)
14:16:29 <amoralej> imo, and given the low participation in last test days, i'd skip this one and would try do it in M2
14:16:41 <amoralej> with some more announcement
14:17:08 <amoralej> and maybe some new ideas that would improve engagement
14:17:37 <amoralej> any new ideas about this is appreciated
14:17:54 <spotz> Ok do we want to take the time now to discuss? Or do add it back to the agenda a little closer to M2?
14:18:14 <amoralej> i'd add it to next meetings agenda
14:18:24 <spotz> Could we organize it more like a hackfest have everyone in IRC or BJ? Swag for participation etc?
14:19:02 <spotz> I can hit up jbrooks if that's something we might want
14:19:18 <amoralej> that'd be cool, let's discuss it
14:19:31 <amoralej> in the past we did several things
14:19:39 <spotz> #action amoralej add RDO Test Days to next weeks meeting
14:19:51 <amoralej> like providing vms for testing
14:19:53 <amoralej> etc..
14:20:03 <mjturek> ooo that sounds fun
14:20:18 <spotz> Ok lets talk next week or hit me up sooner if you want to have pre-meeting brainstorming
14:20:41 <amoralej> now, i'm not sure what may attract people
14:20:49 <amoralej> yes, i think that'd be fine spotz
14:21:14 <spotz> #action spotz talk to jbrooks for possibility of swag/needed things for RDO test days
14:21:36 <spotz> I can atleast get that underway if we might need it
14:21:52 <rdogerrit> Eric Harney proposed openstack/os-brick-distgit rpm-master: Add %check unit tests  https://review.rdoproject.org/r/19338
14:22:08 <spotz> As we're going to talk about the test days more next week I'll move on.
14:22:09 <rdogerrit> Chandan Kumar proposed rdo-jobs master: [DNM] force c8 train jobs  https://review.rdoproject.org/r/28204
14:22:16 <spotz> #topic RDO Doc Days
14:22:30 <spotz> #link  http://rdoproject.org/events/docdays/
14:23:21 <spotz> Again not showing up on the calendar. So something we want to still have? The dates are first week of August so we would need to start planning and advertising
14:23:49 <spotz> And swag/incentives I think would still apply possibly to get participation?
14:24:29 <rdogerrit> Sandeep Yadav created rdo-infra/ci-config master: Add train c8 Component promotion config  https://review.rdoproject.org/r/28214
14:26:05 <rdogerrit> Chandan Kumar proposed rdo-jobs master: [DNM] force c8 train jobs  https://review.rdoproject.org/r/28204
14:26:51 <amoralej> spotz, yes, first week of august sounds fine
14:27:10 <amoralej> spotz, maybe you can also share your experience with updating upstream doc
14:27:51 <spotz> amoralej: Do we know what we need to organize? I can definitely do that and the rdoproject.org site for any changes needed there in regards to Packstack installs
14:29:49 <amoralej> spotz, it may be a good oportunity to get feedback about RDO doc
14:30:15 <amoralej> we haven't thought much about it since some major update of the contributor part
14:30:53 <amoralej> i.e. we probably should metion kolla
14:30:58 <amoralej> or the projects that are using RDO
14:31:16 <spotz> Ok let me work on an agenda and will touch base with jbrooks on this as well. We'll follow up on this next week as well
14:31:20 <amoralej> pointers to how to use RDO
14:31:35 <spotz> #action spotz to do initial leg work on Doc Days and report back next week
14:31:38 <amoralej> or even, add some info about CI in the contributor part
14:31:59 <spotz> Sounds like everything just needs an update
14:31:59 <amoralej> so doc days may be something more like "what do you miss"
14:32:38 <amoralej> said this, I'll be on vacation in august :)
14:32:46 <spotz> And maybe break it into 2 sessions less days
14:32:50 <spotz> Ha!
14:33:14 <spotz> We can bump it:)
14:33:26 <spotz> Anything else on this?
14:33:43 <amoralej> not from my side
14:34:15 <spotz> #topic Next Week's Chair
14:34:28 <spotz> Volunteer?:)
14:34:48 <jcapitao> i can take it
14:35:25 <spotz> Thanks jcap
14:36:36 <spotz> Thanks jcapitao - that's better:)
14:36:45 <spotz> And that's July first already!
14:36:56 <spotz> #topic Open Floor
14:37:36 <spotz> Main install guides updated for RHEL8 as is the KEystone installation guide
14:38:30 <spotz> Ran into an issue with Placement not sure if its RDO related or Placement docs related and had to stop at Nova install due to a repo issue but it was during the time we had the repo issue
14:38:52 <amoralej> what's the issue with placement?
14:40:36 <spotz> Both on the verification. One you need to use pip3 and the other is adding a section into the httpd conf or the second and third verification commands don't work. Had the same issues with Train on the conf issue not the pip3
14:41:08 <spotz> /etc/httpd/conf.d/00-placement-api.conf
14:41:08 <spotz> <Directory /usr/bin>
14:41:08 <spotz> <IfVersion >= 2.4>
14:41:10 <spotz> Require all granted
14:41:12 <spotz> </IfVersion>
14:41:14 <spotz> <IfVersion < 2.4>
14:41:16 <spotz> Order allow,deny
14:41:18 <spotz> Allow from all
14:41:20 <spotz> </IfVersion>
14:41:22 <spotz> </Directory>
14:41:38 <amoralej> so, when using RDO packages, we shouldn't use pip3, unless there is some weird issue
14:42:00 <spotz> https://docs.openstack.org/placement/ussuri/install/verify.html
14:42:00 <spotz> pip3 install osc-placement
14:42:15 <amoralej> i'm pretty sure we have rpm for that
14:42:17 <spotz> I document my documentation so I don't forget:)
14:42:17 <amoralej> let me double check
14:42:25 <rdogerrit> Chandan Kumar created rdo-infra/ci-config master: Discover hashes url ( non-component ) only CentOS-7 distros  https://review.rdoproject.org/r/28215
14:42:47 <amoralej> yep there is python3-osc-placement
14:42:51 <spotz> The verification page FYI is for all the OSes so not rdo specific
14:42:58 <amoralej> mmm
14:43:01 <amoralej> oook
14:43:24 <amoralej> so it's kind of installation verification os-independent
14:43:25 <amoralej> ?
14:43:27 <spotz> yeah, hence the pip3 makes sense as we moved to python3, but I'm not sure if that conf change is only RDO
14:43:46 <spotz> Yeah, all of the install guides are like that
14:44:16 <spotz> But the others you don't have to install anything just run commands which should be generic and technically pip/pip3 is
14:44:44 <amoralej> but that verification part is executed in a different system that the one running openstack services, then
14:44:45 <amoralej> right?
14:44:59 <spotz> No on the controller
14:45:06 <amoralej> then pip3 is not a good idea
14:45:23 <amoralej> mixing rpm and pip can lead to issues
14:45:52 <amoralej> wrt httpd conf for placement
14:46:06 <amoralej> we usually overwrite what comes in the rpm
14:46:10 <spotz> I can put a blurb in for that atleast to use the package on rhel/centos. But I still need to get confirmation on the conf I might just need to build my own Ubuntu cluster
14:46:24 <amoralej> in fact most rpms doesn't provide any httpd conf and it's managed via puppet-<service>
14:46:25 <spotz> So RDO bug?
14:46:40 <amoralej> i.e. look at https://logserver.rdoproject.org/ci.centos.org/weirdo-generic-packstack-scenario001/10061/weirdo-project/logs/etc/conf.d/
14:46:54 <amoralej> you can see that 00-placement-api.conf is cleaned
14:47:08 <amoralej> and actual config is in 10-placement_wsgi.conf
14:47:17 <amoralej> with content https://logserver.rdoproject.org/ci.centos.org/weirdo-generic-packstack-scenario001/10061/weirdo-project/logs/etc/conf.d/10-placement_wsgi.conf.txt.gz
14:47:31 <amoralej> let me compare with the one in rpm
14:47:47 <spotz> ok
14:49:10 * spotz should have been QE in another life
14:49:12 <amoralej> so we are missing the Require all granted
14:49:14 <amoralej> right?
14:49:21 <spotz> yes
14:49:43 <amoralej> yes, can be fixed at RDO
14:49:49 <spotz> Now whether placement works fine without it I haven't test. I just know the second and third verification does not work
14:49:50 <amoralej> btw, i think we don't need conditional
14:50:00 <amoralej> that's just inteneded to work with httpd from el8
14:50:24 <spotz> Well would need a backport for atleast Train as well
14:50:24 <amoralej> verification are openstack commands, right?
14:50:49 <amoralej> do you want to send the fix?
14:51:00 <spotz> yes openstack commands
14:51:09 <amoralej> they should work fine, so yes, good to fix
14:51:12 <spotz> $ openstack --os-placement-api-version 1.2 resource class list --sort-column name
14:51:20 <spotz> $ openstack --os-placement-api-version 1.6 trait list --sort-column name
14:51:40 <amoralej> in fact, as said before, that line exist when deploying with puppet-placement
14:51:51 <spotz> weird
14:52:31 <spotz> Want an RDO project bug? I can put the fix in it. It's been ages since I built an RPM
14:52:52 <amoralej> just need to send the patch to review.rdoproject.org
14:52:58 <amoralej> https://review.rdoproject.org/r/#/q/project:openstack/placement-distgit
14:53:13 <amoralej> are you familiar with sending patches to RDO?
14:53:34 <spotz> Not really, mainly do upstream
14:53:37 <amoralej> it's similar workflow that the one for openstack project
14:53:59 <amoralej> just clone https://github.com/rdo-packages/placement-distgit
14:54:07 <amoralej> push your fix to placement-api.conf
14:54:10 <amoralej> and git review
14:54:23 <spotz> Ok I'll get that done this week:)
14:54:35 <amoralej> i can take care if you don't have a time slot
14:54:49 <amoralej> but it's a good oportunity to get in contact with RDO repos :)
14:56:14 <spotz> amoralej: There's always after work and I do have a meeting with APAC tonigh
14:56:32 <spotz> As we have 4 minutes left does anyone have anything else?
14:59:08 <spotz> #endmeeting