[
https://issues.apache.org/jira/browse/CLOUDSTACK-9620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16319596#comment-16319596
]
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-356481529
@rhtyd Just so I get a feeling for the test failures with regards to other
PRs: Are other PRs failing with issues that don't seem directly related to them?
With regards to my progress running the managed-storage tests, I'm about 1/3
of the way through.
So far, I only see one failure. It is possibly related to commit 1d0f212.
The problem concerns SAN-assisted snapshots. This is when we take a SAN
snapshot, but we don't want to keep the snapshot on the SAN, so we migrate it
to secondary storage (the idea here is to minimize the impact on the source
volume that we are taking a volume snapshot on by not copying from that volume
to secondary storage, but rather going through a SAN snapshot).
In any event, we can't create a template from this kind of snapshot anymore
because we can't find a hypervisor host to perform the copy from secondary to
primary storage.
I have this noted and plan to investigate it soon. In the meanwhile, I've
just continued running the tests and all has been well with them.
Once I have all of the tests run, I can post results.
----------------------------------------------------------------
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:
us...@infra.apache.org
> 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
> Enabled creating a template directly from a volume (i.e. without having to go
> through a volume snapshot) on KVM with managed storage
> Only allowed 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
> Enabled cluster-scoped managed storage
> Added support for VMware dynamic discovery
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
