Meeting started at 2024-03-28 15:00:35 UTC

The Meeting name is 'fedora_cloud_meeting'

!hi

Neil Hanlon (neil) - he / him / his

!hi

Jeremy Cline (jcline) - he / him / his

though I don't think we really have to roll call any more. :)

!hi

Major Hayden (mhayden) - he / him / his

!hi

Dusty Mabe (dustymabe) - he / him / his

I’m double booked

!hi

Tomáš Hrčka (humaton) - he / him / his

dustymabe: we established that long pauses are okay.

:)

* @davdunc and Jeremy Cline to work on #399 Upload Images to Azure Marketplace * Neil Hanlon to provide details for building the test plan for images. * davdunc to add ELN definition and upload for the ELN team. * davdunc to build kiwi definition for kubevirt image * davdunc to build kiwi definition for Oracle image * davdunc to write the ansible uploader for the oracle images and register. * work with the kiwi community to include a definition for kubevirt.

!hi

Neal Gompa (ngompa) - he / him / his

so glad to see that.

okay so Jeremy has been handling the first action item pretty much solo . . . gratitude!

Matt Micene 👋

awesome to see you!

Jeremy Cline: i'd be interested in syncing with you on azure image uploading

👋 it took an embarassingly long time to realize the IRC bridge was dead :)

Jeremy Cline: would you like to repeat your update from the #cloud:fedoraproject.org chat this morning?

when I started to get around to it for us (for community galleries) it was a bit more complicated because of the way aarch64 images are required to be uploaded

maybe I was just confusing mysefl

dustymabe: sure, can do. Still needs a little tweaking for versioning and EOL stuff, but it's pretty close

maybe I was just confusing myself

us == FCOS

Jeremy Cline: just getting them there and registered is a good MVP.

Yeah, so I have https://pagure.io/cloud-image-uploader which listens to Koji build messages and runs an ansible playbook when it sees Azure images completed

:) the EOL we can handle later.

MVP = minimum viable product.

so it sounds like we need help integrating what you have into infra.

It still needs some documentation and I've not wired it up to listen to live messages, but replaying messages results in images being uploaded

awesome.

oh is this goint to replace fedimg?

how difficult would it be to extend to AWS and GCP images?

jednorozec: that's the plan.

especially given some of the wonkiness our AWS image uploads have right now

davdunc: we have several coreos apps that listen to messages and act.. but TBH Jeremy probably mentored me on those, so I think he probably knows how to implement it

Conan Kudo: it shouldn't be difficult at all.

hah. So glad he is working on it!

I don't know how much massaging needs to happen for those images, but it should be another if statement, a playbook to run, and whatever python needs to happen to setup things for the playbook

Matt Micene: welcome! 👏

exactly.

And then we need to plumb the ELN images in for Stephen Gallagher so users can have those too.

okay... this is awesome.

so then the action here is to complete the work with infra to get the Azure images published.

let me end that sentence with a question mark?

I don't think I will let you :)

:) you better!

if you know what's good for me. :)

I think I linked it before but just in case... for aws uploads this is what I hacked together: https://git.resf.org/sig_core/toolkit/src/branch/devel/sync/import-snapshot-publish-aws.sh

I think that is accurate. There's an infra meeting in an hour so maybe I can inquire during the open floor what I need to do to get it deployed.

(but i'd love to turn it into a playbook ;) )

let's do it!

if you need any assistance, I am sure that we can get someone in the #aws:ansible.com group to help us work out any kinks.

it's a workflow that I am sure that they want to support.

So Jeremy Cline is going to work with infra on getting the uploader into place.

we have work to be done together to support the EOL process in the context of Jeremy Cline's work.

we'll call that "deprecation"

then image retirement.

down the road (after all this work is done), we should start making a fedora cloud collection: https://pagure.io/fedora-cloud/fedoraproject.cloud-ansiblecollection

so that people can do things on their own without fedora infra stuff

yes! that's definitely the goal.

then we can have import and registration targets.

and some other use-cases, like configuring private repository mirrors and such.

and supporting Fedora Quality

this could be the collection that makes it possible

hmm, Dalton M and I did something ansible based around private repository mirrors before

probably worth talking to him about it and seeing whether we can do something interesting for the fedora cloud collection

make it public if you can/haven't already.

thanks.

it needs love to handle multiple arches and versions, but it's a good starting point

we can read them and figure out how to add that to the collection. :)

it even handles debuginfod :)

sounds like everything we have.

because I'm awesome like that :P

hehe

haha.

okay.

I also wrote roles for my personal stuff about deploying image build software

so we can bring that over to the collection eventually

thanks Conan Kudo !

what would be a good date for this?

if there are people around, we should schedule it within the next week

Neil Hanlon: yes.

nah but next week is good lol

