15:35:00 <dustymabe> #startmeeting fedora_cloud_meeting
15:35:00 <zodbot> Meeting started Tue Apr 14 15:35:00 2020 UTC.
15:35:00 <zodbot> This meeting is logged and archived in a public location.
15:35:00 <zodbot> The chair is dustymabe. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:35:00 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
15:35:00 <zodbot> The meeting name has been set to 'fedora_cloud_meeting'
15:35:06 <dustymabe> #topic roll call
15:35:30 <cyberpear> .hello2
15:35:31 <zodbot> cyberpear: cyberpear 'James Cassell' <fedoraproject@cyberpear.com>
15:35:35 * dustymabe waves at otubo jdoss cyberpear
15:35:37 <otubo> .hello2
15:35:39 <zodbot> otubo: otubo 'Eduardo Otubo' <eterrell@redhat.com>
15:35:45 <jdoss> .hello2
15:35:46 <zodbot> jdoss: jdoss 'Joe Doss' <joe@solidadmin.com>
15:39:10 * jdoss waves
15:39:15 <dustymabe> how goes all?
15:39:16 <cyberpear> Candidate RC-1.2 I see just came out -- do we need to test it?
15:39:24 <dustymabe> cyberpear: that would be great!
15:39:45 <dustymabe> #topic testing candidate RC composes for F32
15:39:52 <dustymabe> #info Candidate RC-1.2 I see just came out
15:40:05 <dustymabe> any volunteers to help test the candidate compose that just came out
15:40:11 * cyberpear hates "too many channels" freenode limit
15:40:21 <cyberpear> if you can point me to the download link, I'll test on OpenStack
15:40:21 <dustymabe> wow what is that limit?
15:40:43 <fldu1> I can do the test
15:40:53 <cyberpear> not sure, but I went to join #fedora-qa and hit it
15:41:00 <dustymabe> fldu1: sweet - what platform are you on?
15:41:43 <dustymabe> cyberpear: I assume there is a test page for RC 1.2 where we can probably fill in some test results for the cloud image
15:42:20 <fldu1> dustymabe: kubernetes + kvm/qemu
15:42:30 <dustymabe> fldu1: sweet
15:42:51 <cyberpear> https://lists.fedoraproject.org/archives/list/test-announce@lists.fedoraproject.org/thread/ACAEQ6XTMJBKOIXHKPNLM7C4TEGLGZYH/
15:43:35 <cyberpear> https://fedoraproject.org/wiki/Test_Results:Fedora_32_RC_1.2_Cloud
15:44:49 <dustymabe> #link https://fedoraproject.org/wiki/Test_Results:Fedora_32_RC_1.2_Cloud
15:45:02 * cyberpear still can't find the download link
15:45:11 <dustymabe> ok cyberpear what platform do you use ?
15:45:37 <cyberpear> OpenStack Queens
15:46:18 <dustymabe> sweet - i can do AWS
15:46:25 <dustymabe> and we have fldu1 with qemu
15:46:28 <dustymabe> thanks fldu1
15:46:32 <dustymabe> otubo: can you do any testing
15:47:02 <otubo> dustymabe, I can try!
15:47:12 <otubo> (sorry multitasking)
15:47:32 <dustymabe> no worries
15:47:34 <cyberpear> but these are probably close enough? https://dl.fedoraproject.org/pub/fedora/linux/development/32/Cloud/x86_64/images/
15:48:15 <dustymabe> https://kojipkgs.fedoraproject.org/compose/32/Fedora-32-20200414.0/compose/Cloud/x86_64/images/
15:48:21 <dustymabe> those should be good ^^
15:48:38 <dustymabe> I can try to send a link to the mailing list with this information
15:48:56 <fldu1> dustymabe: could be cool yes
15:49:00 <cyberpear> (it was conspicuously absent for the test-announce@ message, or I couldn't find it in there)
15:50:49 <dustymabe> #topic open floor
15:51:14 <dustymabe> ok we can do open floor now - the relening/infra team are coming to our meeting in 10 minutes so we're going to wait for them for the next topic
15:51:19 <dustymabe> cc mboddu nirik ^^
15:52:03 <mboddu> Yeah, we are almost done with the other meeting
15:52:26 <dustymabe> anything for open floor anyone?
15:52:29 <cyberpear> did that blocker issue from last time get fixed?
15:52:51 <otubo> dustymabe, while we wait, I posted a new PR for those cloud-init CVEs.
15:53:03 <otubo> If anyone could take a look and review: https://src.fedoraproject.org/rpms/cloud-init/pull-request/8#
15:54:30 <dustymabe> otubo: thanks. those probably won't go into f32 for release day
15:54:32 <dustymabe> is that OK
15:55:20 <cyberpear> LGTM
15:55:43 <cyberpear> (but right, I don't think CVEs are ever release blocking)
15:55:57 * mboddu should just done with another meeting, need to run something, will be back in 2 min
15:56:52 * nirik also, getting coffee, back in a min
15:57:35 <otubo> dustymabe, cyberpear I think that's ok. Just a heads up for review :)
16:00:58 <mboddu> Okay, I am here
16:01:09 * jdoss waves at mboddu
16:01:15 <dustymabe> #topic periodic releases of Fedora Cloud images
16:01:18 * mboddu waves back at jdoss
16:01:35 <cyberpear> do we currently only do a GA release?
16:01:36 <dustymabe> mboddu: nirik do you have a link to the issue we'd like to discuss
16:01:53 * mboddu checks
16:02:16 <mboddu> .releng 9240
16:02:17 <zodbot> mboddu: Issue #9240: Update published Fedora 31 cloud images - releng - Pagure.io - https://pagure.io/releng/issue/9240
16:02:21 <mboddu> We could use this
16:03:35 <mboddu> dustymabe: ^
16:03:58 <dustymabe> mboddu: so what we'd need here is to have some release engineering scripts to periodically update things like we did for releasing atomic host every two weeks
16:04:12 <mboddu> dustymabe: Yes
16:04:15 <mboddu> But before that
16:04:25 <dustymabe> I think jdoss and a few others were interested in having releases more often as well
16:04:34 <mboddu> Have we decided on testing? Who is going to do that?
16:05:25 <dustymabe> so things would probably be manual at first but it would be really nice if we had automation
16:06:00 <nirik> well, doesn't openqa test these now?
16:06:01 <mboddu> Sure, I understand
16:06:08 <nirik> (since autocloud went away)
16:06:33 <nirik> also, we have fedimg... and... it would be nice to have something nicer. :)
16:06:57 <mboddu> dustymabe: https://openqa.fedoraproject.org/tests/overview?distri=fedora&version=31&build=Fedora-Cloud-31-20200414.0&groupid=1
16:07:05 <nirik> so would the script just figure out what changed and announce it? or does it do anything else?
16:07:18 <fldu1> newbie question: what is fedimg ?
16:07:40 <mboddu> fldu1: https://github.com/fedora-infra/fedimg it listens to message bus and uploads the images
16:08:15 <mboddu> dustymabe: Is fedimg not working?
16:09:00 <dustymabe> ok sorry all, was trying to multitask and it wasn't working
16:09:04 <dustymabe> this has my full attention now
16:09:31 <dustymabe> mboddu: it should be working, do you have any evidence that it isn't ?
16:09:43 <dustymabe> fldu1: fedimg is what uploads the images to AWS right now
16:10:22 <fldu1> dustymabe: seems cool, I wasn't aware of it, I'll have a look :)
16:10:23 <dustymabe> nirik: yes, it would be real nice to have something that was maintained
16:10:36 <nirik> side note ( and I know people probibly already know this), but man is it hard to use the official fedora images in aws... they are not easy to find at all. ;)
16:11:01 <dustymabe> mboddu: I ran a local script to scrape fedimg, I see images from 20200414 so I think it's working
16:11:16 <dustymabe> nirik: there's lots to improve, that's for sure
16:11:34 <nirik> yeah.
16:11:43 <dustymabe> ok so where are we? what's the current open question
16:12:17 <mboddu> I guess we can use openqa for testing
16:12:24 <nirik> I am not sure it fully makes sense to upload every one... why don't we just upload the ones that we are 'releasing' but I guess some people want the very latest daily
16:12:49 <dustymabe> nirik: we're uploading them unconditionally right now - which isn't the smartest thing
16:12:57 <mboddu> And I am confused, if fedimg is working then what is the release process we need to discuss?
16:13:05 <mboddu> dustymabe: ^^ I guess that answers that
16:13:12 <nirik> well, I guess IMHO we should look at the process we have now and an ideal process and try and make the one match the other? :)
16:13:17 <jdoss> Do we need to throw this through openqa? When we do testing, we grab the AMI, boot it, install Nginx and that is enough for us to give that AMI a green light with a basic MVP test.
16:14:17 <dustymabe> mboddu: for a release we need to, get some automated testing (preferably include clouds), copy files to a more permanent location, get them on some mirrors, update website
16:14:20 <nirik> well, before we had autocloud test it and if it passed it was uploaded.
16:14:40 <nirik> now there's openqa doing that same test... I guess the idea being we don't upload one that doesn't work
16:15:02 <mboddu> dustymabe: Okay, I get it
16:15:17 <mboddu> I get it now*
16:15:34 <dustymabe> mboddu: so that's mostly very similar to what we were doing for Atomic Host with the push twoweek atomic script
16:16:18 * nirik liked those release emails with details of changes... was nice
16:16:26 <mboddu> dustymabe: Right, so, releng can handle post testing part to websites(we can look at it but no promises)
16:16:50 <dustymabe> mboddu: so basically releng can handle:
16:16:59 <dustymabe> - copy files to a more permanent location
16:17:04 <dustymabe> - get them on some mirrors
16:17:11 <dustymabe> - update website
16:17:13 <dustymabe> ?
16:17:47 <mboddu> nirik: yeah, iirc, it was part of ostree command that generated the diff (ostree static-delta?)
16:18:17 <dustymabe> `rpm-ostree db diff oldcommit newcommit`
16:18:24 <dustymabe> shows the package diff between two commits
16:18:47 * nirik thinks all those 3 things are doable. would need to talk to websites folks about the last one tho
16:18:52 <mboddu> dustymabe: Websites is a maybe, but definitely can look
16:19:09 <mboddu> Yeah, what nirik said
16:19:38 <dustymabe> maybe we can rely on releng to reach out to websites team for us? I have to admit there aren't a lot of resources for doing this work
16:19:46 <dustymabe> anybody here have skills with frontent/websites ?
16:19:50 <dustymabe> frontend*
16:20:14 <mboddu> I am also considering /pub/alt/cloud/XX for the mirrors location
16:20:19 <dustymabe> +1
16:20:25 <dustymabe> mboddu: can I add one more item:
16:20:39 <dustymabe> - sending release email
16:20:51 <dustymabe> basically we follow a very similar model as we did for atomic host
16:21:05 <mboddu> As I think not everyone needs it, since they are available on cloud and hence I dont want to put in /pub/fedora{-secondary}
16:21:10 <mboddu> dustymabe: Sure
16:21:11 * nirik wonders if we could also do this same thing for containers, but I guess thats a bigger conversation
16:21:20 <dustymabe> true
16:21:26 <dustymabe> ok for the cloud WG
16:21:42 <mboddu> And I will contact the websites folks
16:22:13 <dustymabe> - running tests against qcow (openqa does qemu/kvm already)
16:22:17 * mboddu is *really* *really* not good with UI (I dont think I can emphasize it anymore :D)
16:22:28 <dustymabe> - uploading to AWS (other clouds in future)
16:22:34 <dustymabe> - running tests on clouds
16:22:57 <dustymabe> - promoting release candidates to 'released' status
16:23:20 <dustymabe> does that sound good for the cloud WG?
16:23:51 <mboddu> I *think* we can also perform "uploading to AWS" easily using fedimg, based on the docs, it should be as simple as "trigger_upload.py [-h] -u URL -c COMPOSE_ID [-p]"
16:24:12 <dustymabe> mboddu: right - it already happens, but I'm thinking we should get off of fedimg soon
16:24:19 <dustymabe> jdoss: was working on that
16:24:28 <nirik> fedimg is also aws specific I am pretty sure... (re: other clouds)
16:24:29 <mboddu> dustymabe: Okay
16:24:41 <dustymabe> jdoss: I'm thinking we should axe plume and just use ore directly in the future
16:25:09 <jdoss> ore?
16:25:37 <dustymabe> jdoss: it's part of mantle too, but is more focused on "you give me a file, I create you a disk image in X cloud"
16:25:56 <jdoss> I am OK with that. TBH I am OK with a bash script at this point.
16:26:03 <dustymabe> yep
16:26:06 <jdoss> or ansible, whatever.
16:26:34 <jdoss> start out with a MVP and then make it better if we need more.
16:27:38 <dustymabe> #info we agree we would all like to upload and release cloud images more often. releng has agreed to try to achieve the following items: 1) copy files to a more permanent location 2) get them on some mirrors 3) update website 4) sending release email. Cloud working group will try to do the following items: 1) uploading to clouds 2) running tests on clouds 3) promoting release candidates
16:27:40 <dustymabe> to 'released' status
16:27:43 * nirik nods. working is good. simple is good. Don't care beyond that
16:28:20 <dustymabe> i'll try to make tickets for those items
16:28:39 <dustymabe> can we just work in the cloud sig tracker or does releng want tickets in the releng tracker for those items?
16:29:20 <mboddu> Better releng tracker
16:29:56 <dustymabe> ok
16:30:11 <dustymabe> #action dustymabe to create tickets for the work related to releasing cloud images periodically
16:30:23 <dustymabe> #topic open floor 2
16:30:28 <dustymabe> anything before I close the meeting?
16:30:28 <mboddu> Thanks dustymabe
16:31:04 <cyberpear> The latest compose linked above seems to still have update-testing enabled
16:31:15 <cyberpear> (not sure if it's supposed to or not)
16:31:23 <cyberpear> but otherwise, it seems to work fine on OpenStack Queens
16:31:25 <dustymabe> cyberpear: i.e. when you dnf install xyz it still pulls packages from updates-testing
16:31:29 <cyberpear> yes
16:31:33 <dustymabe> mboddu: nirik ^^
16:31:39 <dustymabe> is that supposed to happen in the latest candidate RC?
16:32:09 <cyberpear> Got the image from https://download-ib01.fedoraproject.org/pub/fedora/linux/development/32/Cloud/x86_64/images/
16:32:09 <mboddu> cyberpear: Were you testing RC or a nightly?
16:32:11 <nirik> until there has been a compose with the fedora-repos update yes
16:32:21 <mboddu> Yeah, thats still nightly, which seems right
16:32:27 <dustymabe> cyberpear: can you try with the link I shared with you earlier?
16:32:30 <cyberpear> downloaded during this meeting
16:33:03 <mboddu> cyberpear: Try https://kojipkgs.fedoraproject.org/compose/32/Fedora-32-20200414.0/compose/Cloud/x86_64/images/
16:33:10 <mboddu> ^ is the RC compsoe
16:33:13 <cyberpear> okay, will test that one too
16:33:18 <dustymabe> thanks cyberpear
16:33:21 <dustymabe> #endmeeting