F25 was the first time Atomic replaced Cloud as Fedora edition on https://getfedora.org. That means we don't have Atomic prerelease pages, so we need to write them/ Furthermore, Atomic never "released" prerelease images, but with F26 the cloud-WG apparently wants to produce them and get them into a prerelease page. See this specific ticket for more information: https://pagure.io/atomic-wg/issue/199
Atomic is not like the other releases, Atomic follows a 2-week release period. That means we will have F26 Atomic Alpha images around 21th or 28th of february, but as always there will no big release date image for atomic. That means we need to add this to our Atomic scripts, parse the images and checksum files and get them into the website. Same will happen for the AMI IDs. As always we just have not much time, but that has become a normal thing ;)
One example of the atomic images are:
We will most likely have new ones soon as we found an issue that we are fixing, but I can open a PR to make changes to new images when necessary.
Any updates here? Where do you plan to place and sync out the prerelease images? IIRC koji cleans up the builds after 2 weeks or so, but I might be wrong.
hey @robyduck - just got images building with a few updates in them so that we can now log in. I have a request into releng to create atomic images in a separate compose and store them in the location that we will use for the entirety of f26.
Until that ticket get's resolved we'll use the images from the branched compose. Here are the ones from last night:
Would you like me to open a PR with these links?
So are we really going with nightlies? If we link to koji images they will not be there forever, we have to make sure we won't have dead links at some point. Also, we need to know if we will have AMIs, if fedimg will care about these or if we should grab them and add them manually, as I expect ther will be no two week artifact for the F26 release cycle.
@dustymabe, and yeah: PRs are really welcome, I will be around only till friday, not sure how much time I will have after it and until release date.
yeah. nightlies is all we have right now until that ticket from releng get's implemented. The koji branched composes are around for a couple of weeks so we'll just keep it updated as we go. We do have AMIs for these images, although some of them are getting deleted right now because they aren't passing tests because of a bug that causes them to take a long time to boot up. Here are a few of the AMIs from last night's build:
Fedora-Atomic-26-20170321.n.0.x86_64 EC2 (us-east-1) ami-4a13a55c hvm gp2 Fedora-Atomic-26-20170321.n.0.x86_64 EC2 (us-east-1) ami-6015a376 hvm standard
ok, thanks
@dustymabe ok, so let's go with them, even if they are untested.
My understanding is, cloud-wg will not be able to provide 2-week-artifacts for prerelease images before F26 GA. So, we can delay this after F26 an go with more or less hard-coded links. Same for AMIs, where we have still the possibility to use a globalvar AMI section manually.
Do you have any solutions for when the koji builds will go away?
They are getting tested, just not by official RC process :).
I'm hoping we get releng to work on https://pagure.io/releng/issue/6713 soon so we will have 2-week-artifacts before F26 GA. You don't need to worry about this, though. I'll keep you updated on the status of that.
Not really. They hang around for a few weeks. I'll just send in a new PR with new images when we're ready if that works for you?
Works for me, but as temporary solution For the next release I would suggest to have a clear ''process'' fo Atomic (pre)releases, which fits the needs and is shared with releng, even for testing, deadlines, etc...
Thanks for keeping us up to date with that ;)
Fedora 26 Alpha has been released and we have an atomic prerelease page running.
Metadata Update from @robyduck: - Custom field blocking adjusted to 637 - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.