Wednesday, 2023-05-31

rdogerritrdo-trunk rdo-trunk proposed rdoinfo master: Bump rdoinfo bobcat-uc tags to latest upper-constraints  https://review.rdoproject.org/r/c/rdoinfo/+/4874500:15
rdogerritrdo-trunk rdo-trunk proposed rdoinfo master: Promote CBS tags update for antelope-9s-testing  https://review.rdoproject.org/r/c/rdoinfo/+/4867200:19
tkajinamjcapitao[m], It seems I have to revert you changes which replaced Stdlib::* by Stdlib::Compat::*. They removed all Stdlib::Compat::* in puppetlabs-stdlib 9.0.0 . https://github.com/puppetlabs/puppetlabs-stdlib/commit/fcbd4267fd830982e86041599d4eb11c2072a94a03:45
tkajinamwondering if you saw any failures caused by Stdlib::Compat::* types when you submitted these changes.03:46
rdogerritChandan Kumar proposed rdo-jobs master: Replace zuul-worker with zuul user  https://review.rdoproject.org/r/c/rdo-jobs/+/4874606:29
*** amoralej|off is now known as amoralej06:39
jcapitao[m]tkajinam: arf, bad timing for my patches then06:57
jcapitao[m]I didn't notice issue on CI06:58
tkajinamhttps://review.opendev.org/c/openstack/puppet-openstack-integration/+/88456107:04
tkajinamjcapitao[m], this one attempts to bump puppet-sdblib and hitting the problem. RDO might hit this issue earlier if it pulls the latest stdlib instead of pinning it to the same version we use in upstream puppet ci07:05
amoralejwe can revert and pin puppet-stdlib in master if needed07:06
amoralejjcapitao[m], karolinku[m] may you review https://review.rdoproject.org/r/c/rdoinfo/+/48681 when you have a chance?07:07
tkajinamamoralej, I've proposed revert and an additional fix so the problem would be resolved soon (though it depends on reviews, of cause). Unless you face the problem and need to fix it urgently in RDO then we don't need that pin and probably can wait for a few days07:08
amoralejat least we got a promotion in master yesterday at least07:09
rdogerritJoel Capitao proposed rdoinfo master: Revert "Pin puppet-stdlib to last promoted commit"  https://review.rdoproject.org/r/c/rdoinfo/+/4874707:11
jcapitao[m]actually it was pinned in rdoinfo07:16
jcapitao[m]amoralej: merging https://review.rdoproject.org/r/c/rdoinfo/+/4868107:20
rdogerritMerged rdoinfo master: Add edpm-image-builder to RDO  https://review.rdoproject.org/r/c/rdoinfo/+/4868107:24
rdogerritrdo-trunk rdo-trunk proposed config master: Create project for edpm-image-builder  https://review.rdoproject.org/r/c/config/+/4874807:27
rdogerritrdo-trunk rdo-trunk proposed config master: Create project info for edpm-image-builder in RDO  https://review.rdoproject.org/r/c/config/+/4874907:27
rdogerritrdo-trunk rdo-trunk proposed config master: Add Zuul definitions for edpm-image-builder  https://review.rdoproject.org/r/c/config/+/4875007:27
rdogerritJoel Capitao proposed config master: Create project for edpm-image-builder  https://review.rdoproject.org/r/c/config/+/4874807:40
rdogerritMerged config master: Create project for edpm-image-builder  https://review.rdoproject.org/r/c/config/+/4874808:44
rdogerritMerged rdoinfo master: Bump rdoinfo bobcat-uc tags to latest upper-constraints  https://review.rdoproject.org/r/c/rdoinfo/+/4874508:50
rdogerritAlfredo Moralejo proposed config master: Create project info for edpm-image-builder in RDO  https://review.rdoproject.org/r/c/config/+/4874909:05
rdogerritAlfredo Moralejo proposed nfvinfo master: Add first build for ovn23.03  https://review.rdoproject.org/r/c/nfvinfo/+/4875109:17
rdogerritMerged config master: Create project info for edpm-image-builder in RDO  https://review.rdoproject.org/r/c/config/+/4874909:18
rdogerritJoel Capitao proposed config master: Add Zuul definitions for edpm-image-builder  https://review.rdoproject.org/r/c/config/+/4875009:19
rdogerritJoel Capitao proposed config master: Add Zuul definitions for edpm-image-builder  https://review.rdoproject.org/r/c/config/+/4875009:20
rdogerritMerged nfvinfo master: Add first build for ovn23.03  https://review.rdoproject.org/r/c/nfvinfo/+/4875109:44
rdogerritMerged config master: Add Zuul definitions for edpm-image-builder  https://review.rdoproject.org/r/c/config/+/4875009:50
rdogerritAlfredo Moralejo proposed nfvinfo master: Publish first build for ovn23.03  https://review.rdoproject.org/r/c/nfvinfo/+/4875209:53
rdogerritMerged nfvinfo master: Publish first build for ovn23.03  https://review.rdoproject.org/r/c/nfvinfo/+/4875210:37
rdogerritAlfredo Moralejo proposed openstack/edpm-image-builder-distgit rpm-master: WIP Initial spec for edpm-image-builder  https://review.rdoproject.org/r/c/openstack/edpm-image-builder-distgit/+/4875310:52
rdogerritKarolina Kula proposed deps/python-virtualenv c9s-bobcat-rdo: Update to 20.21.0  https://review.rdoproject.org/r/c/deps/python-virtualenv/+/4816011:25
rdogerritJoan Francesc Gilabert proposed rdo-jobs master: [DNM] [WIP] Add network isolation to adoption standalone env  https://review.rdoproject.org/r/c/rdo-jobs/+/4875411:43
*** amoralej is now known as amoralej|lunch12:08
rdogerritMarios Andreou proposed rdo-jobs master: WIP switching to ci-framework install_yamls role  https://review.rdoproject.org/r/c/rdo-jobs/+/4851412:29
rdogerritJoan Francesc Gilabert proposed rdo-jobs master: [DNM] [WIP] Add network isolation to adoption standalone env  https://review.rdoproject.org/r/c/rdo-jobs/+/4875412:32
rdogerritJoan Francesc Gilabert proposed rdo-jobs master: [DNM] [WIP] Add network isolation to adoption standalone env  https://review.rdoproject.org/r/c/rdo-jobs/+/4875412:40
rdogerritJoan Francesc Gilabert proposed rdo-jobs master: [DNM] [WIP] Add network isolation to adoption standalone env  https://review.rdoproject.org/r/c/rdo-jobs/+/4875412:56
*** amoralej|lunch is now known as amoralej13:09
jcapitao[m]RDO meeting in less than 10 minutes, feel free to add your topics at https://etherpad.opendev.org/p/RDO-Meeting13:50
rdogerritAlfredo Moralejo proposed openstack/edpm-image-builder-distgit rpm-master: Initial spec for edpm-image-builder  https://review.rdoproject.org/r/c/openstack/edpm-image-builder-distgit/+/4875313:53
rdogerritJoan Francesc Gilabert proposed rdo-jobs master: [DNM] [WIP] Add network isolation to adoption standalone env  https://review.rdoproject.org/r/c/rdo-jobs/+/4875413:58
spotz_Meeting in 1 minute!13:59
amoralejo/14:00
spotz_o/14:00
jcapitao[m]#startmeeting RDO meeting - 2023-05-3114:02
opendevmeetMeeting started Wed May 31 14:02:00 2023 UTC and is due to finish in 60 minutes.  The chair is jcapitao[m]. 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_05_31'14:02
jcapitao[m]#topic roll call14:02
jcapitao[m]#chair amoralej spotz_ 14:02
opendevmeetCurrent chairs: amoralej jcapitao[m] spotz_14:02
karolinku[m]o/14:02
jcapitao[m]#chair karolinku 14:02
opendevmeetWarning: Nick not in channel: karolinku14:02
opendevmeetCurrent chairs: amoralej jcapitao[m] karolinku spotz_14:02
amoraleji think you need the [m] in karolinku[m] 14:03
jcapitao[m]#chair karolinku[m]14:04
opendevmeetCurrent chairs: amoralej jcapitao[m] karolinku karolinku[m] spotz_14:04
jcapitao[m]the autocompletion in my Matrix client hides the [m] 14:05
jcapitao[m]let's start with first topic :)14:07
jcapitao[m]#topic FIPS enabled C9S requires EMS in TLS negotiation to install software14:07
amoralejthat's mine14:08
amoralej#link https://issues.redhat.com/browse/RDO-12414:08
amoralejso, the summary is that a recent update in openssl in C9S has made that any fips enabled system can not install packages from repo servers without EMS negotiation14:09
amoralejwe have two cases related to RDO14:09
amoralejtrunk.rdoproject.org for RDO Trunk14:10
amoralejrepos.fedoraproject.org for rdo-release packages installing cloudsig repos14:10
amoralejfips jobs running in upstream projects have hit this issue, i could workaround in devstack but we need to look for a better way14:11
amoralejfor trunk.r.o, i couldn't find a way to enable EMS in https with mod_ssl in centos7, so unless we can find some way, i think the solution will come with trunk.r.o migration to a newer OS14:12
amoralejthat's something we need to work with the infra team, i already discussed with apevec , but i guess it will take some time and planification14:12
amoralejwrt repos.fedoraproject.org i think that the best we can do is to move those packages to some other place, as that's server is mainly an obsolete infra14:13
jcapitao[m]and it's out of our control also14:14
apevecyep, infra team will include this into backlog14:14
apevecjust wondering, do we really need that machine?14:14
jcapitao[m]what was the reason to host rdo-release RPM on repos.fedoraproject.org ?14:15
apevecit started as backup in AWS when the old rdocloud was unreliable14:15
amoralejgiven that the url we use to install rdo-release is https://rdoproject.org/repos/rdo-release.el9.rpm my understanding is that we have some .htaccess to redirect the requests14:15
amoralejjcapitao[m], to be able to install it in non centos servers14:16
apevecah are we talking about trunk.r.o or repos.fpo?14:16
amoralejapevec, both, right now repos.fpo14:16
amoralejbut we can go back to trunk.r.o later14:16
apevecrepos.fpo is legacy14:16
apevecand we should just abandon it14:17
amoraleji think the best option is to simply ship those rpm from www.rdoproject.org itself14:17
amoralejas we already depend on it for the redirect14:17
jcapitao[m]yeah +114:17
amoralejwe may even maintain the same urls14:18
amoralejso, no impact for users14:18
apevecyep14:19
spotz_nice14:19
amoralejbth, i have no idea how is that configured, i don't see anything in rdo-website repo14:19
amoralejthat maintains any redirect or something14:20
apevecyeah I wonder how we manage that .htaccess 14:20
amoralejit may be in the ansible which maintains the webserver14:20
amoralejso any volunteer to dig on it? :)14:20
jcapitao[m]it rings me a bell14:20
jcapitao[m]I can work on it14:21
amoralejthanks jcapitao[m] 14:21
amoralej#action jcapitao will investigate on how to move rdo-release rpms to rdoproject.org server14:22
amoralejwrt trunk.r.o, back to apevec question14:22
amoraleji think having a separate server has two pros:14:23
amoralej1. having two servers able to serve repos in case one fails (i mean trunk-centos8.r.o and trunk.r.o)14:23
amoralej2. serving content and api is more critical that building so splitting both functions is useful so that we can do maintenances in the builder with no impact in the server14:24
amoralejalso in terms of avoiding the builder impacts in the server14:24
amoralejsaid this, we may move trunk.r.o to the same infra as trunk-centos814:25
amoralejalthough having different infra providers is also a good thing in terms of reliability14:25
jcapitao[m]makes sense14:27
jcapitao[m]the con is maintenance and cost :)14:27
spotz_Hey I can design us a totally redundant infrastructure but they are quite $$$$$:)14:28
amoralejyes14:28
amoralejcurrently, we have two systems in aws, i have no idea about cost14:29
amoralejsaid this, this is something to discuss with infra team14:29
amoralejthey are probably the best informed for this decission14:30
spotz_Yeah and the ones to maintain it14:30
jcapitao[m]right14:30
amoralejso, i think this is it about this topic14:31
jcapitao[m]ok thank you14:31
jcapitao[m]let's move to next topic14:31
jcapitao[m]#topic pyproject-macros POC14:31
karolinku[m]that's mine14:32
karolinku[m]you can find detailed etherpad here: https://review.rdoproject.org/etherpad/p/pyproject_macros_reqs_generations_POC14:32
karolinku[m]but tl;dr: we need both BR and Requirements to calculate proper order by dlrn, so we need a file (or other kind of input) with list of Total BR and Total Requirements. My hopes are to use rpmbuild to manage spec BR and pyproject macros to manage requirements from source code. Hopes are under verification now. 14:32
karolinku[m]if that works, then: yes, we could remove Requires  from spec14:33
karolinku[m]I mean - that's possible14:33
karolinku[m]but not BR's14:33
amoralejit'd be cool if we can get all the requirements without running rpmbuild, only by running macros14:33
karolinku[m]I don't think that's possible. In my glance example, there is BR which is not defined in source code14:34
karolinku[m]so it's not catched by macros14:34
amoralejbut those will need to be added as BuildRequires in the spec14:35
amoralejso we can parse the spec file without running rpmbuild14:35
amoralejmy point aginst running rpmbuild at that point is that it will be more difficult to integrate it in dlrn and would make it much slower14:36
karolinku[m]why slower?14:36
amoralejbecause it would need to run the rpmbuild command for each package at the beginning only to calculate the order, then order it, then build the packages14:37
karolinku[m]-br option is a quick way to  parse BRs from spec file, which skips phases of building binaries14:38
amoralejand at the end, iiuc, there is no big win of running rpmbuild vs finding the BRs in the spec file directly, or there is?14:38
karolinku[m]rpmbuild is understanding comditions, grep not14:39
amoralejand rpmspec ?14:39
karolinku[m]it is too14:40
karolinku[m]understans conditions too14:40
karolinku[m]It would be great to use just one tool, but at this moment i'm not sure how to encourage macros to produce nice output and parse BR from specs14:41
amoralejso if we don't use automated BRs, running with -br would be pretty fast but if we do automatic BRs, it takes some time to process14:41
amoralejlet's split in two, running macros from one side, and parsing spec in the other14:42
amoralejat the end we'd need to join both14:42
amoralejyep, one of the challenges is how to get a nice output from the macro14:43
amoralejbut, i guess it must be some way as it's what package build does14:43
amoralejwhen using macros14:44
amoralejit'd be good to check if those macros are doing something else apart from displaying in stdout14:44
karolinku[m]im afraid thats it can be installed "on the fly"14:44
amoralejmaybe it's able to write the spec or something14:44
karolinku[m]I mean: found missining BR -> install -> move to another BR check, but need to confirm, but looks like so14:45
amoraleji see, we need to confirm14:47
karolinku[m]what concerns me about macros: 14:47
karolinku[m]> _If pyproject.toml is not found, the macros automatically fall backs to using setuptools with configuration in setup.cfg/setup.py._14:47
karolinku[m]that's why im not sure if it looking at BR in spec14:48
amoralejactually that's what will happen in openstack packages14:48
amoralejbut setup.cfg/setup.py will load requirements from requirements.txt14:49
amoralejactually we can also look to use the tox option14:49
karolinku[m]yes, it will14:49
amoralejwhich is what we used in the glance review14:49
amoralejwell, at the end it will look for setup.cfg/setup.py14:49
karolinku[m]sure, but it is still not BR14:49
amoralejwdym?14:49
amoraleji'm not following you now14:50
karolinku[m]systemd in glance is this special kind of requirement, which is not mentioned in any requirement.txt file,  setup.cfg/setup.py or any other14:50
amoralejyeah, we will always need to consume that from the spec14:50
amoralejany non-python dep has to go from explicit BR in the spec14:50
amoralejcan't be automated14:51
amoralejtbh, in most cases those will not affect to the order, but in any case we need to have both automatic and explicit BRs into account14:51
karolinku[m]yes, that's why it is so importat  to not to cut out rpmbuild/rpmspec from the beginning, because we may be not able to parse spec BR with macros14:51
amoraleji'm not cutting rpmspec, only rpmbuild :)14:52
amoralejactually, we will not be able to parse spec br with macros14:52
amoralejbut tbh, that's the easy part imo14:53
amoralejactually, rpmbuild is an option, but i think it should be just a last resort14:53
jcapitao[m]that was a good discussion here14:55
jcapitao[m]I need to move to next and last topic because we have 5min left14:55
jcapitao[m]#topic openstack clients on EPEL914:56
amoralejwe can continue working about this after the mtg14:56
amoraleji mean pyproject macros14:57
jcapitao[m]yeah sure14:57
jcapitao[m]#info openstack clients and dependencies are being built currently14:57
jcapitao[m]you may have seen some BZ tickets operations14:57
amoralejthere still many packages pending to build ?14:58
jcapitao[m]I scripted all that and will handle them as low prio14:58
jcapitao[m]amoralej: yes, but huge effort has been produced since a year now to build packages on EPEL914:58
jcapitao[m]so now there are only more or less openstack packages to build14:59
amoralejok15:00
jcapitao[m]#topic next chair15:00
jcapitao[m]who's willing to chair next week ?15:00
amoraleji can take it15:01
jcapitao[m]#action amoralej will chair next week15:01
jcapitao[m]thank you15:02
jcapitao[m]#topic open floor15:02
jcapitao[m]if you have something to bring on before I close the mtg15:02
spotz[m]And remember next week is video15:03
jcapitao[m]right15:03
amoralejnothing from my side15:03
jcapitao[m]I'm going to close the mtg15:04
jcapitao[m]thank you all for joining15:04
jcapitao[m]#endmeeting15:05
opendevmeetMeeting ended Wed May 31 15:05:06 2023 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:05
opendevmeetMinutes:        https://meetings.opendev.org/meetings/rdo_meeting___2023_05_31/2023/rdo_meeting___2023_05_31.2023-05-31-14.02.html15:05
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/rdo_meeting___2023_05_31/2023/rdo_meeting___2023_05_31.2023-05-31-14.02.txt15:05
opendevmeetLog:            https://meetings.opendev.org/meetings/rdo_meeting___2023_05_31/2023/rdo_meeting___2023_05_31.2023-05-31-14.02.log.html15:05
spotz[m]Thanks all!15:05
rdogerritMerged rdo-website master: Add May 24 meeting  https://review.rdoproject.org/r/c/rdo-website/+/4871615:18
rdogerritJoel Capitao proposed rdo-website master: Add May 31 meeting  https://review.rdoproject.org/r/c/rdo-website/+/4875715:18
rdogerritJoan Francesc Gilabert proposed rdo-jobs master: [DNM] [WIP] Add network isolation to adoption standalone env  https://review.rdoproject.org/r/c/rdo-jobs/+/4875415:31
rdogerritAlfredo Moralejo proposed rdoinfo master: Tripleo removal from RDO Master  https://review.rdoproject.org/r/c/rdoinfo/+/4875815:40
rdogerritMerged rdo-infra/ansible-role-weirdo-puppet-openstack master: Symlink p-o-i repo to the path where it expects and set ZUUL_BRANCH  https://review.rdoproject.org/r/c/rdo-infra/ansible-role-weirdo-puppet-openstack/+/4211915:48
rdogerritLuigi Toscano proposed rdoinfo master: Revert "Roll-back glance-tempest-plugin to 0.2.0 on wallaby"  https://review.rdoproject.org/r/c/rdoinfo/+/4875915:53
rdogerritJoel Capitao proposed rdo-infra/weirdo master: WIP Add openstack ansible test  https://review.rdoproject.org/r/c/rdo-infra/weirdo/+/4876016:08
rdogerritJoel Capitao proposed rdo-infra/weirdo master: WIP Add openstack ansible test  https://review.rdoproject.org/r/c/rdo-infra/weirdo/+/4876016:28
rdogerritJoel Capitao proposed rdo-jobs master: WIP Add weirdo openstack-ansible scenario001  https://review.rdoproject.org/r/c/rdo-jobs/+/4876116:30
rdogerritJoel Capitao proposed rdo-jobs master: WIP Add weirdo openstack-ansible scenario001  https://review.rdoproject.org/r/c/rdo-jobs/+/4876116:37
*** amoralej is now known as amoralej|off16:43
rdogerritrdo-trunk rdo-trunk proposed openstack/neutron-distgit rpm-master: openstack-neutron: failed to build 3fc97633a0  https://review.rdoproject.org/r/c/openstack/neutron-distgit/+/4876319:48

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