okay... maybe thursday the 4th?

would that work for folks?

Works for me

I can make it work :)

I'm mostly bowing out as I'm busy with things, but I think we really only need a couple of folks to work with this

okay. same. I can make it wor.

the big new thing is the aarch64-for-all-the-things

Conan Kudo: you have done enough.

Thanks for making all of these new test case requirements necessary!

the fact that the plumbing for this even works is because you didn't sleep. :)

<3

okay.

Proposed: Cloud Test Day on April 4th?

are we agreed?

Anybody (besides Conan Kudo ) opposed?

mhayden Matt Micene any objections?

sounds good!

Awesome.

wait .. did i just oppose? i'm good with it!

(late ack)

hah.

Neil Hanlon: anything you think we can add to the test day, just dig in there.

I'm not opposed

I just am too tired.

understood Conan Kudo you are off the hook.

we will work on doing the testing and adding more testing to the testing because you made more images and more opportunity for users.

that. Genuinely: thank you.

okay. ticket updated.

If you find time Conan Kudo et. al. can you add what you think we should include in the test operations generally?

sure

which ticket?

I added the meeting flag to the ticket so we revisit it next week.

the test day one?

next meeting, I mean.

yea.

yes.

okay will do

🙏

we should add some cloud-init validations to the image testing.

speaking of cloud-init, i was trying to get the dhcpcd change into F40 but it turned out to be a more complex issue than i planned 🙃

:(

I hear you on that one.

only blocker is an SELinux denial, but that is going to be fixed in the next selinux-policy pkg

nice!

we also need to include the container images we just included in the kiwi definitions.

and I think that the dhcp option that mhayden is working on is a pretty important test case too.

indeedy

will need some help there for sure

also old issues, like nspawn support and the like.

I guess this is a bit of a separate topic, but it would be nice to have some automated testing for all the images that runs after each build

(or maybe that exists in some capacity somewhere?)

Jeremy Cline: Conan Kudo has been working on CI for the kiwi definitions.

we should include additional testing in the definitions for the images that he is producing and verifying.

every supported image is built in CI

Jeremy Cline: I think it's good to discuss here/now.

we just don't have any way to boot and test them in CI

err release-blocking image

the definitions support way more than what is release blocking

but we could add that as another [p,t]oddler with an outcome.

Yeah, that would be good. I was also thinking say, post uploading the image to a cloud, something goes and boots it and does stuff

yes, that is probably what we want

that's what the img-proof tool from SUSE does, and we should have a similar workflow

Is that something openqa could do? I assume so, but I've never fiddled with it

yea. if we can't adopt it (I don't think we can) we can learn from it.

it's like mash, it requires a bunch of stuff we don't package.

I don't believe so, Jeremy Cline

openqa _could_ do some of the work.

Are we okay building it as a container though? IIRC Fedora infra was more okay with running stuff that wasn't necessarily packaged with RPMs

aiui it can't schedule a job on a cloud--it can do remote agents but it expects to launch them in qemu. but yeah, it could do other tests for sure

but It would be better to validate in the environments that we are building the images to run in.

Neil Hanlon: that's in the works on openqa next, but it's not completed.

Are we okay building img-proof as a container though? IIRC Fedora infra was more okay with running stuff that wasn't necessarily packaged with RPMs

oh, nice! I didn't realize that :D

there is a lot of work going on to make it "cloud-enabled"

img-proof requires being hooked into obs's uploader system

which we don't have

Ah

I looked into potentially making it optional, but after how davdunc's discussion with the mash folks went, I didn't bother

that kinda makes it a learning platform for now.

Zuul could be a good option here, I think.. with the ability to gate releases on tests, e.g.

Well, if openqa is getting worked on to support cloudy things I imagine that's the direction we'd want to go

yea. mash would be better for us if it had a plugin architecture, but it doesn't.

Neil Hanlon can you explore.

?

yeah, i have some experience with it from the opendev projects. i can add it to the list

awesome!

okay.

let's leave this for now and go to open topic.

Thanks mhayden for all the work on the cloud-init dhcp action.

no problemooo

I noticed the Azure images are missing from the https://fedoraproject.org/cloud/download beta listings, anyone familiar with how that works? Otherwise I'll poke around https://gitlab.com/fedora/websites-apps/fedora-websites/cms/fedoraproject.org/ until I figure it out

Jeremy Cline: it's in the website code.

ask darknao to help you locate the fedora-messaging script and we can add them in.

i expect that the arm64 images for the new listings are also not showing up.

Need to add that as a requirement for new images.

it's an update to listener.

we need that in the tickets too.

I'll add a ticket for it.

that should be part of our test day activities too.

okay.

anything else? We are out of time.

I am going to call it here then. Thanks everyone for attending.

not from I.