Conga Home > Conga Use Cases > | Cluster and Storage group Pages | Red Hat |
by Jim Parsons
Last Modified: $Date: 2006/03/06 21:48:04 $
Description: An admin wishes to incorporate one or more Physical Volumes into a Volume Group.
Goal Level: User Goal.
Actors: Administrator.
Trigger:An administrator wishes to add one or more physical volumes to a volume group.
Basic Path:
Success End Conditions: The volume group is named and created.
Alternative Paths:It is
possible within the underlying API for LVM to specify constraints on:
Exception Paths:
Failure End Conditions:
Preconditions:
Postconditions:
Sample Narrative:
Open Issues:
The commandline equivalent for this command is:
vgcreate volume_group_name /dev/hdb1 /dev/hdb2
The following is the complete list of options available for this operation:
vgcreate [-A|--autobackup {y|n}] [-d|--debug] [-h|--help] [-l|--maxlog-
icalvolumes MaxLogicalVolumes] [-p|--maxphysicalvolumes MaxPhysicalVol-
umes] [-s|--physicalextentsize PhysicalExtentSize[kKmMgGtT]] [-v|--ver-
bose] [--version] VolumeGroupName PhysicalVolumePath [PhysicalVol-
umePath...]
Another open issue for this use case is the difference between options available for changing the parameters for a VG after it has been created and activated, in terms of LVM1 vs. LVM2. For example, if a user is running LVM1, the UI must not offer the chance to change the max number of PVs for a VG. If running LVM2, this operation is allowed, however.