15:01:04 <ykarel> #startmeeting RDO meeting - 2019-09-04
15:01:05 <openstack> Meeting started Wed Sep  4 15:01:04 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:06 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:01:08 <openstack> The meeting name has been set to 'rdo_meeting___2019_09_04'
15:01:19 <PagliaccisCloud> ٩( ᐛ )و
15:01:26 <jpena> o/
15:01:28 <ykarel> please add topic to agenda https://etherpad.openstack.org/p/RDO-Meeting
15:01:33 <ykarel> #chair jpena PagliaccisCloud
15:01:34 <openstack> Current chairs: PagliaccisCloud jpena ykarel
15:01:41 <rdogerrit> Rafael Folco proposed rdo-infra/ci-config master: [WIP] Staging promoter provisioning  https://review.rdoproject.org/r/21909
15:04:09 <rdogerrit> User marios proposed rdo-infra/ci-config master: WIP D N M create and push container manifest with ppc and amd64  https://review.rdoproject.org/r/22002
15:05:18 <ykarel> Ok let's start with known topics
15:05:28 <ykarel> [ssbarnea, jpena]: Proposed adding ansible 2.8 as default version to base job. Any concerns? Workaround availabel as anyone can define ansible-version: 2.7 if they want or need. - https://review.rdoproject.org/r/#/c/21996/
15:05:45 <ykarel> #topic Proposed adding ansible 2.8 as default version to base job. Any concerns?
15:05:46 <jpena> zbr: ^^
15:06:34 <zbr> jpena: based on my tests we should have no concerns. anyone of different ideas?
15:06:50 <ykarel> zbr, can u share what tests u did here also
15:06:58 <zbr> considering that we do have a documented workaround it should be very easy to patch, after.
15:07:40 <jpena> I created some reviews to test common jobs: https://review.rdoproject.org/r/21997, https://review.rdoproject.org/r/21998, https://review.rdoproject.org/r/22000, https://review.rdoproject.org/r/22001
15:07:54 <jpena> all worked fine, I haven't found any obvious issue
15:08:07 * ykarel looks
15:08:56 <ykarel> Ansible Version: 2.8.3
15:09:22 <zbr> ykarel: ci testing was limted to ovb but i run locally with 2.8
15:09:45 <ykarel> jpena, zbr isn't rhel8 job tested somewhere, as the patch specifically mentions rhel8 and python detection
15:09:59 <zbr> yes, see https://review.rdoproject.org/r/#/c/21918/
15:10:08 * ykarel looks
15:10:12 <zbr> you see rhel-8 there
15:11:09 <ykarel> zbr, ack, but i guess ansible_python_interpreter is set somewher in those jobs
15:11:30 <ykarel> i think u need to test without setting it, /me need to look more to those job defs
15:11:35 <zbr> ykarel: i can vet that 2.8 can properly detect python
15:11:55 <zbr> sshnaidm|ruck: ^ maybe you can confirm that too?
15:12:21 <zbr> i know because I used 2.8 locally since it was released, this being its major "selling point"
15:14:55 <ykarel> zbr, i think it works as i remember overcloud deploy in rhel8 runs with ansible 2.8 only and there is no python_interpreter set
15:15:11 <zbr> in fact that change was already workflowed few days ago but it failed to merge for random issues, 7 rechecks so far and still counting:D
15:15:35 <ykarel> hard luck :(
15:15:54 <sshnaidm|ruck> testing here w/o interpreter set: https://review.rdoproject.org/r/#/c/21892/
15:15:59 <sshnaidm|ruck> ykarel, zbr ^
15:16:08 <ykarel> sshnaidm|ruck, ack
15:17:00 <ykarel> ok so we agree to move zuul base jobs to ansible 2.8 once testing finishes
15:17:28 <ykarel> unless and until someone objects
15:18:07 <jpena> fwiw, upstream zuul is using 2.8 as a default, and we have not found any issues
15:18:20 <ykarel> ok good news
15:18:43 <ykarel> anything else to discuss with this topic, or we shall move to next
15:18:55 <jpena> let's move on
15:19:19 <ykarel> ack
15:19:31 <ykarel> #topic [ykarel]: CentOS8 and RDO Train
15:19:34 <ykarel> it's me
15:19:46 <ykarel> so couple of info
15:19:49 <ykarel> #info     CentOS8 RC Work is completed as per https://wiki.centos.org/About/Building_8, but we still don't have any ETA for it's release.
15:20:01 <ykarel> #info If it's released sooner we can start RDO preparation for CentOS8 and get Train released with CentOS8, if it's not released sooner it will be very difficult to get Train released with CentOS8. For now we have started with train preparation with CentOS7 only
15:21:05 <ykarel> so in short we don't have CentOS8 bit's ready for us to move RDO Train to it, so we need to wait
15:22:09 <ykarel> ok, it was just for info, let's move to next topic
15:22:21 <ykarel> i will update here once we have some more news
15:22:26 <ykarel> #topic Train release preparation update
15:23:01 <ykarel> centos7-train bootstrap has started
15:23:06 <ykarel> jpena, would u like to update ^^
15:23:11 <jpena> yep
15:23:32 <jpena> So we have started the centos7-train bootstrap process. For now, you can see its status at https://trunk.rdoproject.org/centos7-train-bootstrap/report.html
15:23:51 <jpena> we will need some more passes, the first one failed when stestr (a dependency) required cliff (an RDO Trunk package)
15:24:17 <zbr> re centos8: why we do not get access to a RC build? Why we have to wait like everyone else for a "release"? Asking because having a pre-release would allow to spot missing bits and fix them before the release.
15:24:17 <jpena> once that is fixed, I expect the builder to be in good shape by the end of the week, and we'll switch the URL to the usual one
15:25:33 <ykarel> jpena, nice
15:25:54 <ykarel> zbr|out, re. centos8 we have asked for RC images, and waiting for response from rbowen
15:26:27 <ykarel> yes if we have RC builds we can start preparation, but would need a release to get Train released over it
15:26:55 <jpena> in any case, we have a ton of dependencies to build, and also depend on other SIGs (Ceph, Virt...)
15:27:12 <ykarel> yup that's also true :(
15:28:06 <ykarel> and regarding Train preparation, one more update
15:28:12 <ykarel> #info non clients libraries are being released upstream this week, RDO prep started, status being tracked at https://review.rdoproject.org/etherpad/p/train-release-preparation
15:30:37 <ykarel> any queries on it, else we move to open floor
15:31:53 <ykarel> #topic chair for next meeting
15:31:58 <ykarel> any volunteer?
15:32:25 <jpena> I'll take it
15:32:36 <ykarel> Thanks
15:32:42 <ykarel> #action jpena to chair next week
15:32:57 <ykarel> #topic open floor
15:33:11 <ykarel> feel free to bring any topic now
15:34:16 <rdogerrit> Rafael Folco proposed rdo-infra/ci-config master: promotion staging zuul job  https://review.rdoproject.org/r/21873
15:34:50 <mjturek> ykarel: since it's a little quiet, can I point at your patch to restore ppc container builds? https://review.rdoproject.org/r/#/c/22083/
15:35:15 <mjturek> reviews appreciated, thanks if you already have
15:35:35 <ykarel> mjturek, yes let's wait for zuul, then we can get it merged
15:35:47 <mjturek> fair enough! :)
15:37:43 <rdogerrit> Zoltan Caplovic created rdo-infra/rdo-infra-playbooks master: Playbook for rcm-registry (rhos-rcn tenant)  https://review.rdoproject.org/r/22085
15:41:10 <ykarel> ok any other topic, or we close and everyone gets 20 minutes back
15:41:15 <ykarel> ?
15:41:48 * jpena votes for the 20 minutes
15:42:29 * ykarel don't see any objection to vote, so let's close
15:42:33 <ykarel> #endmeeting