Hi, we don't create the volumes directly. We send Nova one "create server" request, and Nova creates the disks as part of building the instance. The section of that request describing the disks (block_device_mapping_v2) has no field for a name or description, the upstream OpenStack API simply doesn't carry one.
Nova names them itself: blank data volumes become <instance-id>-blank-vol, and volumes built from an image or snapshot are left unnamed, which is why they show up blank in the list.
Log in to comment and vote
Comments1
Alin
Sep 10
Hi, we don't create the volumes directly. We send Nova one "create server" request, and Nova creates the disks as part of building the instance. The section of that request describing the disks (block_device_mapping_v2) has no field for a name or description, the upstream OpenStack API simply doesn't carry one.
Nova names them itself: blank data volumes become <instance-id>-blank-vol, and volumes built from an image or snapshot are left unnamed, which is why they show up blank in the list.