Github user rafaelweingartner commented on the issue:
https://github.com/apache/cloudstack/pull/1918
That is a good idea @nvazquez, thanks for the help here ;)
What do you think guys (@nvazquez, @borisstoyanov, @jayakarteek)? if we use
the "summary.config.cpuReservatio" as @nvazquez suggested we could remove the
changes proposed on (UserVmJoinDaoImpl.java) and avoid having a POJO with
inconsistent data. Moreover, we concentrate VMware related logic and operation
in VMware classes.
---
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.
---
