14:03:07 <amoralej> #startmeeting RDO meeting - 2022-07-27 14:03:07 <opendevmeet> Meeting started Wed Jul 27 14:03:07 2022 UTC and is due to finish in 60 minutes. The chair is amoralej. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:03:07 <opendevmeet> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:03:07 <opendevmeet> The meeting name has been set to 'rdo_meeting___2022_07_27' 14:03:12 <amoralej> #topic roll call 14:03:14 <jcapitao[m]> o/ 14:03:18 <kkula> o/ 14:03:23 <amoralej> #chair jcapitao[m] kkula 14:03:23 <opendevmeet> Current chairs: amoralej jcapitao[m] kkula 14:03:36 <amoralej> add your topics to https://etherpad.opendev.org/p/RDO-Meeting if any 14:06:38 <rdogerrit> Alfredo Moralejo created config master: Add Karolina as maintainer for deps https://review.rdoproject.org/r/c/config/+/44242 14:06:50 <amoralej> ok, let's start with the first topic 14:07:07 <amoralej> #topic Status of dependencies automatic updates 14:07:19 <amoralej> jcapitao[m], i think you can summarize the status 14:07:28 <amoralej> as it has been a great progress in the last days 14:07:58 <jcapitao[m]> finally 14:08:22 <jcapitao[m]> so we're now using report-uc.py script to bump lower deps 14:08:59 <jcapitao[m]> for each package we send a distgit patch to bump it 14:09:13 <jcapitao[m]> if NVR not found in CBS 14:09:42 <jcapitao[m]> If the NVR is found we promote it directly in -testing 14:10:12 <jcapitao[m]> BUT we might change, as amoralej proposed this morning 14:10:20 <jcapitao[m]> to promote it to -candidate 14:10:52 <amoralej> actually, my proposal is 14:10:55 <jcapitao[m]> and let the bot to promote -candidate to -testing alongside RDO projects 14:10:55 <rdogerrit> Merged openstack/cinder-distgit train-rdo: Require websocket-client (for DataCore driver) https://review.rdoproject.org/r/c/openstack/cinder-distgit/+/44171 14:11:01 <amoralej> yeah, that 14:11:12 <amoralej> but note, that packages are automatically included in -candidate when built 14:11:22 <amoralej> so, no action is needed to get them into -candidate 14:11:33 <amoralej> so, once the review is merged 14:11:59 <amoralej> just wait for next periodic execution of promotion from candidate to -testing 14:12:14 <amoralej> actually, one option may be to do two different reviews 14:12:23 <jcapitao[m]> ah, much easier then 14:12:26 <amoralej> one for regular openstack packages, other separated only for deps 14:12:41 <amoralej> so, first run the script with -n, commit the changes 14:12:51 <amoralej> then run it again without -n, commit again 14:12:58 <amoralej> and then git review will send both 14:13:08 <jcapitao[m]> great ! 14:13:16 <jcapitao[m]> I like it 14:13:29 <jcapitao[m]> +1 14:13:32 <amoralej> althouth from CI 14:13:33 <amoralej> mmmm 14:13:47 <amoralej> second one would not include openstack updates 14:13:51 <amoralej> mmm 14:14:10 <amoralej> i'm not sure that's bad, in this case 14:14:29 <jcapitao[m]> why ? 14:14:40 <spotz_> just peeking in, not really ehre:) 14:14:48 <amoralej> why will not test it or while is not bad? 14:14:56 <amoralej> #chair spotz_ 14:14:56 <opendevmeet> Current chairs: amoralej jcapitao[m] kkula spotz_ 14:15:06 <amoralej> o/ :) 14:15:34 <jcapitao[m]> as the second one we'll have just the deps diff 14:15:43 <jcapitao[m]> why it might be bad ? 14:15:56 <amoralej> yes, so the ci jobs will run with promoted content + changed content in the review (only deps) 14:16:12 <amoralej> although it will actually be on top of the openstack packages update 14:16:22 <jcapitao[m]> ah ok 14:16:26 <amoralej> anyway, in this case 14:16:30 <amoralej> we are only doing it on master 14:16:40 <amoralej> on master we are not updating openstack packages 14:16:50 <amoralej> right? 14:17:00 <jcapitao[m]> right 14:17:00 <amoralej> so, effectively it will only do deps 14:17:05 <jcapitao[m]> only on master 14:17:05 <amoralej> yeah 14:17:26 <jcapitao[m]> right right 14:17:30 <amoralej> so, yeah, we can simply run it without -n in zed from candidate to testing 14:17:34 <amoralej> and that will be enough 14:17:36 <jcapitao[m]> no issues then 14:17:46 <amoralej> jcapitao[m], so, let me summarize 14:17:49 <jcapitao[m]> we'll just have to handle master differently 14:18:30 <amoralej> #info a job will automatically check for differences between upper-constraints and actual versions in dependencies repo for master release 14:19:21 <amoralej> #info if there is a new version in u-c which is in fedora, the job will propose to update it in RDO Deps deps/<project> distgit using fedora srpm 14:20:26 <amoralej> #info the existing automation will also propose to update dependencies which have been built to zed-testing 14:21:03 <amoralej> #info first execution of the automated depencencies updates has found 50 deps to update which were available in fedora 14:21:30 <amoralej> #info automatic updates can be found in https://review.rdoproject.org/r/q/topic:deps-uc-update 14:21:35 <amoralej> jcapitao[m], is that correct? 14:22:06 <jcapitao[m]> yes 14:22:10 <kkula> great job, jcapitao[m]! 14:22:27 <amoralej> yes, great job 14:22:55 <jcapitao[m]> thank you :) it took some time though 14:22:57 <amoralej> i think this will work much better that previous attempt event-based 14:23:19 <amoralej> btw, what if we inject automatically pyproject-rpm-macros ? 14:23:20 <amoralej> as br 14:23:43 <amoralej> look for br python3-devel, if it exist, add pyproject-rpm-macros ? 14:23:58 <amoralej> or look for any specific macro that we know that requires it 14:24:10 <amoralej> pyproject_buildrequires i.e. 14:24:21 <amoralej> well, that's different topic :) 14:24:35 <jcapitao[m]> yeah I was thinking of that earlier 14:24:55 <jcapitao[m]> while fixing failed jobs 14:25:01 <jcapitao[m]> yes we should 14:25:12 <amoralej> btw, i'm figuring out how to print the link to the cbs built task created by the cbs jobs 14:25:16 <jcapitao[m]> as many will fail in the future for same reason I'd say 14:25:27 <amoralej> in the review comments, to avoid going to logs 14:25:32 <amoralej> jcapitao[m], yes 14:25:52 <amoralej> actually, other option would be to introduce it in be buildroot by default 14:26:03 <amoralej> but it's better to maintain it as clean as possible 14:26:25 <jcapitao[m]> right, explicit > implicit 14:26:34 <amoralej> yep 14:27:04 <jcapitao[m]> putting the URL in patch comment ? 14:27:14 <amoralej> yes 14:27:42 <amoralej> using zuul_return 14:27:48 <jcapitao[m]> aah 14:27:51 <amoralej> i discovered that lastly 14:27:55 <amoralej> look at https://review.rdoproject.org/r/c/rdo-jobs/+/44236/1/playbooks/DLRN/rpmbuild.yaml 14:27:58 <jcapitao[m]> there is a zuul callback 14:28:03 <amoralej> https://review.rdoproject.org/r/c/puppet/puppet-stdlib-distgit/+/44237 14:28:07 <amoralej> see the comments there 14:28:23 <amoralej> i mean, that's not cbs build, just to check the functionality 14:28:34 <amoralej> This is a test message 2 with variable puppet/puppet-stdlib-distgit 14:28:38 <jcapitao[m]> great ! 14:28:41 <amoralej> ideally, add something like 14:29:19 <jcapitao[m]> yes let's add it, to ease troubleshooting 14:29:25 <amoralej> CBS task created by job deps-cbs-validate: https://cbs.centos.org/koji/taskinfo?taskID=2930496 14:29:32 <amoralej> just an example 14:29:46 <amoralej> that will save us some time 14:30:47 <jcapitao[m]> good idea, I'll propose a patch 14:30:58 <amoralej> i'm working on it, don't worry 14:31:10 <amoralej> i'm almost have it done 14:31:23 <amoralej> one last thing about deps 14:31:33 <amoralej> #link https://review.rdoproject.org/r/c/config/+/44242 14:31:44 <amoralej> i've proposed adding kkula as maintainer for deps 14:32:15 <amoralej> she has worked a lot on deps, so i think she knows everything about it :) 14:32:41 <amoralej> so, i think she deserves to have full rights on it 14:32:46 <amoralej> thanks kkula!! 14:32:59 <jcapitao[m]> yeah good job kkula ! 14:33:01 <jcapitao[m]> +2 14:33:30 <kkula> thank you:) thats very nice 14:34:19 <amoralej> you'll have superpowers now :) 14:34:50 <kkula> with great power comes great responsibility... 14:35:19 <amoralej> of course :) 14:35:45 <amoralej> you'll do it great 14:36:24 <amoralej> btw, you can +1 the review to explicit acceptance :) 14:36:41 <kkula> ok 14:37:17 <amoralej> i think that's it for today, wrt deps 14:37:21 <amoralej> am i missing something? 14:37:48 <rdogerrit> Dariusz proposed rdo-infra/ci-config master: Fetch info about jobs from ZUUL https://review.rdoproject.org/r/c/rdo-infra/ci-config/+/43303 14:37:48 <rdogerrit> Dariusz proposed rdo-infra/ci-config master: Reduce number of arguments provided to function https://review.rdoproject.org/r/c/rdo-infra/ci-config/+/43161 14:37:49 <rdogerrit> Dariusz proposed rdo-infra/ci-config master: Fetch jobs history at once https://review.rdoproject.org/r/c/rdo-infra/ci-config/+/43307 14:37:49 <rdogerrit> Dariusz proposed rdo-infra/ci-config master: Removed component option https://review.rdoproject.org/r/c/rdo-infra/ci-config/+/43338 14:38:02 <amoralej> i wonder how will it work on stable releases, jcapitao[m] it'd be easy to run it manualkly just to check how many deps would be updated in stable releases? 14:38:10 <amoralej> yoga or wallaby, i.e. 14:38:57 <jcapitao[m]> mmmh you mean just one shot ? 14:39:02 <jcapitao[m]> or periodically ? 14:39:29 <rdogerrit> Dariusz proposed rdo-infra/ci-config master: Fetch jobs history at once https://review.rdoproject.org/r/c/rdo-infra/ci-config/+/43307 14:39:32 <jcapitao[m]> I can test on yoga and wallaby yes 14:39:40 <jcapitao[m]> ah just one more thing 14:39:44 <rdogerrit> Merged deps/python-websocket-client c9s-zed-rdo: Update to 1.3.3 https://review.rdoproject.org/r/c/deps/python-websocket-client/+/44231 14:39:59 <jcapitao[m]> currently it's attached to requirements projec 14:40:15 <amoralej> jcapitao[m], just one shot 14:40:19 <amoralej> initially, at least 14:40:19 <jcapitao[m]> but we do nothing we requirements project now 14:40:31 <jcapitao[m]> maybe we should attach it to rdoinfo 14:40:32 <amoralej> ah, good point 14:40:52 <amoralej> mmm it doesn't use anything in the requirements, right? 14:41:01 <jcapitao[m]> nope 14:41:05 <amoralej> the report-uc always pulls the file from github? 14:41:09 <jcapitao[m]> before we were triggering as post commit 14:41:17 <jcapitao[m]> right 14:41:26 <amoralej> ok, let's move it to rdoinfo then 14:41:58 <jcapitao[m]> ok, I'll move it 14:41:59 <amoralej> we have a bunch of jobs running together in periodic pipeline, we may need to create a second periodic pipeline at a different time 14:42:05 <amoralej> but that's unrelated 14:42:12 <jcapitao[m]> good point 14:42:14 <amoralej> let's see if we have node failures 14:42:26 <jcapitao[m]> ack 14:43:58 <amoralej> ok, so that's it 14:44:14 <amoralej> moving to open floor 14:44:21 <amoralej> #topic open floor 14:44:26 <rdogerrit> Merged deps/python-ujson c9s-zed-rdo: Update to 5.4.0 https://review.rdoproject.org/r/c/deps/python-ujson/+/44229 14:44:33 <amoralej> volunteers to chair the next meeting? 14:45:06 <kkula> I can take 14:45:50 <amoralej> ok, it's added to the etherpad 14:45:53 <amoralej> thanks kkula 14:46:08 <amoralej> anything else you'd like to discuss? 14:46:39 <kkula> nothing from me 14:46:48 <jcapitao[m]> nothing either 14:47:03 <amoralej> review https://review.rdoproject.org/r/c/rdo-website/+/44123 if you have a chance 14:47:31 <amoralej> and https://review.rdoproject.org/r/c/rdo-website/+/44118 btw 14:48:33 <jcapitao[m]> I'll take a look 14:49:39 <rdogerrit> Dariusz proposed rdo-infra/ci-config master: Reduce number of arguments provided to function https://review.rdoproject.org/r/c/rdo-infra/ci-config/+/43161 14:49:39 <rdogerrit> Dariusz proposed rdo-infra/ci-config master: Fetch jobs history at once https://review.rdoproject.org/r/c/rdo-infra/ci-config/+/43307 14:49:40 <rdogerrit> Dariusz proposed rdo-infra/ci-config master: Removed component option https://review.rdoproject.org/r/c/rdo-infra/ci-config/+/43338 14:50:03 <amoralej> ah, and there is new PS of https://review.rdoproject.org/r/c/rdo-infra/releng/+/43723/ i'll review it today later 14:50:22 <amoralej> jcapitao[m], ^ we need to learn pandas btw :) 14:50:28 <kkula> yep, I applied you suggestions 14:50:56 <kkula> jcapitao[m], take a look when you will have time:) 14:50:59 <amoralej> you are proud of your new tool? :) 14:51:19 <amoralej> i think it's pretty cool 14:51:38 <kkula> is only backend now, I want it... alive! 14:52:15 <amoralej> you are much closer now :) 14:53:00 <jcapitao[m]> ah! good opportunity to understand pandas :) 14:53:09 <amoralej> it is, yep 14:53:15 <amoralej> i think we can close the meeting 14:53:34 <amoralej> thank you for joining, have a nice day 14:53:45 <amoralej> #endmeeting