Re: F35 Change: Make btrfs the default file system for Fedora Cloud (System-Wide Change proposal)

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

 



> Am 25.05.2021 um 21:56 schrieb Neal Gompa <ngompa13@xxxxxxxxx>:
> 
> On Tue, May 25, 2021 at 3:52 PM Peter Boy <pboy@xxxxxxxxxxxxx> wrote:
>> 
>> 
>> Am 25.05.2021 um 19:03 schrieb Ben Cotton <bcotton@xxxxxxxxxx>:
>> 
>> https://fedoraproject.org/wiki/Changes/FedoraCloudBtrfsByDefault
>> 
>> This includes the same subvolume layout that is used on the desktop
>> variants [[Changes/BtrfsByDefault|as introduced in Fedora Linux 33]],
>> as well as transparent Zstd compression
>> [[Changes/BtrfsTransparentCompression|as introduced in Fedora Linux
>> 34]].
>> 
>> 
>> 
>> Wonder why a cloud image would just have a special affinity for a desktop system. Who runs their desktop in the cloud?
>> 
>> And there is a reason why the partition layout of server and desktop differs.
>> 
>> 
> 
> The partition layout differed specifically to maximize available
> space.

As to my knowledge it’s not about space (there is no difference in this respect), it's about strikt separation of system and user data, containment in the event of a file system failure, and opportunities and simplification of recovery.  

...
> So the same model works totally fine for both desktop and
> server.

I myself lack the exact technical knowledge, but (all?) server and file system experts I hear consider just that a gross misconception. 


>> == Release Notes ==
>> 
>> The default file system on the cloud is now Btrfs, following the
>> desktop change in Fedora Linux 33. Fedora Server, IoT, and CoreOS are
>> still specifically excluded.
>> 
>> 
>> It wasn't long ago that the plan was to better align cloud and server.
> 
> That's still a goal, but Server Edition has more complex needs to
> address before we could do it there by default. Since the storage
> needs for Cloud Edition are tremendously simpler, we can do it here
> first and iterate on getting things to the point that we could propose
> it for Server Edition.

That’s fine for me. Practically, this means putting that plan on hold for the next 10 or so Fedora releases. 

For this time, we should come up with something else to easily set up a Fedora Server VM in Fedora Server as a transitional measure. Maybe the ARM disk image for SBC's would be a good starting point. This disk image already offers an almost perfect implementation of the structure and concept of Fedora Server Edition, at least much closer than the current Cloud Base disk image. Their composition script might be a good starting point if you leave off the hardware specific parts. 



_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux