[
https://issues.apache.org/jira/browse/CLOUDSTACK-9620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16217618#comment-16217618
]
ASF GitHub Bot commented on CLOUDSTACK-9620:
--------------------------------------------
mike-tutkowski commented on issue #2298: CLOUDSTACK-9620: Enhancements for
managed storage
URL: https://github.com/apache/cloudstack/pull/2298#issuecomment-339118036
That is actually snapshots on the storage system (SolidFire snapshots, in
this case). The problem is that we have to copy the volume from a source to a
new destination volume (due to the way Storage XenMotion works) and can’t
reproduce the snapshots on the destination side.
From: Syed Mushtaq Ahmed <[email protected]>
Reply-To: apache/cloudstack <[email protected]>
Date: Tuesday, October 24, 2017 at 1:22 PM
To: apache/cloudstack <[email protected]>
Cc: "Tutkowski, Mike" <[email protected]>, Author
<[email protected]>
Subject: Re: [apache/cloudstack] CLOUDSTACK-9620: Enhancements for managed
storage (#2298)
Don’t allow Storage XenMotion on a VM that has any managed-storage volume
with one or more snapshots.
Is this VM snapshots on XenServer or snapshots on SolidFire?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on
GitHub<https://github.com/apache/cloudstack/pull/2298#issuecomment-339102623>,
or mute the
thread<https://github.com/notifications/unsubscribe-auth/AC4SHy4eBZ9UNyxLqB8hQfFSiLl4KafUks5svjkNgaJpZM4P7Giw>.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
> Improvements for Managed Storage
> --------------------------------
>
> Key: CLOUDSTACK-9620
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9620
> Project: CloudStack
> Issue Type: Improvement
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: KVM, Management Server, VMware, XenServer
> Affects Versions: 4.11.0.0
> Environment: KVM, vSphere, and XenServer
> Reporter: Mike Tutkowski
> Assignee: Mike Tutkowski
> Fix For: 4.11.0.0
>
>
> Allowed zone-wide primary storage based on a custom plug-in to be added via
> the GUI in a KVM-only environment (previously this only worked for XenServer
> and VMware)
> Added support for root disks on managed storage with KVM
> Added support for volume snapshots with managed storage on KVM
> Enable creating a template directly from a volume (i.e. without having to go
> through a volume snapshot) on KVM with managed storage
> Only allow the resizing of a volume for managed storage on KVM if the volume
> in question is either not attached to a VM or is attached to a VM in the
> Stopped state.
> Included support for Reinstall VM on KVM with managed storage
> Enabled offline migration on KVM from non-managed storage to managed storage
> and vice versa
> Included support for online storage migration on KVM with managed storage
> (NFS and Ceph to managed storage)
> Added support to download (extract) a managed-storage volume to a QCOW2 file
> When uploading a file from outside of CloudStack to CloudStack, set the min
> and max IOPS, if applicable.
> Included support for the KVM auto-convergence feature
> The compression flag was actually added in version 1.0.3 (1000003) as opposed
> to version 1.3.0 (1003000) (changed this to reflect the correct version)
> On KVM when using iSCSI-based managed storage, if the user shuts a VM down
> from the guest OS (as opposed to doing so from CloudStack), we need to pass
> to the KVM agent a list of applicable iSCSI volumes that need to be
> disconnected.
> Added a new Global Setting: kvm.storage.live.migration.wait
> For XenServer, added a check to enforce that only volumes from zone-wide
> managed storage can be storage motioned from a host in one cluster to a host
> in another cluster (cannot do so at the time being with volumes from
> cluster-scoped managed storage)
> Don’t allow Storage XenMotion on a VM that has any managed-storage volume
> with one or more snapshots.
> Enabled for managed storage with VMware: Template caching, create snapshot,
> delete snapshot, create volume from snapshot, and create template from
> snapshot
> Added an SIOC API plug-in to support VMware SIOC
> When starting a VM that uses managed storage in a cluster other than the one
> it last was running in, we need to remove the reference to the iSCSI volume
> from the original cluster.
> Added the ability to revert a volume to a snapshot
> Enable cluster-scoped managed storage
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
