cloudstack-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From GitBox <>
Subject [GitHub] [cloudstack] jcsdatera opened a new pull request #3410: Add Datera storage plugin
Date Wed, 26 Jun 2019 11:11:03 GMT
jcsdatera opened a new pull request #3410: Add Datera storage plugin
   1. Zone-wide and cluster-wide primary storage support
   2. VM template caching automatically on Datera, the subsequent VMs can be created instantaneously
by fast cloning the root volume.
   3. Rapid storage-native snapshot
   4. Multiple managed primary storages can be created with a single Datera cluster to provide
better management of
         - Total provisioned capacity
         - Default storage QoS values
         - Replica size ( 1 to 5 )
         - IP pool assignment for iSCSI target
         - Volume Placement ( hybrid, single_flash, all_flash )
    5. Volume snapshot to VM template
    6. Volume to VM template
    7. Volume size increase using service policy
    8. Volume QoS change using service policy
    9. Enabled KVM support
   10. New Datera app_instance name format to include ACS volume name
   11. VM live migration
   ## Description
   <!--- Describe your changes in detail -->
   <!-- For new features, provide link to FS, dev ML discussion etc. -->
   <!-- In case of bug fix, the expected and actual behaviours, steps to reproduce. -->
   <!-- When "Fixes: #<id>" is specified, the issue/PR will automatically be closed
when this PR gets merged -->
   <!-- For addressing multiple issues/PRs, use multiple "Fixes: #<id>" -->
   <!-- Fixes: # -->
   ## Types of changes
   <!--- What types of changes does your code introduce? Put an `x` in all the boxes that
apply: -->
   - [ ] Breaking change (fix or feature that would cause existing functionality to change)
   - [ ] New feature (non-breaking change which adds functionality)
   - [ ] Bug fix (non-breaking change which fixes an issue)
   - [x] Enhancement (improves an existing feature and functionality)
   - [ ] Cleanup (Code refactoring and cleanup, that may add test cases)
   ## Screenshots (if appropriate):
   ## How Has This Been Tested?
   <!-- Please describe in detail how you tested your changes. -->
   <!-- Include details of your testing environment, and the tests you ran to -->
   <!-- see how your change affects other areas of the code, etc. -->
   <!-- Please read the [CONTRIBUTING](
document -->

This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:

With regards,
Apache Git Services

View raw message