Feature #778
Disk image type should be propagated by saveas
| Status: | Closed | Start date: | 08/22/2011 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | - | % Done: | 0% | |
| Category: | Core & System | |||
| Target version: | Release 3.2 - S1 | |||
| Resolution: | fixed | Pull request: |
Description
The metadata should be inherited from source VM template
From Robert Parrott parrott@seas.harvard.edu
--
he
disk type is vital metadata for using the disk image, and needs to be
propagated along with location and other data from the running VM
instance to to the image manager when the "saveas" command is issued.
Otherwise the "DRIVER" metadata is missing from the image template,
and there's no information about how to use the image; one would have
to guess at the image type without prior knowledge ( as I did).
History
#1
Updated by Ruben S. Montero almost 10 years ago
- Target version set to Release 3.4
#2
Updated by Ruben S. Montero almost 10 years ago
- Assignee set to Tino Vázquez
#3
Updated by Ruben S. Montero almost 10 years ago
- Assignee deleted (
Tino Vázquez)
#4
Updated by Ruben S. Montero almost 10 years ago
- Status changed from New to Assigned
- translation missing: en.field_story_points set to 0
#5
Updated by Ruben S. Montero almost 10 years ago
- Status changed from Assigned to New
#6
Updated by Ruben S. Montero almost 10 years ago
- Category set to Core & System
#7
Updated by Ruben S. Montero over 9 years ago
- Status changed from New to Closed
- Target version changed from Release 3.4 to Release 3.2 - S1
- Resolution set to fixed
We have solved this with two new features:
- Image type can be specified through the save_as method
- Image types can be changed