Hello!
My name is Joe Doss and I want to help the Fedora Cloud SIG bring more frequent tested releases of Fedora Cloud it's user base. The goal of this project is to provide more frequent updates of Fedora Cloud to users on a set cadence or on a case per case basis for major security events.
One major pain point that Fedora Cloud currently faces is the fact that once a new Fedora release comes out, the cloud images are no longer updated over time. This brings a poor user experience if bugs that are fixed later on in the current release cycle but are painful on the first boot of a Fedora Cloud instance until the user updates the instance.
I reached out to Dusty Mabe and he agreed to mentor me on this project along with help from Kellin and Mohan.
The current ideas on the table for bringing this project to light are:
* Standardize and improve Fedora Cloud tests * Create a Fedora Cloud test day for these updates to help improve tests * Set a release cadence policy post Fedora Release * Set a security update policy for major security updates
We will create issues under pagure.io/cloud-sig and try to get this project rolling by Fedora 30 at the latest. Any comments or suggestions on this topic are very welcome.
Thanks! Joe
On Fri, Jun 15, 2018 at 10:21 PM, Joe Doss joe@solidadmin.com wrote:
Hello!
My name is Joe Doss and I want to help the Fedora Cloud SIG bring more frequent tested releases of Fedora Cloud it's user base. The goal of this project is to provide more frequent updates of Fedora Cloud to users on a set cadence or on a case per case basis for major security events.
One major pain point that Fedora Cloud currently faces is the fact that once a new Fedora release comes out, the cloud images are no longer updated over time. This brings a poor user experience if bugs that are fixed later on in the current release cycle but are painful on the first boot of a Fedora Cloud instance until the user updates the instance.
That's not entirely true, the cloud images are updated for major security events. They are also built every day [1]. The issue is to date there's not been a proper process in which they're updated/communicated etc. Over all I welcome what you generally propose.
I reached out to Dusty Mabe and he agreed to mentor me on this project along with help from Kellin and Mohan.
The current ideas on the table for bringing this project to light are:
- Standardize and improve Fedora Cloud tests
- Create a Fedora Cloud test day for these updates to help improve tests
- Set a release cadence policy post Fedora Release
- Set a security update policy for major security updates
We will create issues under pagure.io/cloud-sig and try to get this project rolling by Fedora 30 at the latest. Any comments or suggestions on this topic are very welcome.
On 06/18/2018 03:25 AM, Peter Robinson wrote:
On Fri, Jun 15, 2018 at 10:21 PM, Joe Doss joe@solidadmin.com wrote:
Hello!
One major pain point that Fedora Cloud currently faces is the fact that once a new Fedora release comes out, the cloud images are no longer updated over time. This brings a poor user experience if bugs that are fixed later on in the current release cycle but are painful on the first boot of a Fedora Cloud instance until the user updates the instance.
That's not entirely true, the cloud images are updated for major security events. They are also built every day [1]. The issue is to date there's not been a proper process in which they're updated/communicated etc. Over all I welcome what you generally propose.
Yeah we build images every night (I talked to Joe about it), but as far as I know we haven't "released" any updated images after GA, even for security issues, for some time.
Dusty
On 18 June 2018 at 09:21, Dusty Mabe dusty@dustymabe.com wrote:
On 06/18/2018 03:25 AM, Peter Robinson wrote:
On Fri, Jun 15, 2018 at 10:21 PM, Joe Doss joe@solidadmin.com wrote:
Hello!
One major pain point that Fedora Cloud currently faces is the fact that once a new Fedora release comes out, the cloud images are no longer updated over time. This brings a poor user experience if bugs that are fixed later on in the current release cycle but are painful on the first boot of a Fedora Cloud instance until the user updates the instance.
That's not entirely true, the cloud images are updated for major security events. They are also built every day [1]. The issue is to date there's not been a proper process in which they're updated/communicated etc. Over all I welcome what you generally propose.
Yeah we build images every night (I talked to Joe about it), but as far as I know we haven't "released" any updated images after GA, even for security issues, for some time.
Please define "release" as it can mean different things to different groups. If you ask QA you will get one definition. If you ask release engineering you will get a similar but slightly different one. And various other groups have their own what constitutes a release. Using the term in general leads to long threads where people are either in violent agreement or completely arguing past each other for a long time.
Dusty
cloud mailing list -- cloud@lists.fedoraproject.org To unsubscribe send an email to cloud-leave@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/cloud@lists.fedoraproject.org/...
On 06/18/2018 11:57 AM, Stephen John Smoogen wrote:
On 18 June 2018 at 09:21, Dusty Mabe dusty@dustymabe.com wrote:
On 06/18/2018 03:25 AM, Peter Robinson wrote:
On Fri, Jun 15, 2018 at 10:21 PM, Joe Doss joe@solidadmin.com wrote:
Hello!
One major pain point that Fedora Cloud currently faces is the fact that once a new Fedora release comes out, the cloud images are no longer updated over time. This brings a poor user experience if bugs that are fixed later on in the current release cycle but are painful on the first boot of a Fedora Cloud instance until the user updates the instance.
That's not entirely true, the cloud images are updated for major security events. They are also built every day [1]. The issue is to date there's not been a proper process in which they're updated/communicated etc. Over all I welcome what you generally propose.
Yeah we build images every night (I talked to Joe about it), but as far as I know we haven't "released" any updated images after GA, even for security issues, for some time.
Please define "release" as it can mean different things to different groups. If you ask QA you will get one definition. If you ask release engineering you will get a similar but slightly different one. And various other groups have their own what constitutes a release. Using the term in general leads to long threads where people are either in violent agreement or completely arguing past each other for a long time.
Release, meaning checksums are signed, content is on the mirrors, and the website links to it. At least that is what I think of in terms of a release from an end-user perspective.
Dusty
On 06/18/2018 02:25 AM, Peter Robinson wrote:
On Fri, Jun 15, 2018 at 10:21 PM, Joe Doss joe@solidadmin.com wrote:
Hello!
My name is Joe Doss and I want to help the Fedora Cloud SIG bring more frequent tested releases of Fedora Cloud it's user base. The goal of this project is to provide more frequent updates of Fedora Cloud to users on a set cadence or on a case per case basis for major security events.
One major pain point that Fedora Cloud currently faces is the fact that once a new Fedora release comes out, the cloud images are no longer updated over time. This brings a poor user experience if bugs that are fixed later on in the current release cycle but are painful on the first boot of a Fedora Cloud instance until the user updates the instance.
That's not entirely true, the cloud images are updated for major security events. They are also built every day [1]. The issue is to date there's not been a proper process in which they're updated/communicated etc. Over all I welcome what you generally propose.
Fair enough. I guess my major point here is these updated images are not the something that a user can consume on each of the supported cloud providers after the initial GA for the current Fedora release cycle without a bunch of manual work.
Having a release cadence for updating these official images will help users out a lot.
Joe
On Fri, Jun 15, 2018 at 04:21:49PM -0500, Joe Doss wrote:
My name is Joe Doss and I want to help the Fedora Cloud SIG bring more frequent tested releases of Fedora Cloud it's user base. The goal of this project is to provide more frequent updates of Fedora Cloud to users on a set cadence or on a case per case basis for major security events.
Hi Joe! This is awesome. It's something we've wanted for a long time but had no one really championing it, which is exactly what it needs.
I reached out to Dusty Mabe and he agreed to mentor me on this project along with help from Kellin and Mohan.
Awesome!
We will create issues under pagure.io/cloud-sig and try to get this project rolling by Fedora 30 at the latest. Any comments or suggestions on this topic are very welcome.
Yeah, there's one thing -- I really would like to see Fedora Cloud merged with Fedora Server for F29 (or at the latest, F30). That shouldn't block this plan in any way, though!
On 06/18/2018 07:39 AM, Matthew Miller wrote:
We will create issues under pagure.io/cloud-sig and try to get this project rolling by Fedora 30 at the latest. Any comments or suggestions on this topic are very welcome.
Yeah, there's one thing -- I really would like to see Fedora Cloud merged with Fedora Server for F29 (or at the latest, F30). That shouldn't block this plan in any way, though!
Cool! I don't really care where the cloud-sig moves to as a user as long as the cloud images continue to remain as trimmed down as they are now but with more frequent official releases for users to consume. I definitely want to be apart of that discussion if they plan is to move Fedora Cloud under Fedora Server's umbrella.
Joe
On Wed, Jun 20, 2018 at 10:33:35AM -0500, Joe Doss wrote:
Cool! I don't really care where the cloud-sig moves to as a user as long as the cloud images continue to remain as trimmed down as they are now but with more frequent official releases for users to consume. I definitely want to be apart of that discussion if they plan is to move Fedora Cloud under Fedora Server's umbrella.
Awesome. Are you, by any chance, going to be at Flock this summer?
Hi Joe,
Welcome!
I have been the QA contact for Cloud/Atomic test days for the past several releases, so I am here to help you set up any test days you might have in mind.
We are currently planning a F29 Beta Cloud/Atomic test day for October 1, as shown here: [0] [1]
Let me know what you're planning for a test day and I can help coordinate/set up QA presence and support.
Thanks,
Geoff Marr IRC: coremodule
[0] https://apps.fedoraproject.org/calendar/QA/2018/10/2/#_ [1] https://www.pagure.io/fedora-qa/issue/553
On Wed, Jun 20, 2018 at 9:43 AM, Matthew Miller mattdm@fedoraproject.org wrote:
On Wed, Jun 20, 2018 at 10:33:35AM -0500, Joe Doss wrote:
Cool! I don't really care where the cloud-sig moves to as a user as long as the cloud images continue to remain as trimmed down as they are now but with more frequent official releases for users to consume. I definitely want to be apart of that discussion if they plan is to move Fedora Cloud under Fedora Server's umbrella.
Awesome. Are you, by any chance, going to be at Flock this summer?
-- Matthew Miller mattdm@fedoraproject.org Fedora Project Leader _______________________________________________ cloud mailing list -- cloud@lists.fedoraproject.org To unsubscribe send an email to cloud-leave@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/cloud@lists. fedoraproject.org/message/PPPCDKJK42DNMM7AZNAISMVM2FT6ZAS7/
cloud@lists.stg.fedoraproject.org
-
Dusty Mabe -
Geoffrey Marr -
Joe Doss -
Matthew Miller -
Peter Robinson -
Stephen John Smoogen