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