[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-4744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nitin Mehta updated CLOUDSTACK-4744:
------------------------------------

    Description: 
updateVolume was enhanced with "path" parameter as a part of the "Ability to 
have better control over first class objects in CS" feature. It allows Admin to 
change path for the volume assuming that the admin knows volume location/name 
on the primary storage.

In addition to that, following fields have to be updatable as well:

* state
* pool_id (primary storage id)
* chaininfo

  was:
updateVolume was enhanced with "path" parameter as a part of the "Ability to 
have better control over first class objects in CS" feature. It allows Admin to 
change path for the volume assuming that the admin knows volume location/name 
on the primary storage.

In addition to that, following fields have to be updatable as well:

* state
* pool_id (primary storage id)


> updateVolume needs more changes in the context of "Ability to have better 
> control over first class objects in CS" feature
> -------------------------------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-4744
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4744
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the 
> default.) 
>    Affects Versions: 4.2.0
>            Reporter: Alena Prokharchyk
>            Assignee: Alena Prokharchyk
>             Fix For: Future
>
>
> updateVolume was enhanced with "path" parameter as a part of the "Ability to 
> have better control over first class objects in CS" feature. It allows Admin 
> to change path for the volume assuming that the admin knows volume 
> location/name on the primary storage.
> In addition to that, following fields have to be updatable as well:
> * state
> * pool_id (primary storage id)
> * chaininfo



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Reply via email to