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

ASF GitHub Bot commented on CLOUDSTACK-8847:
--------------------------------------------

Github user nitin-maharana commented on the pull request:

    https://github.com/apache/cloudstack/pull/823#issuecomment-162947373
  
    The functionality purely depends on the meaning of compatibility. Here is 
what I understood about the compatibility. For example, if our current compute 
offering is associated with tags (x,y) then the new compute offering should 
have tags atleast (x,y), then only it can have the same functionality as the 
current one. Suppose the new offering has the only tag(x), then it is missing 
the functionality associated with tag(y).
    
    One more example, Suppose we have three hosts H1,H2,H3.
    The tags associated with H1 is (x,y), H2 is only (y) and H3 is (x,y,z).
    
    Suppose our current compute offering has (x,y) as host tags. So the VM can 
be placed in H1 or H3 as both the tags are associated with these hosts but 
cannot be placed in H2 as tag (x) is missing. But according to the prior 
situation, it can list a compute offering which has host tag only (y), so the 
VM can be placed in H2 also. I think this is an issue. 


> ListServiceOfferings is returning incompatible tagged offerings when called 
> with VM id
> --------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-8847
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8847
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the 
> default.) 
>            Reporter: Nitin Kumar Maharana
>
> When calling listServiceOfferings with VM id as parameter. It is returning 
> incompatible tagged offerings. It should only list all compatible tagged 
> offerings. The new service offering should contain all the tags of the 
> existing service offering. If that is the case It should list in the result.



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

Reply via email to