I opened the following ticket:
https://issues.apache.org/jira/browse/CLOUDSTACK-9371
From: Tutkowski, Mike
Sent: Wednesday, April 27, 2016 7:12 PM
To: dev@cloudstack.apache.org
Subject: Re: Resizing a volume
It appears the offending code was added here
Subject: Re: Resizing a volume
I see the problem.
It's in storage.js
if (jsonObj.hypervisor == "KVM" || jsonObj.hypervisor == "XenServer" ||
jsonObj.hypervisor == "VMware") {
if (jsonObj.state == "Ready" || jsonObj.state == "
ving.
Maybe a GUI developer can fill us in as to what's expected here?
From: Tutkowski, Mike
Sent: Wednesday, April 27, 2016 5:13 PM
To: dev@cloudstack.apache.org
Subject: Re: Resizing a volume
Here's a pic:
http://imgur.com/2k380Yd
It's for a vol
tack.apache.org
Subject: Re: Resizing a volume
Hi Wido,
I'm referring to the commands.properties file, where you can set permissions
for a given API.
However, I see volumeResize has the following setting, which should enable
users to access it:
resizeVolume=15
Perhaps there's just a b
alk to you later,
Mike
From: Wido den Hollander
Sent: Wednesday, April 27, 2016 1:33 AM
To: Tutkowski, Mike; dev@cloudstack.apache.org
Subject: Re: Resizing a volume
> Op 26 april 2016 om 22:37 schreef "Tutkowski, Mike"
> :
>
>
> ??
> Op 26 april 2016 om 22:37 schreef "Tutkowski, Mike"
> :
>
>
> ??Hi,
>
>
> I noticed that by default non-admins cannot resize a volume to a different
> disk offering.
>
>
> Anyone know why that's the default behavior? I would think that would be an
> expected operation for end users.
>
