Since storage type are supposed to represent the underlying technology
of disk templates, the storage type 'sharedfile' is superfluous, because
technically both disk templates 'file' and 'sharedfile' use the file system.
This will be of use when implementing the storage space reporting for
all disk templates.
Signed-off-by: Helga Velroyen <helgav@google.com>
Reviewed-by: Michele Tartara <mtarara@google.com>
ST_LVM_PV = "lvm-pv"
ST_LVM_VG = "lvm-vg"
ST_RADOS = "rados"
-ST_SHARED_FILE = "sharedfile"
VALID_STORAGE_TYPES = compat.UniqueFrozenset([
ST_BLOCK,
ST_LVM_PV,
ST_LVM_VG,
ST_RADOS,
- ST_SHARED_FILE,
])
# Storage fields
DT_FILE: ST_FILE,
DT_PLAIN: ST_LVM_VG,
DT_RBD: ST_RADOS,
- DT_SHARED_FILE: ST_SHARED_FILE,
+ DT_SHARED_FILE: ST_FILE,
}
# the set of network-mirrored disk templates
, ("StorageLvmPv", 'C.stLvmPv)
, ("StorageLvmVg", 'C.stLvmVg)
, ("StorageDiskless", 'C.stDiskless)
- , ("StorageSharedFile", 'C.stSharedFile)
, ("StorageBlock", 'C.stBlock)
, ("StorageRados", 'C.stRados)
, ("StorageExt", 'C.stExt)