cloudstack/engine/storage
Koushik Das bc399b981f volume-upload: If SSVM is destroyed and started, then partially uploaded volumes/templates remain in
inconsistent state (NotUploaded or UploadInProgress) and doesn't transition to any terminal
state (Uploaded, Uploaded). As a result these volumes/templates cannot be removed. Fix is to handle such
volume/template entries correctly.
2015-04-22 19:28:51 +05:30
..
cache Bump master version to 4.6.0-SNAPSHOT after branching 4.5.0-SNAPSHOT 2014-10-29 14:54:23 +01:00
datamotion Create a template from a SAN snapshot 2014-11-06 10:33:23 -07:00
image volume-upload: If SSVM is destroyed and started, then partially uploaded volumes/templates remain in 2015-04-22 19:28:51 +05:30
integration-test Added a "long getUsedIops(StoragePool)" method to the PrimaryDataStoreDriver interface 2014-11-12 13:38:58 -07:00
resources/META-INF/cloudstack fix compile 2013-11-01 16:16:03 -07:00
snapshot Adding support for backend snapshots to Xenserver625StorageProcessor 2014-11-10 22:41:00 -07:00
src/org/apache/cloudstack/storage volume-upload: If SSVM is destroyed and started, then partially uploaded volumes/templates remain in 2015-04-22 19:28:51 +05:30
test/org/apache/cloudstack/engine/subsystem/api/storage Reformatted all of the code. 2013-11-21 06:15:26 -08:00
volume volume-upload: If SSVM is destroyed and started, then partially uploaded volumes/templates remain in 2015-04-22 19:28:51 +05:30
pom.xml Bump master version to 4.6.0-SNAPSHOT after branching 4.5.0-SNAPSHOT 2014-10-29 14:54:23 +01:00
storage.ucls Cleanup of Xen and XenServer terms. Cloned xen plugin creating a xenserver plugin, then removed xen plugin 2014-06-07 04:50:23 -04:00