#702 F35 Change: Make btrfs the default file system for Fedora Cloud
Closed 2 months ago by pbokoc. Opened 2 years ago by bcotton.

This issue tracks the release note for the following Fedora Change:

https://fedoraproject.org/wiki/Changes/FedoraCloudBtrfsByDefault

If you own this change, please add additional information here that we should communicate to Fedora users. Specifically, please consider:

  • New features available because of this change - pick 2 or 3 that are important
  • Considerations for users of previous releases of Fedora (upgrade issues, format changes, etc.)
  • Links to any upstream Release Notes
  • If this helps Fedora be a superior environment for our target audiences, please explain how so that we can emphasize this.

Your notes to us do not need to be formally written. We will edit them and add details as needed. This is a way for you to ensure that we know what is critical about your change.

If you want to write this release note, then:

  • Assign this issue to yourself
  • Check the wiki page linked above, find out what the change is about
  • Determine whether the change actually made it into the release or not[0]
  • Write a draft release note using that information against the correct branch here, in Pagure. (or see below)
  • Get in touch with the contact person/people listed on the wiki page, either through IRC or e-mail, and ask them to check your draft for technical accuracy
  • Submit your Release Note as a PR to this repository.

Once you're done with the above, make sure to either commit the relnote to an appropriate section of the Release Notes book, or, if you're not familiar with Git, AsciiDoc, or whatever else, just add it to this issue as a comment and let pbokoc[1] know that you're done with this one and you'd like the note included. Be sure to do this at least one day before the final release (October 29 according to the current schedule). Also make sure to do this even for relnotes that haven't been checked by the change owner.

[0] You can do that by asking the change owner listed on the wiki page; alternatively you can infer it by checking the tracker bug (linked in Wiki) in Bugzilla and looking at its status; see bug comments for details. Ask someone on the mailing list or on IRC if you're not sure.
[1] In #fedora-docs on FreeNode (UTC+1 timezone, online mostly during the day on weekdays), or pbokoc @redhat.com if you can't get a hold of me on IRC.


Metadata Update from @chrismurphy:
- Issue assigned to chrismurphy

2 years ago

@chrismurphy Hi, are you still planning to write this one?

Yep, I wrote it up in a separate issue for cloud sig review. Since there are no nacks, let's go with that.
https://pagure.io/cloud-sig/issue/349

I'll just copy paste the whole thing into this issue.

In this release:

  • Reflink and snapshot support; overlayfs automatically will use reflinks for copy-up operations, making container operations more efficient and performant; it is an option to use the native Btrfs driver in-lieu of overlayfs;
  • Metadata and data integrity checking enabled by default, for every read;
  • Adds the ability to logically separate contents of the volume without dividing up the available space: currently Cloud edition images use the same subvolume layout as Fedora desktop variants. But it's straightforward to make adjustments post-install, and to enhance image creation tools;
  • Zstd compression is enabled out of the box;
  • All the features Btrfs has to offer are opt-in. They aren't in your way if you don't need them, but are there if you do, all under one command interface.
  • Using Fedora Cloud images on RHEL with libguestfs container (needs some minimal documentation to include in release notes and the feature page)
    https://src.fedoraproject.org/container/libguestfs

Future features:

  • More complete resource control picture by including IO isolation;
  • Performance improvements by extended CoW capabilities to package management;
  • Native fscrypt support: per directory and subvolume encryption;

Metadata Update from @bcotton:
- Issue set to the milestone: F35

2 years ago

Metadata Update from @pbokoc:
- Issue set to the milestone: None (was: F35)
- Issue status updated to: Closed (was: Open)

2 months ago

Login to comment on this ticket.

Metadata