GitHub user rhtyd opened a pull request:

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

    ui: show resize volume button to all users

    ![screenshot from 2016-06-23 
12-29-56](https://cloud.githubusercontent.com/assets/95203/16294438/436f6dbc-393e-11e6-91b5-cb2e49a01cc6.png)
    
    The resize volume is support on all major hypervisors (Xen, VMware, KVM).
    The hypervisor key is returned by the list volumes response only for admins
    but not for users or domain admin users. This removes the check, as the 
operation
    is supported on all major hypervisors that CloudStack supports.
    
    With this bug fix all users would see resize volume button in the UI.
    
    /cc @swill 

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

    $ git pull https://github.com/shapeblue/cloudstack ui-resize-show-allusers

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

    https://github.com/apache/cloudstack/pull/1595.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 #1595
    
----
commit b68ae1949e9fa5ae376a0ae7b67c3349b9e83418
Author: Rohit Yadav <rohit.ya...@shapeblue.com>
Date:   2016-06-23T06:57:51Z

    ui: show resize volume button to all users
    
    The resize volume is support on all major hypervisors (Xen, VMware, KVM).
    The hypervisor key is returned by the list volumes response only for admins
    but not for users or domain admin users. This removes the check, as the 
operation
    is supported on all major hypervisors that CloudStack supports.
    
    With this changes all users would see resize volume button in the UI.
    
    Signed-off-by: Rohit Yadav <rohit.ya...@shapeblue.com>

----


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