Periodic Cloud Image Updates
by Joe Doss
Hey folks!
I was talking on IRC with Dusty and he said this topic would be good for
the mailing list. What would it take to get an updated cloud image
beyond the first image that comes out when a new version of Fedora ships?
Here is some end user context. My org uses Fedora Cloud in production
and we are working towards moving our developers to using Fedora for
their development environments. To do this we use Vagrant with the
Fedora 25 cloud image. We hit a pretty bad bug
(https://bugzilla.redhat.com/show_bug.cgi?id=1401561) with rpcbind which
would cause major work flow issues when bringing up their dev envs.
Even with an updated package using the current Fedora Cloud base users
most likely will still have a problem
(https://bugzilla.redhat.com/show_bug.cgi?id=1401561#c57 details out the
possible edge case) due to outdated selinux-policy packages on the base
image.
A periodic update to the base image would be a nice quality of life for
Fedora Cloud end users and help put blocker bugs, like the one I linked
above, in the past.
Thanks!
Joe
--
Joe Doss
joe(a)solidadmin.com
7 years, 2 months
[atomic-wg] Issue #138 `Produce updated cloud base images monthly`
by Dusty Mabe
dustymabe added a new comment to an issue you are following:
``
A few users have been requesting this as of late: [mail thread] (https://lists.fedoraproject.org/archives/list/cloud@lists.fedoraproject.o...)
@mattdm had some questions in [this mail](https://lists.fedoraproject.org/archives/list/cloud@lists.fedorapro... copying them here:
So, we are already _making_ these; you can see them at
https://apps.fedoraproject.org/autocloud/compose — they're currently
under a compose ID with "Atomic" in the name, but AIUI that's going to
be split out. (I was worried that these might not include updates, but
that's fixed.)
Let's make a list of what needs to happen... here's what I can think
of:
1. Decide if we are okay with the level of automated testing these are
getting, or if we need human testing, or if we need more automated
testing
2. If we need more automated tests, someone needs to sign up for that
3. If we need human testing, someone needs to sign up to write the
release criteria
4. And, someone would need to commit to doing the validation every
time.
4. Work with release engineering and infrastructure to adapt the Atomic
Host gating/release process for Cloud Base
5. Work with release engineering to get updated images to mirrors and
stuff
6. Someone needs to sign up to update the Vagrant Atlas index
7. Work with websites to update cloud.fedoraproject.org to also offer
updated images. (I'm thinking the page should default to the latest,
but there should be some way to "scroll back" all the way to the GA
releases.)
8. Decide if we want to switch Cloud Base entirely to this
automatic process and eschew release milestones
I'm sure I'm missing something -- what else should be added?
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/138
7 years, 2 months