Wednesday, 2023-02-08

« Tuesday, 2023-02-07 Index Thursday, 2023-02-09 »
rdogerritrdo-trunk proposed rdoinfo master: Bump rdoinfo wallaby tags to latest upper-constraints  https://review.rdoproject.org/r/c/rdoinfo/+/4687900:21
rdogerritrdo-trunk created rdoinfo master: Promote CBS tags update for zed-9s-release  https://review.rdoproject.org/r/c/rdoinfo/+/4691400:23
rdogerritrdo-trunk proposed rdoinfo master: Promote CBS tags update for xena-8s-release  https://review.rdoproject.org/r/c/rdoinfo/+/4685300:28
rdogerritrdo-trunk created rdoinfo master: Promote CBS tags update for wallaby-8s-release  https://review.rdoproject.org/r/c/rdoinfo/+/4691500:30
rdogerritrdo-trunk created openstack/nova-distgit rpm-master: openstack-nova: failed to build 4f11257e97  https://review.rdoproject.org/r/c/openstack/nova-distgit/+/4691602:11
*** gce108_ is now known as gce10802:21
rdogerritMerged rdo-jobs master: Replace one sleep by proper oc wait call  https://review.rdoproject.org/r/c/rdo-jobs/+/4689403:43
rdogerritMerged rdo-jobs master: Get some more data out of the pods  https://review.rdoproject.org/r/c/rdo-jobs/+/4689603:43
rdogerritMerged rdo-jobs master: Gather some more logs from the EDPM node  https://review.rdoproject.org/r/c/rdo-jobs/+/4690603:44
rdogerritChandan Kumar proposed rdo-jobs master: Enable firewalld/nftables in EDPM jobs  https://review.rdoproject.org/r/c/rdo-jobs/+/4686803:45
rdogerritChandan Kumar proposed rdo-jobs master: Enable firewalld/nftables in EDPM jobs  https://review.rdoproject.org/r/c/rdo-jobs/+/4686803:47
*** rcastillo|rover is now known as rcastillo03:59
rdogerritMerged rdo-jobs master: Enable firewalld/nftables in EDPM jobs  https://review.rdoproject.org/r/c/rdo-jobs/+/4686804:44
*** ysandeep|out is now known as ysandeep05:12
*** blarnath is now known as d34dh0r5306:52
*** blarnath is now known as d34dh0r5307:02
rdogerritMerged rdoinfo master: Promote CBS tags update for zed-9s-release  https://review.rdoproject.org/r/c/rdoinfo/+/4691408:05
rdogerritMerged rdoinfo master: Promote CBS tags update for xena-8s-release  https://review.rdoproject.org/r/c/rdoinfo/+/4685308:10
rdogerritMerged openstack/designate-tempest-plugin-distgit xena-rdo: python-designate-tests-tempest-0.15.0-1  https://review.rdoproject.org/r/c/openstack/designate-tempest-plugin-distgit/+/4691108:21
rdogerritCédric Jeanneret created config master: Add cjeanner pub key to hosts  https://review.rdoproject.org/r/c/config/+/4691708:26
*** jpena|off is now known as jpena08:29
rdogerritJoel Capitao created rdoinfo master: Lock openstackclient for Wallaby  https://review.rdoproject.org/r/c/rdoinfo/+/4691808:35
rdogerritMerged config master: Add cjeanner pub key to hosts  https://review.rdoproject.org/r/c/config/+/4691708:37
*** amoralej|off is now known as amoralej08:40
rdogerritMerged rdoinfo master: Lock openstackclient for Wallaby  https://review.rdoproject.org/r/c/rdoinfo/+/4691809:13
rdogerritCédric Jeanneret proposed rdo-jobs master: Gather network data from hosts  https://review.rdoproject.org/r/c/rdo-jobs/+/4690809:23
*** ysandeep is now known as ysandeep|food09:27
rdogerritChandan Kumar created rdo-jobs master: Sync the role from install_yamls/pull/63  https://review.rdoproject.org/r/c/rdo-jobs/+/4691910:11
rdogerritCédric Jeanneret proposed rdo-jobs master: Gather network data from hosts  https://review.rdoproject.org/r/c/rdo-jobs/+/4690810:25
rdogerritMarios Andreou created config master: Add openstack-k8s-operators/data-plane-adoption to rdo github projects  https://review.rdoproject.org/r/c/config/+/4692010:37
rdogerritChandan Kumar proposed rdo-jobs master: Sync the role from install_yamls/pull/63  https://review.rdoproject.org/r/c/rdo-jobs/+/4691910:44
rdogerritMerged config master: Add openstack-k8s-operators/data-plane-adoption to rdo github projects  https://review.rdoproject.org/r/c/config/+/4692010:47
*** ysandeep|food is now known as ysandeep11:10
*** ysandeep is now known as ysandeep|ruck11:10
rdogerritChandan Kumar created rdo-jobs master: [DNM] install_yamls job  https://review.rdoproject.org/r/c/rdo-jobs/+/4692111:25
*** amoralej is now known as amoralej|lunch11:58
rdogerritMarios Andreou proposed rdo-jobs master: WIP adding job definition for data_plane_adoption job  https://review.rdoproject.org/r/c/rdo-jobs/+/4687712:11
*** blarnath is now known as d34dh0r5312:14
rdogerritMarios Andreou proposed rdo-jobs master: WIP adding job definition for data_plane_adoption job  https://review.rdoproject.org/r/c/rdo-jobs/+/4687712:19
rdogerritCédric Jeanneret proposed rdo-jobs master: Gather some more node data  https://review.rdoproject.org/r/c/rdo-jobs/+/4690812:22
rdogerritChandan Kumar proposed rdo-jobs master: Sync the role from install_yamls/pull/63  https://review.rdoproject.org/r/c/rdo-jobs/+/4691912:31
rdogerritChandan Kumar proposed rdo-jobs master: [DNM] install_yamls job  https://review.rdoproject.org/r/c/rdo-jobs/+/4692112:45
*** amoralej|lunch is now known as amoralej13:12
rdogerritCédric Jeanneret created rdo-jobs master: [DNM] Attempt at locking the firewall  https://review.rdoproject.org/r/c/rdo-jobs/+/4692413:29
amoralejrdo meeting is in 12 minutes, remember to add your topics to https://etherpad.opendev.org/p/RDO-Meeting13:48
*** dasm|off is now known as dasm|rover13:51
rdogerritCédric Jeanneret proposed rdo-jobs master: [DNM] Attempt at locking the firewall  https://review.rdoproject.org/r/c/rdo-jobs/+/4692414:01
amoralejmtg time14:01
amoralej#startmeeting RDO meeting - 2023-02-0814:02
opendevmeetMeeting started Wed Feb  8 14:02:01 2023 UTC and is due to finish in 60 minutes.  The chair is amoralej. Information about MeetBot at http://wiki.debian.org/MeetBot.14:02
opendevmeetUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:02
opendevmeetThe meeting name has been set to 'rdo_meeting___2023_02_08'14:02
amoralejo/14:02
amoralej#topic roll call14:02
jcapitao[m]o/14:02
amoralej#chair jcapitao[m] 14:02
opendevmeetCurrent chairs: amoralej jcapitao[m]14:02
karolinku[m]o/14:03
amoralej#chair karolinku[m] 14:04
opendevmeetCurrent chairs: amoralej jcapitao[m] karolinku[m]14:04
amoralejok, i'll start with the first topic14:05
amoralej#topic antelope is coming14:06
amoralej#link https://releases.openstack.org/antelope/schedule.html14:06
amoralej#info this week is final release for non-client libraries14:06
amoralej#info next week is requirements freeze14:07
amoralejso we are again in release prep cycle14:07
amoralejso it can be a good moment if you have any ideas about improvements or changes14:08
amoralejthis release we'll take some advantage on the changes done by jcapitao[m] 14:08
amoralejto consume release from rdoinfo instead of hardcoding14:08
amoralejin some jobs14:08
amoralejwe need to keep an eye on it14:09
jcapitao[m]yes indeed14:09
jcapitao[m]I'm trying to remind what we could improve14:09
karolinku[m]we can improve script for branching14:10
jcapitao[m]maybe the tools and scripts, to put them in a container toolbox14:10
jcapitao[m]and standardize the upgrade process14:11
amoralejok, let's go one by one14:11
amoralej1. improve script for branching, can you elaborate a bit more?14:12
karolinku[m]I think now its not even merged in repo14:12
amoralejyou mean the one to find out hashes to create distgit branches?14:13
karolinku[m]yes14:13
amoralejok, good14:13
karolinku[m]i can take care of this14:13
amoralejnice14:13
amoralejgood to have all the scripts in releng repo14:14
karolinku[m]I think we hae now possibility to list projects to branching14:14
karolinku[m]by rdopkg14:14
amoralej#action karolinku[m] will propose improvements on distgit branching automation14:14
amoralejmmm14:14
amoralejlike checking what's already branched and so on?14:15
amoralejcurrently we have rdopkg and scripts/tools in releng project, as rdo_projects script14:16
amoralejit'd be great to improve automation and see what fits where14:16
karolinku[m]i need to dig for it, I used it once - it is Joel's feature14:17
amoralejah, ok14:17
amoralejso nice14:17
amoralejnext one14:17
amoralej2. maybe the tools and scripts, to put them in a container toolbox14:17
amoralejinteresting14:17
jcapitao[m]mmh14:17
amoraleji had never thought about it, but it may be a good thing14:17
karolinku[m]what would be an advantage of such approach?14:18
amoralejhaving a container with all the tools we usually need properly ready14:18
jcapitao[m]yes in order to have all the tools in the user PATH14:18
amoralejin my case, at least, i don't have releng installed in my laptop14:18
jcapitao[m]without having to pip install them in virtualenv14:19
amoraleji create a virtualenv every time that i need it14:19
amoralejusually i do when a new release approaches14:19
amoralejso, having a container ready may be an advantadge14:19
*** tosky_ is now known as tosky14:19
karolinku[m]ah. right. I still have the same one14:19
amoralejwith all the scripts, variables file deployed etc...14:19
jcapitao[m]exactly14:20
amoralejwe'd have to map ssh config and keys from the host14:20
jcapitao[m]we should create a repo to host the Containerfile14:21
jcapitao[m]with Gerrit config etc14:21
amoralejso that we can send reviews, etc...14:21
jcapitao[m]and Zuul CI/CD jobs to build test and push it on Quay registry14:21
jcapitao[m]yeah all secrets mounted as volume14:21
amoralejexactly14:22
amoralejmy suggestion is to start by creating a Dockerfile that we can build and use14:22
amoralejwith instructions in README file14:22
amoralejonce we have that, we can automate building and pushing to a registry14:23
jcapitao[m]right, let's start with a MVP14:23
karolinku[m]i like it!14:23
jcapitao[m]I can take care of it :)14:23
jcapitao[m]I mean just the kick off14:24
amoralej#action jcapitao will create a rdo-tools container that we can use to simplify the reldel work14:24
amoralejgood :)14:24
amoralej3. and standardize the upgrade process14:25
amoralejwdym ?14:25
jcapitao[m]it's a followup of the container toolbox14:26
jcapitao[m]so, when we say "we need to branch the project"14:27
jcapitao[m]we'll tell someone (in doc for instance) to use that specific command14:27
jcapitao[m]which will do the job14:27
jcapitao[m]the specific command which is available in the toolbox14:28
jcapitao[m]in fact14:29
jcapitao[m]I was wondering whether we should document the process or not 14:29
jcapitao[m]but as the process is constantly evolving 14:30
amoralejsorry, i'm not following you14:31
amoralejyou mean the entire branch process, reqcheck, branching etc... in a command?14:31
karolinku[m]or you mean standarize entire release process?14:32
jcapitao[m]no no sorry14:32
jcapitao[m]yes the entire release process14:32
jcapitao[m]like a release roadmap14:32
jcapitao[m]to do this action, run this command14:33
jcapitao[m]for all the action during the release process14:33
jcapitao[m]of course we can't automatize/script all the actions14:33
amoralejso, your proposal is to standardize and document better the process14:33
amoralejright?14:34
jcapitao[m]yes somehow :)14:34
karolinku[m]good idea. its is gonna be my third release and the only thing I can relay on is our past jira/trello cards14:34
amoralejhow would you propose to implement it?14:35
amoralejdocs? tooling improvement?14:35
jcapitao[m]both14:36
karolinku[m]I would start from docs14:36
jcapitao[m]the doc describing the roadmap14:36
jcapitao[m]and tooling improvment in order to not put complex commands in doc14:37
jcapitao[m]complex command which might change in the future14:37
amoralejwe have an old and basic page14:38
amoralejit was like, high level workflow14:38
amoraleji understand you want something more detailed and easy to follow14:38
jcapitao[m]yes14:39
amoralejhttps://www.rdoproject.org/documentation/branching/14:39
amoralejok, so i think it'd be good to get feedback about it from karolinku[m] as the latest RDOer to arrive14:40
amoralejso probably a task for both :)14:40
amoralejis it ok?14:40
karolinku[m]as many feedback as you want :D14:41
amoralejmy mind is maybe too contaminated of the current workflow to think in something different :)14:41
jcapitao[m]good14:41
jcapitao[m]well me too :D14:41
amoralejless that me, i think :)14:41
karolinku[m]what I mean, that i dont think we do have any documantation about release at all14:41
jcapitao[m]for sure :)14:41
karolinku[m]like even high-level one14:42
amoralejwe could do a mtg about it once we have some ideas14:42
amoralej#action jcapitao[m] and karolinku[m] to document the workflow from new releases14:43
jcapitao[m]alright14:43
amoralejis it fine?14:43
jcapitao[m]yup14:43
amoralejanything else wrt antelope?14:43
karolinku[m]nope14:44
jcapitao[m]we're good I think14:44
amoraleji think we can wait until next week to create jira ticket etc... so that we have some time to consider changes14:44
amoralejbut we don't have much time, tbh, so let's start soon14:44
jcapitao[m]right14:45
amoralej#topic open floor14:45
amoralejany topic you want to discuss?14:46
amoralejkarolinku[m], you know if your talk in CentOS Connect is being published in youtube or somewhere?14:46
karolinku[m]yes, there is14:47
karolinku[m]https://www.youtube.com/watch?v=AOd0MJBm9ZM14:47
karolinku[m]i'm there about 1:32h14:48
amoralejbut that's the entire stream, you know if they plan to publish per-talk videos?¿14:48
karolinku[m]ah, I don't know14:48
amoraleji'm looking for the url with the right time to put a link :)14:51
amoralej#info you can see karolinku[m] presentation about RDO in CentOS Connect in https://youtu.be/AOd0MJBm9ZM?t=554314:52
amoralejyep, i think that works14:53
amoralejdid you get any feedback about RDO worthy to share?14:53
karolinku[m]I got feedback that rdoinfo idea (centralized info of all projects) is great14:54
amoralejgood14:55
amoralejok, if there are not other topics, i'll ask for volunteer to chair next week and close the mtg14:55
karolinku[m]I can take it14:55
amoralej#action karolinku[m] will chair next meeting14:55
amoralejok, i'm closing the meeting14:56
amoralejthanks both for joining!14:56
amoralej#endmeeting14:56
opendevmeetMeeting ended Wed Feb  8 14:56:39 2023 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:56
opendevmeetMinutes:        https://meetings.opendev.org/meetings/rdo_meeting___2023_02_08/2023/rdo_meeting___2023_02_08.2023-02-08-14.02.html14:56
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/rdo_meeting___2023_02_08/2023/rdo_meeting___2023_02_08.2023-02-08-14.02.txt14:56
opendevmeetLog:            https://meetings.opendev.org/meetings/rdo_meeting___2023_02_08/2023/rdo_meeting___2023_02_08.2023-02-08-14.02.log.html14:56
jcapitao[m]thanks for chairing !14:57
*** dasm|rover is now known as dasm|afk15:36
*** ysandeep|ruck is now known as ysandeep|out15:36
jcapitao[m]amoralej: https://review.rdoproject.org/r/c/deps/python-flask/+/46486 and https://review.rdoproject.org/r/c/deps/python-fixtures/+/46901 when you have a chance16:02
spotzSorry to have missed this morning I didn't get in until 2am16:03
Tengudpawlik: heya! what's the state of the rdo infra - especially zuul?16:18
dpawlikTengu: soon will be available16:32
Tenguok. Guess my tests will wait for tomorrow then :)16:32
dpawlikso far, we are facing with rate limit from GH ;/16:32
Tengu"yay" :)16:32
dpawlikTengu: easy, in almost half hour "they will unlock us"16:33
Tenguof course :)16:34
*** jpena is now known as jpena|off17:32
*** amoralej is now known as amoralej|off17:41
dpawlikTengu:arround?18:37
dpawlikdo you have any job  that will trigger zuul?18:37
dasm|afkdpawlik: if you're still in need of a job: https://review.rdoproject.org/r/c/testproject/+/4578119:15
jcapitao[m]spotz @_oftc_spotz:matrix.org: no worries !19:26
spotz:) I figured agenda lorbus and karolinku[m] at the least could chat about their talks:)19:27
*** dasm|afk is now known as dasm|offline22:05
« Tuesday, 2023-02-07 Index Thursday, 2023-02-09 »

Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!