15:01:17 <ykarel> #startmeeting RDO meeting - 2019-02-06
15:01:18 <openstack> Meeting started Wed Feb  6 15:01:17 2019 UTC and is due to finish in 60 minutes.  The chair is ykarel. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:01:19 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:01:21 <openstack> The meeting name has been set to 'rdo_meeting___2019_02_06'
15:01:44 <ykarel> @all Please add agenda at https://etherpad.openstack.org/p/RDO-Meeting
15:01:54 <ykarel> #topic roll call
15:02:34 <jpena> o/
15:02:43 <amoralej> o/
15:02:55 <ykarel> #chair jpena amoralej
15:02:55 <openstack> Current chairs: amoralej jpena ykarel
15:03:20 <baha> o/
15:03:46 <ykarel> #chair baha
15:03:47 <openstack> Current chairs: amoralej baha jpena ykarel
15:05:32 <ykarel> Let's start
15:05:44 <ykarel> baha looks like you added agenda at wrong place
15:06:03 <ykarel> #topic Updates on removal of python2-* from Fedora 30 by EOM
15:06:16 <baha> I did, thanks for letting me know =)
15:06:34 <ykarel> so we did a good progress in fedora package cleanup and the status is at https://etherpad.openstack.org/p/fedora_py2_removal_tickets
15:06:49 <rdogerrit> Lee Yarwood created rdoinfo master: WIP Update Nova project maintainers  https://review.rdoproject.org/r/18737
15:07:09 <ykarel> we are currently blocked by a package https://src.fedoraproject.org/rpms/python-rackspace-auth-openstack which is python2 and is not owned by openstack-sig
15:07:32 <ykarel> amoralej is trying to contact maintainer for this, as soon as it's clear we can move forward with further cleanup
15:07:40 <amoralej> yes
15:07:42 <amoralej> i sent a mail
15:07:47 <amoralej> and ask for feedback in the bz
15:08:00 <amoralej> if the does not reply, i'll ask provenpackager to retire it
15:08:13 <ykarel> okk perfect
15:08:57 <ykarel> moving to next topic
15:09:09 <ykarel> #topic [amoralej] rdoinfo reorganization status
15:09:40 <amoralej> it's done :)
15:09:44 <rdogerrit> Lee Yarwood created config master: WIP Update Nova project cores  https://review.rdoproject.org/r/18738
15:09:46 <amoralej> reviews are merged
15:09:50 <amoralej> and jobs reorganized
15:10:48 <ykarel> also docs updated and info about new orgainsation is at https://www.rdoproject.org/documentation/intro-packaging/#rdoinfo
15:11:57 <ykarel> also a PR is open for feedback to update packages based on rdoinfo reorg:- https://github.com/redhat-openstack/website/pull/1270
15:13:23 <ykarel> amoralej, jpena can you revisit ^^
15:14:01 <ykarel> moving to next topic
15:14:05 <ykarel> #topic [baha] tripleo upstrem logging authorization
15:14:18 <ykarel> https://github.com/rdo-infra/weirdo/blob/master/playbooks/logs-ci-centos.yml Wondering if auth method here is OK
15:14:19 <mjturek> o/
15:14:25 <ykarel> #chair mjturek
15:14:26 <openstack> Current chairs: amoralej baha jpena mjturek ykarel
15:14:31 <baha> So this one's just a quick question for anyone who might know!
15:15:13 <baha> mjturek and I are still digging on container build logging, we're wondering if the authentication method used there would work for our job - e.g. if api_key is an environment variable set up by jenkins or anything like that
15:15:41 <baha> We're also wondering if someone needs to set up a folder for us on the log server
15:17:26 <ykarel> so we are using that script to collect logs, so those param seems correct
15:17:50 <amoralej> api_key comes from an environment variable injected by secrets, iirc
15:18:09 <jpena> let me check it quickly, I remember seeing that before
15:19:13 <jpena> baha: so CICO_API_KEY is set as an env variable for the jenkins worker
15:19:30 <jpena> in ci.centos.org, it is set for rdo-ci-cloudslave01 to 05
15:19:48 <jpena> so if your job is running there, we'll be fine
15:20:18 <baha> It's on cloudslave04, so we should be good on that end! Thank you
15:20:22 <jpena> yep
15:20:33 <mjturek> jpena: so the job starts there but then grabs a power node from cico. The cico node would probably need it injected I think?
15:20:53 <mjturek> baha: maybe I'm misunderstanding?
15:21:16 <jpena> mjturek: no, it's needed to request the node from cico
15:21:25 <jpena> the cico node doesn't need the key
15:21:41 <mjturek> hmm okay just making sure
15:22:15 <baha> So the second half, then, is whether or not we need someone to make the base folder (using job name) for us
15:22:40 <baha> So that we can start pushing logs into it each run
15:23:05 <jpena> baha: I think it's not needed, the rsync part (https://github.com/rdo-infra/weirdo/blob/master/playbooks/logs-ci-centos.yml#L38-L45) should take care of it
15:23:52 <mjturek> awesome so seems like we just need to modify the script the playbook uses a bit and we should be good to go
15:23:54 <baha> Alright! Just wanted to make sure the job would have write access at the base level for that
15:24:07 <baha> Thank you =)
15:25:00 <ykarel> baha, anything else on this or shall we move
15:25:11 <baha> We should be good to move on!
15:25:20 <ykarel> okk Thanks
15:25:25 <ykarel> #topic Chair for next meeting
15:25:34 <ykarel> Any volunteer?
15:25:55 <jpena> I'll take it
15:26:08 <ykarel> #action jpena to chair next meeting
15:26:23 <ykarel> #topic Open Discussion
15:26:45 <ykarel> so bring any topic now
15:27:06 <phillw> o/
15:27:40 <phillw> Do you good people still run the Office Hour?
15:30:11 <ykarel> phillw, currently it's not running i think
15:30:25 <phillw> ok, thanks :)
15:30:39 <ykarel> but we are always here to answer queries
15:30:46 <ykarel> and on our mailing list
15:31:12 <phillw> I'll use both when I re-start with rdo in the coming weeks.
15:31:22 <ykarel> phillw, ack
15:32:26 <ykarel> any other topic, or we close
15:34:57 <ykarel> so let's end
15:35:14 <ykarel> #endmeeting