Anaconda wants to (has to?) use Cockpit Storage in place of blivet-gui. Cockpit Storage will be offered to users as an escape hatch to get their storage into shape so that Anaconda can then lay down the OS onto it.

Typical tasks are the initializing of a disk with a partition table and creating partitions in them for the various OS related mount points ("/", "/boot", "/var", "/home", etc). Other tasks might be the creation of a LVM2 volume group with logical volumes, the creation of a Stratis pool, or making iSCSI and NVMe drives available.

The exact interface between Anaconda and Cockpit Storage is still open (at least I think so). Anaconda might just find all the new block devices that have been created by Cockpit Storage, and run the appropriate "vgcreate", "cryptsetup", and "mkfs" commands on them the create the desired OS filesystems. Or Anaconda might expect to find fully formatted filesystems with mount point information and just untar the OS bits into them. Or something inbetween.

https://docs.google.com/document/d/191DKDA8JeS3ZpnNgWjC5NLJcOHwppzI2bQrJZMHCEHs/edit