[
https://issues.apache.org/jira/browse/DTACLOUD-532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dies Koper updated DTACLOUD-532:
--------------------------------
Attachment: 0009-FGCP-exclude-system-disks-from-storage_volumes-and-c.patch
Patch that fixes the issue.
> fgcp: storage_volumes (and cimi volumes collection) should not include system
> disks
> -----------------------------------------------------------------------------------
>
> Key: DTACLOUD-532
> URL: https://issues.apache.org/jira/browse/DTACLOUD-532
> Project: DeltaCloud
> Issue Type: Bug
> Components: Server
> Environment: FGCP
> Reporter: Dies Koper
> Assignee: Dies Koper
> Attachments:
> 0009-FGCP-exclude-system-disks-from-storage_volumes-and-c.patch
>
>
> Currently, storage_volumes (and thereby cimi volumes) include both system and
> additional disks with the fgcp.
> The reason I included system disks was because it exposed the snapshot
> (backup & restore) operation for the system disk.
> This is very apparent when listing system volumes: when creating a system
> from a template with only machine templates, no volume templates, the system
> volume collection includes the machines' system volumes, which just looks
> wrong.
> Also, in a recent discussion on the DC dev ML with David L., it was clarified
> that system disks should not be included:
> -----
> are these truly volumes (i.e., storage that as its own lifecycle, not
> connected to that of the machine to which it is attached ?) If so, I
> believe they should be included - if they vanish when the machine
> vanishes, they are 'disks' not 'volumes' in CIMI lingo.
> -----
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
