[jira] [Commented] (CLOUDSTACK-9433) Change of VM compute offering with additional storage tags not allowed

["ilya musayev (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-9433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15388039#comment-15388039 ] 

ilya musayev commented on CLOUDSTACK-9433:
------------------------------------------

Lets think this thru...

You are a hosting provider that has 10,000 virtual machines with compute offering A that has no storage tags. 

From the underlying infrastructure - that is a fairly sized environment with petabyte of storage across many clusters and zones.. 

Change it on the fly - would wreck havoc  - if tag was missed somewhere. 

Its far easier to migrate to service offering that has a tag VS updating an existing service offering with a tag. 

It would require a downtime - but so would your proposed implementation. 

The difference is - the update of service offering - is a structured approach - where you can decide who moves to what storage tag and where... Changing tag on existing service offering that has many vms associated - is helping incompetent admin - shoot himself in the foot. 

For an advanced user like yourself, you can alter the tag in MySQL DB directly - if you are certain the tag change won't cause any vm start issues.

Regards
ilya

> Change of VM compute offering with additional storage tags not allowed
> ----------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-9433
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9433
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>    Affects Versions: 4.8.0
>            Reporter: Christian Meier
>
> It is not possible to upgrade service offerings of a with no storage tags to a offering with a storage tag.
> The UI does not show a newly created Service Offering which has defined a Storage Tag. If tried through cloudmonkey, the error reports :
> "Unable to upgrade virtual machine; the new service offering should have tags as subset of current service offering tags. Current service offering tags: []; new service offering tags: [RootLun]"
> While I understood the error message in the first place, it seems to me an artificially introduced restriction which does not reflect real circumstances.
> Usually users start without using a sophisticated tagging scheme. Later on while already having instantiated VMs, and maybe getting additional primary storage they want to refine their usage scheme. They start to create offerings with storage tags. All existing machines cannot migrate to these new service offerings but must be completely reinstalled.
> (An automatic storage migration might be an additional option, but I think still the ROOT admin can manually migrate the existing volumes if necessary.) More importantly, I think the artificial restriction must be removed.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)