Bug 1154443

Created attachment 948329 [details]
PNG image of desired partition table.

Description of problem:

The anaconda installer on the F21-alpha-1 installation DVD does not allow the user to perform custom partitioning across multiple drives.  Although it will properly recognize two different drives (in my case an SSD and an HDD) it will not allow the user to assign the partitions into user-defined partitions and volume groups on separate physical devices.  

Specifically, I am trying to perform an installation where the infrequently modified files (/boot and root partitions) exist on the SSD, and the frequently modified files (/var, swap, and /home) exist on the HDD.  Furthermore, I have a need to encrypt /var, swap and /home, as these partitions contain sensitive data, but I have no desire to encrypt /boot or root, as the data in these partitions is public and static in nature.

Anaconda will not allow the partititions to be configured in the desired fashion.  See attachment for a spreadsheet that lists all of the specifics of the desired partitioning scheme.

Version-Release number of selected component (if applicable):

F21-Alpha-1 KDE DVD iso

How reproducible:

Always

Steps to Reproduce:
1. attempt to configure partitions as listed in attachment
2.
3.

Actual results:

Anaconda won't allow the user to create a customized partitioning scheme:

1. The user is prevented from assigning the desired volume group to the desired physical device (SSD or HDD); instead, anaconda just assigns the vg to the last-scanned physical device.

2. The user is prevented from assigning partitions to the desired volume group; anaconda seems to insist on placing /var in the same volume group as /, regardless of whether the user wants this or not.

3. The user is prevented from changing the status of the encryption flag on a per-partition basis.

4. anaconda defaults to putting /boot on the last device that was selected, rather than allowing user to choose boot device.  This makes it impossible to select encryption for some partitions and not others.

5. when manually creating partitions, anaconda does not accept the user's last choice of a volume group name as the default value.  instead, anaconda scans the hard disk to obtain the vg name used on the previous install, and forces this as the default value, ignoring user input.  (this happens even when the volume group name on the physical devices was allegedly destroyed by secure erase.  see Bug 1154350.


Expected results:

Partitioning as desired

Additional info: