16:06:19 <zlopez> #startmeeting Infrastructure (2023-10-12)
16:06:19 <zodbot> Meeting started Thu Oct 19 16:06:19 2023 UTC.
16:06:19 <zodbot> This meeting is logged and archived in a public location.
16:06:19 <zodbot> The chair is zlopez. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions.
16:06:19 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
16:06:19 <zodbot> The meeting name has been set to 'infrastructure_(2023-10-12)'
16:06:19 <zlopez> #meetingname infrastructure
16:06:19 <zodbot> The meeting name has been set to 'infrastructure'
16:06:19 <zlopez> #chair nirik zlopez nb bodanel dtometzki jnsamyak lenkaseg patrikp
16:06:19 <zodbot> Current chairs: bodanel dtometzki jnsamyak lenkaseg nb nirik patrikp zlopez
16:06:19 <zlopez> #info Agenda is at: https://board.net/p/fedora-infra
16:06:19 <zlopez> #info About our team: https://docs.fedoraproject.org/en-US/cpe/
16:06:20 <zlopez> #info Fedora Infra documentation: https://docs.fedoraproject.org/en-US/infra
16:06:22 <zlopez> #topic namaste
16:07:19 <zlopez> hello everyone
16:07:29 <jednorozec> hello
16:07:30 <zlopez> Welcome to fedora infra meeting
16:07:34 <zlopez> .hello
16:07:34 <zodbot> zlopez: (hello <an alias, 1 argument>) -- Alias for "hellomynameis $1".
16:07:37 <zlopez> .hi
16:07:38 <zodbot> zlopez: Something blew up, please try again
16:07:41 <zodbot> zlopez: An error has occurred and has been logged. Please contact this bot's administrator for more information.
16:07:47 <jednorozec> heh
16:07:59 <jednorozec> .hello humaton
16:08:00 <zodbot> jednorozec: Something blew up, please try again
16:08:03 <zodbot> jednorozec: An error has occurred and has been logged. Please contact this bot's administrator for more information.
16:08:05 <zlopez> Oh no, I blew up zodbot
16:08:10 <jednorozec> me2
16:08:56 <zlopez> I'm not sure how you can reload it
16:09:30 <jednorozec> I have just the big hammer
16:09:40 <zlopez> I can restart it completely, but there is a way to reload it
16:10:04 <jednorozec> !topic is zodbot working?
16:10:10 <jednorozec> #topic is zodbot working?
16:10:11 <aheath1992> .hi
16:10:12 <zodbot> aheath1992: Something blew up, please try again
16:10:15 <zodbot> aheath1992: An error has occurred and has been logged. Please contact this bot's administrator for more information.
16:10:27 <zlopez> Let me restart it
16:10:46 <pcreech> poop... sorry guys, had an impromptu mental health day, and forgot to take care of this meeting.
16:11:18 <jednorozec> no worries we blew up zod bot for you :)
16:12:16 <zlopez> Hm, the service was dead
16:12:18 <zlopez> .hi
16:12:19 <zodbot> zlopez: Something blew up, please try again
16:12:21 <dtometzki> .hi
16:12:22 <zodbot> zlopez: An error has occurred and has been logged. Please contact this bot's administrator for more information.
16:12:25 <zodbot> dtometzki: Something blew up, please try again
16:12:28 <zodbot> dtometzki: An error has occurred and has been logged. Please contact this bot's administrator for more information.
16:12:43 <pcreech> Nice :D  and feel free to carry on without me, still taking care of some stuff
16:12:58 <dtometzki> .hi
16:12:59 <zodbot> dtometzki: Something blew up, please try again
16:13:05 <zodbot> dtometzki: An error has occurred and has been logged. Please contact this bot's administrator for more information.
16:13:07 <zlopez> pcreech: I will give you chair for next week :-D
16:13:19 <dtometzki> hello together
16:14:04 <zlopez> Sorry for late start
16:14:18 <pcreech> zlopez, works for me
16:14:37 <dtometzki> it is ok i was late too
16:15:37 <zlopez> I'm not sure what is happening with zodbot, I don't have admin rights for it, so I can't fix it
16:16:07 <zlopez> We can try the next meeting on matrix, the matrix zodbot is running fine
16:16:33 <zlopez> Let's continue with next topic
16:16:34 <jednorozec> anything in the logs?
16:16:34 <zlopez> #topic New folks introductions
16:16:34 <zlopez> #info This is a place where people who are interested in Fedora Infrastructure can introduce themselves
16:16:34 <zlopez> #info Getting Started Guide: https://fedoraproject.org/wiki/Infrastructure/GettingStarted
16:16:57 <zlopez> jednorozec: Invalid password for zodbot
16:18:13 <zlopez> Anyone new on the meeting?
16:19:13 <zodbot_> zlopez: [hellomynameis zlopez]
16:19:16 <zodbot_> dtometzki: [hellomynameis dtometzki]
16:19:19 <zodbot_> dtometzki: [hellomynameis dtometzki]
16:19:42 <zlopez> .hello
16:19:42 <zodbot> zlopez: (hello <an alias, 1 argument>) -- Alias for "hellomynameis $1".
16:19:46 <zlopez> .hi
16:19:47 <zodbot> zlopez: Something blew up, please try again
16:19:50 <zodbot> zlopez: An error has occurred and has been logged. Please contact this bot's administrator for more information.
16:19:51 <phsmoura> .hi
16:19:53 <zodbot> phsmoura: Something blew up, please try again
16:19:56 <zodbot> phsmoura: An error has occurred and has been logged. Please contact this bot's administrator for more information.
16:20:11 <zlopez> It's still broken
16:20:20 <zodbot_> zlopez: (hello <an alias, 1 argument>) -- Alias for "hellomynameis $1".
16:20:23 <zodbot_> zlopez: [hellomynameis zlopez]
16:20:26 <zodbot_> phsmoura: [hellomynameis phsmoura]
16:21:18 <zlopez> Let's continue
16:21:38 <zlopez> #topic Next chair
16:21:38 <zlopez> #info magic eight ball says:
16:21:38 <zlopez> #info chair 2023-10-19 pcreech
16:21:38 <zlopez> #info chair 2023-10-26 zlopez
16:21:38 <zlopez> #info chair 2023-11-02 ???
16:21:39 <zlopez> #info chair 2023-11-09 ???
16:22:04 <zlopez> I will give the next week to pcreech
16:22:38 <zlopez> #info chair 2023-10-26 pcreech
16:23:05 <zlopez> Anyone for November?
16:23:35 <jednorozec> I can do it
16:23:56 <zlopez> Which one?
16:24:38 <jednorozec> 02
16:24:41 <jednorozec> 02-11
16:24:48 <jednorozec> 11-02 that is
16:25:00 <zlopez> #info chair 2023-11-02 jednorozec
16:25:15 <zlopez> Anyone wants to take 2023-11-09
16:25:19 <zlopez> ?
16:27:29 <zlopez> Let's move on
16:27:31 <zlopez> #topic announcements and information
16:27:31 <zlopez> #info CPE Infra&Releng EU-hours team has a Monday through Thursday 30 minute meeting going through tickets at 0730 UTC in https://matrix.to/#/#meeting-3:fedoraproject.org
16:27:31 <zlopez> #info CPE Infra&Releng NA-hours team has a Monday through Thursday 30 minute meeting going through tickets at 1800 UTC in #fedora-meeting-3
16:27:31 <zlopez> #info Zodbot is now available on matrix
16:27:32 <zlopez> #info Fedora 39 final freeze in effect
16:27:40 <zlopez> Any other announcement
16:27:57 <zlopez> ?
16:31:15 <zlopez> It seems that there is none
16:31:26 <zlopez> Let's move to oncall then
16:31:32 <zlopez> #topic Oncall
16:31:32 <zlopez> #info https://fedoraproject.org/wiki/Infrastructure/Oncall
16:31:32 <zlopez> #info https://docs.fedoraproject.org/en-US/cpe/day_to_day_fedora/
16:31:45 <zlopez> #info dtometzki is on call from 2023-10-13 to 2023-10-19
16:31:45 <zlopez> #info pcreech is on call from 2023-10-20 to 2023-10-26
16:31:45 <zlopez> #info nirik is on call from 2023-10-27 to 2023-11-02
16:31:45 <zlopez> #info ??? is on call from 2023-11-03 to 2023-11-09
16:32:29 <jednorozec> I can take the oncall 11-03-11-09
16:32:38 <zlopez> It's yours :)
16:32:51 <zlopez> #info jednorozec is on call from 2023-11-03 to 2023-11-09
16:33:05 <zlopez> #info Summary of last week: (from current oncall )
16:33:20 <zlopez> dtometzki: the floor is yours
16:33:59 <dtometzki> there was no pings last week
16:34:42 <zlopez> It seems that this was quiet week
16:34:50 <dtometzki> yes
16:35:05 <zlopez> I will skip the monitoring discussion as nirik is not here this week
16:35:30 <zlopez> And we have a learning topic for today
16:35:36 <zlopez> #topic Learning topic
16:35:45 <zlopez> # info pungi intro/crash course [jednorozec] on 2023-10-?? and 2023-10-26
16:35:57 <jednorozec> weee
16:36:01 <jednorozec> I missed last week
16:36:15 <zlopez> Yes, we made the meeting shorter
16:36:33 <jednorozec> Sorry about that, had to unload some stuff at home.
16:36:41 <jednorozec> but I am here today
16:37:00 <jednorozec> Lets talk about pungi
16:38:04 <jednorozec> Pungi serves as a distribution compose tool responsible for creating release snapshots that encompass various release deliverables.
16:38:32 <jednorozec> These deliverables encompass items like installation trees, RPM packages, repodata, bootable ISOs, kickstart trees, anaconda images, and PXE boot images.
16:38:46 <jednorozec> Pungi is comprised of several distinct executables that share a common library.
16:39:08 <jednorozec> The primary entry point is the "pungi-koji" script, which loads the compose configuration and initiates the process.
16:39:30 <jednorozec> The compose process occurs in multiple phases, with each phase being responsible for generating specific artifacts on the storage disk and updating the overall compose object, which is passed through all the phases.
16:40:02 <jednorozec> More on phases: https://docs.pagure.org/pungi/phases.html
16:40:51 <jednorozec> Pungi itself does not handle the majority of the actual work. Instead, it delegates these tasks to separate executables. Pungi's role is to ensure that all the required commands are executed in the correct order with the appropriate arguments. It also manages the relocation of generated artifacts to their respective destinations.
16:41:27 <jednorozec> The name "pungi-koji" reflects the fact that many of these separate executables submit tasks to Koji, which is responsible for performing the actual work in a traceable and auditable manner. Unlike manually executing tasks in Koji, Pungi guarantees that all images are constructed from the same package set and produces deliverables that Koji cannot generate, such as YUM repositories and installer ISOs.
16:42:14 <jednorozec> Fedora has its pungi configuration files here https://pagure.io/pungi-fedora/tree/main
16:43:21 <jednorozec> the configuration for most of the artifacts is here https://pagure.io/pungi-fedora/blob/main/f/fedora.conf
16:43:58 <jednorozec> you can see that we have split some parts of the configuration file for general config https://pagure.io/pungi-fedora/blob/main/f/general.conf
16:45:33 <jednorozec> Each fedora release has its own branch with pungi configuration branched from rawhide at the branching point.
16:45:58 <jednorozec> some important parts of the conf file are tag useg to gather packages https://pagure.io/pungi-fedora/blob/main/f/fedora.conf#_38
16:46:48 <jednorozec> kickstart definition that is used for artifacts https://pagure.io/pungi-fedora/blob/main/f/fedora.conf#_200
16:47:47 <jednorozec> so are you following are there any questions?
16:48:18 <zlopez> I'm following you :-)
16:48:31 <zlopez> No questions from my side
16:49:20 <zlopez> The split of the configuration took some time, because it needed some changes in Bodhi from what I remember
16:49:32 <jednorozec> yup good job zlopez
16:49:45 <jednorozec> so
16:50:00 <jednorozec> we have the tag we want to use f40
16:50:11 <jednorozec> we have bunch of kickstarts pulled from our repo
16:50:19 <jednorozec> 
16:50:19 <jednorozec> {
16:50:19 <jednorozec> 'image-build': {
16:50:19 <jednorozec> 'format': [('raw-xz','raw.xz')],
16:50:19 <jednorozec> 'name': 'Fedora-KDE',
16:50:20 <jednorozec> 'kickstart': 'fedora-disk-kde.ks',
16:50:22 <jednorozec> 'distro': 'Fedora-30',
16:50:24 <jednorozec> 'disk_size': 18,
16:50:26 <jednorozec> 'arches': ['aarch64'],
16:50:28 <jednorozec> 'repo': 'Everything',
16:50:30 <jednorozec> 'install_tree_from': 'Everything',
16:50:32 <jednorozec> 'subvariant': 'KDE',
16:50:34 <jednorozec> 'failable': ['*'],
16:50:36 <jednorozec> }
16:50:38 <jednorozec> },
16:50:40 <jednorozec> soory if I broke your formatting
16:50:58 <jednorozec> this is definition of image build task in pungi.
16:51:34 <jednorozec> You can see the kickstart that is going to be used, arch repo
16:51:40 <jednorozec> anything weird?
16:52:50 <zlopez> Isn't this an old one?
16:52:54 <zlopez> Fedora-30
16:53:00 <jednorozec> right
16:53:19 <jednorozec> and look at this one
16:53:20 <jednorozec> {
16:53:20 <jednorozec> 'image-build': {
16:53:20 <jednorozec> 'format': [('vagrant-libvirt','vagrant-libvirt.box'), ('vagrant-virtualbox','vagrant-virtualbox.box')],
16:53:20 <jednorozec> 'name': 'Fedora-Scientific-Vagrant',
16:53:21 <jednorozec> 'kickstart': 'fedora-scientific-vagrant.ks',
16:53:23 <jednorozec> 'distro': 'Fedora-22',
16:53:25 <jednorozec> 'disk_size': 40,
16:53:27 <jednorozec> 'arches': ['x86_64'],
16:53:29 <jednorozec> 'repo': 'Everything',
16:53:31 <jednorozec> 'install_tree_from': 'Everything',
16:53:33 <jednorozec> 'subvariant': 'Scientific',
16:53:35 <jednorozec> 'failable': ['*'],
16:53:37 <jednorozec> },
16:53:39 <jednorozec> 'factory-parameters': {
16:53:41 <jednorozec> 'ova-option': 'vagrant_sync_directory=/home/vagrant/sync'
16:53:43 <jednorozec> }
16:53:45 <jednorozec> },
16:53:49 <jednorozec> even older right?
16:54:08 <zlopez> Do we still have Scientific subvariant?
16:54:28 <zlopez> And this is for vagrant box if I'm looking correctly
16:54:50 <jednorozec> that does not matter :) its a image build
16:55:11 <Southern_Gentlem> jednorozec, i have a couple of questions after you get done
16:56:18 <jednorozec> so the distro variable is the release when we switched to uefi on that platform
16:56:36 <jednorozec> it was a different release for different arches
16:57:05 <jednorozec> this is later on used to setup boot-loader in the correct way
16:57:11 <jednorozec> Southern_Gentlem, shoot
16:58:20 <jednorozec> we are closing to the the time of the meeting :/ not event 1/3 of the stuff. Lot of things to cover in pungi...
16:58:53 <zlopez> I have it planned for next week as well
16:59:18 <jednorozec> yup I subscribed to 2 parts
16:59:38 <jednorozec> But not sure what to cover because we will have to choose
17:00:06 <jednorozec> Probably the different phases that are there and how we use them
17:00:35 <zlopez> We are at the end of our time and there will be Go/No-go meeting happening now
17:00:41 <zlopez> Let me end it here
17:00:48 <zlopez> #endmeeting