show base image when creating a volume from an image

Bug #1333625 reported by Dafna Ron
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
python-cinderclient
Invalid
Undecided
Unassigned

Bug Description

I created several volumes from different images and could not remember which Image I used for each volume.
can we add a field that would should what was the image copied to the volume?

[root@puma31 ~(keystone_admin)]# cinder list
+--------------------------------------+-----------+--------------+------+-------------+----------+-------------+
| ID | Status | Display Name | Size | Volume Type | Bootable | Attached to |
+--------------------------------------+-----------+--------------+------+-------------+----------+-------------+
| 3d8c0b46-2d51-4b7d-a3f1-a3bc47c8ed4c | available | dafna1 | 20 | None | true | |
| 42efedc0-28c8-4973-9975-513c3d224b3e | error | rhel | 20 | None | false | |
| 7f53b701-16a4-4a4e-85bc-4e4dbc181ddd | error | dafna-admin | 4 | None | false | |
| b2a0950d-7edd-4e3d-8e94-51474942c191 | available | dafna | 20 | None | true | |
+--------------------------------------+-----------+--------------+------+-------------+----------+-------------+
[root@puma31 ~(keystone_admin)]# cinder show 42efedc0-28c8-4973-9975-513c3d224b3e
+--------------------------------+--------------------------------------+
| Property | Value |
+--------------------------------+--------------------------------------+
| attachments | [] |
| availability_zone | nova |
| bootable | false |
| created_at | 2014-06-23T15:32:29.000000 |
| display_description | None |
| display_name | rhel |
| encrypted | False |
| id | 42efedc0-28c8-4973-9975-513c3d224b3e |
| metadata | {} |
| os-vol-host-attr:host | puma31.scl.lab.tlv.redhat.com |
| os-vol-mig-status-attr:migstat | None |
| os-vol-mig-status-attr:name_id | None |
| os-vol-tenant-attr:tenant_id | a6fb16b9b32d4860bbc418b788bd6bea |
| size | 20 |
| snapshot_id | None |
| source_volid | None |
| status | error |
| volume_type | None |
+--------------------------------+--------------------------------------+

Changed in python-cinderclient:
assignee: nobody → chandankumar (chandankumar-093047)
Revision history for this message
Ritesh Paiboina (rsritesh) wrote :

Could you please elaborate more what is the objective here .

THank you

Revision history for this message
Dafna Ron (dron-3) wrote :

I am not sure I am following your question.
Having the src image info on a create disk would be best practice as it is information shown in many virtualization programs,
I am sure you will not ask an administrator to boot up every volume they have to locate a volume created from a specific image.

Revision history for this message
Sean McGinnis (sean-mcginnis) wrote : Owner Expired

Unassigning due to no activity.

Changed in python-cinderclient:
assignee: chandankumar (chandankumar-093047) → nobody
Revision history for this message
gundarapu kalyan reddy (gundarapu-reddy) wrote :

In the bug description you are executing cinder show command for a volume which is not bootable(no source image). Anyways the info about source image using cinder show command is implemented as volume_image_metadata in openstack Mitaka version.
Please correct me if i am wrong.

Changed in python-cinderclient:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.