15:00:24 #startmeeting RDO meeting - 2019-11-27 15:00:24 Meeting started Wed Nov 27 15:00:24 2019 UTC and is due to finish in 60 minutes. The chair is jpena. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:25 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:00:27 The meeting name has been set to 'rdo_meeting___2019_11_27' 15:00:41 o/ 15:00:42 Remember that you can add any last-minute topic to the agenda at https://etherpad.openstack.org/p/RDO-Meeting 15:00:45 #topic roll call 15:00:48 #chair amoralej 15:00:49 Current chairs: amoralej jpena 15:00:50 o/ 15:00:52 o/ 15:01:02 #chair leanderthal jcapitao 15:01:03 Current chairs: amoralej jcapitao jpena leanderthal 15:01:08 aw, shucks 15:01:10 o/ 15:01:23 #chair tosky 15:01:23 Current chairs: amoralej jcapitao jpena leanderthal tosky 15:04:04 let's start with the agenda 15:04:09 #topic CentOS8 Updates, still no ETA for centos8 buildroot in CBS. 15:04:38 amoralej: ^^ 15:05:02 #info projects started removing support for python2 15:05:34 pressure to move to centos8 is growing as some projects are not longer running with python2 15:05:57 and we still don't have buildroot for centos8 in cbs so we've started plan B 15:06:08 which is building dependencies in a copr 15:06:26 #info Started deps bootstrap in copr https://copr.fedorainfracloud.org/coprs/g/openstack-sig/centos8-deps 15:07:00 who is responsible for the buildroot? is there something i can do to follow up? 15:07:17 #info deps bootstrap is using latest fedora builds in f32 and enabling automatic dependencies in python to match fedora behavior 15:07:28 leanderthal, it's task for centos infra team 15:07:32 gotcha. 15:07:44 they report status in cbs meeting on mondays 15:07:45 amoralej, okay, i'll nudge 15:08:04 currently there is no ETA 15:08:14 ok 15:08:21 move forward on plan b and i'll nudge as well 15:08:28 ack 15:08:45 yeah, plan b is just temporary until we can start doing proper cbs builds 15:09:13 okay 15:09:50 but i expect it will help us to bootstrap a rdo trunk repo and bootstrap faster in cbs 15:10:03 that's it from my side 15:10:09 ack, moving on 15:10:13 #topic Meeting time update 15:10:44 so we got one more response in the email thread (thanks leanderthal!), that's a total of 5 people in favor of meeting one hour earlier 15:10:49 that's 14:00 UTC on Wednesdays 15:10:52 :-) 15:10:58 earlier? or later? 15:11:02 earlier 15:11:04 i'd LOVE earlier. 15:11:07 i can totally do earlier. 15:11:32 so an hour and eleven minutes ago? 15:11:36 it would've started? 15:11:39 rdo-trunk created openstack/kuryr-kubernetes-distgit rpm-master: openstack-kuryr-kubernetes: failed to build b56581c https://review.rdoproject.org/r/23857 15:11:41 ended eleven minutes ago? 15:11:41 yep 15:11:45 #YESSSSS 15:11:53 so, unless someone complains in the next few minutes, can we agree on that? 15:11:58 yuppers 15:12:07 let's give people a few minutes to reply here, though? 15:12:12 yes, just in case 15:12:16 exactly. 15:12:18 +1 15:12:21 +1 15:12:27 +1 15:12:38 tosky: I think you're the only one in the meeting who did not reply to the thread. Are you ok with having the RDO meeting 1 hour earlier? 15:13:23 so my only hesitation is that it'd be at 0600 for west coast united states. 15:13:30 but... we don't have anyone hard core over there? 15:13:36 jpena: I'm usually passively following anyway, and I'm around 15:13:46 the furthest over off the top of my head is in central us time zone. 15:13:51 tosky, nice 15:13:54 so I thought it was better to leave the decision to the people who follow more actively 15:13:57 but thanks for asking :) 15:14:42 also, for example, in china it'd be 2200 instead of 2300 15:14:55 it's a more manageable time for India, too 15:15:00 exactly. 15:16:44 alright, we have a deal 15:17:02 #agreed Meeting time moves to 14:00 UTC on Wednesdays (1 hour earlier than before) 15:17:23 #topic Questions about RDO CI/Software Factory 15:17:28 tosky: ^^ 15:18:07 so, during the Cinder PTG and now during the Virtual Cinder PTG, the issue of 3rd party CIs popped up 15:18:21 cinder has many of them, and several are struggling to switch to zuulv3 15:18:45 so I though about proposing the usage of software factory, because it's what I've seen used by you 15:19:42 now, I almost know nothing about it, and I may have looked more around, but the question is: do you have some documentation on the way you set up the RDO CI? Some guidelines, 15:19:48 some documents that could be shared 15:19:59 there's some documentation on https://www.softwarefactory-project.io/docs/3.3/operator/quickstart.html?highlight=third%20party#third-party-ci-quickstart 15:20:08 (don't worry about the ssl certificate, we'll solve that soon) 15:21:01 * tosky looking 15:22:48 those are the instructions for connecting the 3rd party CI; but before that, is the basic software factory documentation enough to set a "production" system? Is there some trick or issue you found and it's not documented? 15:23:04 tosky, so, iiuc you are proposing them to deploy their instances or sf to run it 15:23:06 right? 15:23:32 the basic documentation should be enough to deploy. Most of the tricks are in the user setup for review.opendev, and then all the zuul job setup 15:24:03 yes, the idea is to have the cinder team document something know to work for the 3rd party CIs 15:24:04 a basic setup is really 3-4 commands (install repo rpm, install sfconfig, edit yaml file, run sf-config) 15:24:26 they'll also need to configure nodepool 15:24:37 that's the thing about documentation :) 15:24:38 and to have a openstack tenant for it 15:25:00 I guess they can rely on the standard zuul documentatin for the nodepool part, or is there something that helps on the sf side? 15:25:31 i think it's quite standard nodepool config 15:25:59 there's documentation from the sf side to automate the setup. Basically, add the nodepool provider info (URL for cloud provider, user, password, tenant, etc) to the sfconfig.yaml file, and let the installer do its magic 15:26:56 tosky: feel free to ping me or tristanC for any details, we'd be happy to help 15:27:05 jpena: this one: https://www.softwarefactory-project.io/docs/3.3/operator/deployment.html#installation ? 15:27:19 right 15:27:47 I wrote a blog post some time ago with all details, but it was using an earlier version (with zuul v2 and jenkins) 15:27:49 do you prefer if we act as a filters, or can we unleash the 3rd party CI admins directly towards you and tristanC? :) 15:28:30 if you want to set up an initial guide, we'd be more than happy. After that, there's the #softwarefactory channel on Freenode where you can unleash the beast 15:28:50 perfect, thanks! 15:29:04 I will report this back to the cinder people and see how to move forward 15:29:27 no other questions for now 15:29:53 thanks tosky! 15:30:28 #topic Chair for next meeting 15:30:32 any volunteers? 15:31:02 I can totally do it now! with the earlier time, i'm online for the entirety! 15:31:17 #action leanderthal to chair the next meeting 15:31:19 thx :o) 15:31:36 #topic open floor 15:33:18 Any other topics to discuss? 15:34:16 tosky: we'd be happy to help you setup a third party ci, the doc is pretty light on that subject but you can start with https://softwarefactory-project.io/docs/operator/quickstart.html#third-party-ci-quickstart 15:35:40 all magic in the quickstart, that's good 15:40:14 Ronelle Landy proposed rdo-jobs master: DNM: Testing add_repos for component promotion https://review.rdoproject.org/r/23841 15:43:26 jpena, i think we're good for the meeting if you wanna close out 15:43:27 Merged rdoinfo master: Bump Ussuri to OVS/OVN 2.12 https://review.rdoproject.org/r/23355 15:43:32 yes, let's close 15:43:34 #endmeeting