[atomic-wg] Issue #231 `clarify meaning of "rolling" for future fedora atomic releases`

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



jberkus added a new comment to an issue you are following:
``
Dusty: 

You're thinking in terms of systems which are updated, individually, by hand.  This is not how people admin most systems anymore, and definitely not what Atomic is for.  Atomic is aimed at clouds of automatically managed systems, so any discussion of updates and upgrades and rebases needs to be in this context.   You really need to get the outdated paradigm out of your thinking.

As I see it, we have three choices:

1. we have one stream, and "upgrade" automatically takes you forward, even if you're consuming the "next" Fedora major release.

2. we require rebase for "major version" changes, and continue to support the ostree for the old version for some defined period of time.

3. We release a system where users' clouds break every 6 months requiring a manual intervention, and eventual migration to CoreOS, which actually supports cloud automation.

These are the realistic choices.  You don't get others.
``

To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/231
_______________________________________________
cloud mailing list -- cloud@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to cloud-leave@xxxxxxxxxxxxxxxxxxxxxxx




[Index of Archives]     [Fedora General Discussion]     [Older Fedora Users Archive]     [Fedora Advisory Board]     [Fedora Security]     [Fedora Devel Java]     [Fedora Legacy]     [Fedora Desktop]     [ATA RAID]     [Fedora Marketing]     [Fedora Mentors]     [Fedora Package Announce]     [Fedora Package Review]     [Fedora Music]     [Fedora Packaging]     [Centos]     [Fedora SELinux]     [Coolkey]     [Yum Users]     [Big List of Linux Books]     [Yosemite News]     [Linux Apps]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Asterisk PBX]

  Powered by Linux