cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-9620) Improvements for Managed Storage
Date Wed, 27 Dec 2017 00:41:00 GMT


ASF GitHub Bot commented on CLOUDSTACK-9620:

mike-tutkowski commented on a change in pull request #2298: CLOUDSTACK-9620: Enhancements
for managed storage

 File path: plugins/api/solidfire-sioc/pom.xml
 @@ -0,0 +1,47 @@
+  Licensed to the Apache Software Foundation (ASF) under one
+  or more contributor license agreements. See the NOTICE file
+  distributed with this work for additional information
+  regarding copyright ownership. The ASF licenses this file
+  to you under the Apache License, Version 2.0 (the
+  "License"); you may not use this file except in compliance
+  with the License. You may obtain a copy of the License at
+  Unless required by applicable law or agreed to in writing,
+  software distributed under the License is distributed on an
+  KIND, either express or implied. See the License for the
+  specific language governing permissions and limitations
+  under the License.
+<project xmlns="" xmlns:xsi=""
+  <modelVersion>4.0.0</modelVersion>
+  <artifactId>cloud-plugin-api-solidfire-sioc</artifactId>
+  <name>Apache CloudStack Plugin - API SolidFire (SIOC)</name>
 Review comment:
   @rhtyd From what I recall, I have enabled this to only run with the -Dnoredist flag. It
is an API plug-in, so I just placed it with the other API plug-ins that I found. I'm fine
with moving it, though, if you think that's the better way to go. Let me know. Thanks!

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:

> Improvements for Managed Storage
> --------------------------------
>                 Key: CLOUDSTACK-9620
>                 URL:
>             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:
>         Environment: KVM, vSphere, and XenServer
>            Reporter: Mike Tutkowski
>            Assignee: Mike Tutkowski
>             Fix For:
> 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
> 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:
> 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
> Add support for VMware dynamic discovery

This message was sent by Atlassian JIRA

View raw message