To make BTRFS (or any new file-system) the default for a distribution
will be really hard.

My thought on the subject:

-1. IS IT STILL DESIRED TO MAKE BTRFS THE DEFAULT FILE-SYSTEM FOR
FEDORA AT SOME (yet unknown) POINT IN THE FUTURE?

0. DETERMINE A ROOT FILE-SYSTEM CRITERIA (AND/OR a DEFAULT FS CRITERIA)
   * Does it exists somewhere in written and consolidated form?

1. DETERMINE CURRENT BTRFS STATUS (F18 ONWARDS)
   * See below.

2. EVALUATE IF 'CURRENT BTRFS STATUS' MEETS 'ROOT|DEFAULT FILE-SYSTEM CRITERIA'

3. ANACONDA: DETERMINE WHICH BTRFS FEATURES WILL BE SUPPORTED
   * Which raid levels, data, metadata, subvol, etc. Maybe some
features will not be available or supported (either by a bug or by
design).

4. ANACONDA: DETERMINE WHICH BTRFS DEFAULTS WILL USED
   * DEFAULTS FOR AUTOMATIC PARTITIONING with SCHEME as BTRFS
   * DEFAULTS FOR MANUAL PARTITIONING with SCHEME as BTRFS
   >> currently (and correct me if i am wrong): STANDARD PARTITIONS:
for SWAP and /boot, / as btrfs

5. ANACONDA: HANDLE ALL BTRFS SIZE/FREE SPACE REQUIREMENTS
   * To be able to REJECT all Storage Configurations in which the
resulting btrfs file-system will be too small and either fail or hit a
known-bug/issue (which was declared non-blocker).


~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

1. DETERMINE CURRENT BTRFS STATUS (F18 ONWARDS)

A page similar to
http://qa.fedoraproject.org/blockerbugs/milestone/18/final/buglist
could be created to track 'BTRFS AS DEFAULT FS' status. Anybody
interested in BTRFS
as the default file-system for Fedora will be able to see at a glance
how is that
going. Bug-reports will be still filled against bugzilla.

Tackers:

* BTRFS_INSTALLER_SUPPORT
  Criteria TBD... (need input from Anaconda developers)
  DRAF: Any bug/issue that impacts the installer.

* FS_RELIABILITY
  Criteria TBD...
  DRAFT: Any bug in which the file-system behaves erratically or incorrectly.
  Data Loss and Data Corruption are the worst example.

* FS_PERFORMANCE
  Criteria TBD... (but as the name implies)
  DRAFT: Any bug that is NOT in FS_RELIABILITY in which the
file-system is performing 'correctly' but its performance is not ok.

* FS_MISC_ISSUES
  Criteria TBD...
  DRAFT: Any bug that is NOT in either FS_RELIABILITY nor
FS_PERFORMANCE. Also it must not be on BTRFS_INSTALLER_SUPPORT.

* BTRFS_ISSUES_QUEUE
  DRAFT: Anybody could mark any btrfs bug as blocking this. Then some
assigned people can classify this queue and put them into any of the
previous queues.



* BTRFS_FEATURE_MAP
  DRAFT: A link to another page in which all btrfs features and
possible configurations are rated: UNK | OK | ISSUE:MISC | ISSUE:PERF
| ISSUE:REL | ISSUE:INST
  Example: BTRFS vXX MIRROR on VIRTIO: ISSUE:REL (very drafty)
  The idea of this is that one could see at a glance, which subset of
features are the most problematic ones, and more.
  Something similar to: http://www.x.org/wiki/RadeonFeature

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

I know that it is a bit overkill, but maybe some subset of this could be done.

Cheers.
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

Reply via email to