GitHub user mike-tutkowski opened a pull request:

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

    System VMs on Managed Storage

    This PR makes it easier to spin up system VMs on managed storage.
    
    Managed storage is when you have a dedicated volume on a SAN for a 
particular virtual disk (making it easier to deliver QoS).
    
    For example, with this PR, you'd likely have a single virtual disk for a 
system VM. On XenServer, that virtual disk resides by itself in a storage 
repository (no other virtual disks share this storage repository).
    
    Same concept for vSphere. The virtual disk of the system VM would reside by 
itself in a datastore (no other virtual disks share this datastore).
    
    It was possible in the past to spin up system VMs that used managed 
storage, but this PR facilitates the use case by making changes to the System 
Service Offering dialog (and by putting in some parameter checks in the 
management server).

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

    $ git pull https://github.com/mike-tutkowski/cloudstack managed_system_vms

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

    https://github.com/apache/cloudstack/pull/1642.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 #1642
    
----
commit af8e76c8e993ac6298d643fbf1f588ab0e5265f9
Author: Mike Tutkowski <mike.tutkow...@solidfire.com>
Date:   2016-08-12T03:26:06Z

    Updated the GUI to enable storage QoS for system VMs

commit 3b84b10f8e3b95e832a2ed2509f84552fe6f67a7
Author: Mike Tutkowski <mike.tutkow...@solidfire.com>
Date:   2016-08-12T04:53:52Z

    Throw an exception if customized IOPS or hypervisor snapshot reserve are 
passed in for a system VM.

----


---
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