GitHub user mike-tutkowski opened a pull request:

    https://github.com/apache/cloudstack/pull/1748

    KVM enhancements for managed storage

    This PR contains changes mainly related to enhancing managed storage on 
KVM. I recently added these features to a custom build of 4.5 for a prospect 
(and, here, I'd like to place these changes in master):
    
    Allow zone-wide primary storage based on a custom plug-in to be added via 
the GUI in a KVM-only environment.
    
    Support for root disks on managed storage with KVM
    
    Template caching with managed storage and KVM
    
    Support for volume snapshots with managed storage on KVM
    
    Added the ability to revert a volume to a snapshot on KVM
    
    Updated some integration tests
    
    Enforce that a SolidFire volume’s Min IOPS cannot exceed 15,000 and its 
Max and Burst IOPS cannot exceed 100,000.
    
    A SolidFire volume must be at least one GB.
    
    The storage driver should not remove the row from the 
cloud.template_spool_ref table.
    
    Enable cluster-scoped managed storage
    
    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).
    
    Updates for SAN-assisted snapshots

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/mike-tutkowski/cloudstack 
managed-storage-enhancements-for-kvm

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/cloudstack/pull/1748.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1748
    
----

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Reply via email to