rafaelweingartner commented on issue #3012: WIP: Fixed resource calculation
CPU, RAM for accounts.
URL: https://github.com/apache/cloudstack/pull/3012#issuecomment-437395364
@bwsw what happened with this PR? I mean, there are now a lot of docker
files, and other things that are not related
rafaelweingartner commented on issue #3012: WIP: Fixed resource calculation
CPU, RAM for accounts.
URL: https://github.com/apache/cloudstack/pull/3012#issuecomment-436731471
It is a coincidence. It was not a problem because of the changes, but rather
a worked that was working as it should.
rafaelweingartner commented on issue #3012: WIP: Fixed resource calculation
CPU, RAM for accounts.
URL: https://github.com/apache/cloudstack/pull/3012#issuecomment-436640655
Ping me on Slack if you get lost.
This is an au
rafaelweingartner commented on issue #3012: WIP: Fixed resource calculation
CPU, RAM for accounts.
URL: https://github.com/apache/cloudstack/pull/3012#issuecomment-436638636
Actually, you keep using this one. You only need to change the target branch
here, and then update your `bwsw:bug/ac
rafaelweingartner commented on issue #3012: WIP: Fixed resource calculation
CPU, RAM for accounts.
URL: https://github.com/apache/cloudstack/pull/3012#issuecomment-436634502
Sure, but then the process is a little bit different. You need to target
4.11 branch. This will require you to cherr
rafaelweingartner commented on issue #3012: WIP: Fixed resource calculation
CPU, RAM for accounts.
URL: https://github.com/apache/cloudstack/pull/3012#issuecomment-436633277
Ok, I looked in the code, and the table is used in some other places,
specially the `ServiceOfferingJoinVO`. Therefo
rafaelweingartner commented on issue #3012: WIP: Fixed resource calculation
CPU, RAM for accounts.
URL: https://github.com/apache/cloudstack/pull/3012#issuecomment-436631226
Ops, I was with the other issue in the cache... Sorry ;)
Let me load this one out of the HDD again...
--
rafaelweingartner commented on issue #3012: WIP: Fixed resource calculation
CPU, RAM for accounts.
URL: https://github.com/apache/cloudstack/pull/3012#issuecomment-436626755
Can you explain further why (your concerns)?I mean, if logically the result
is the same when finding the physical in
rafaelweingartner commented on issue #3012: WIP: Fixed resource calculation
CPU, RAM for accounts.
URL: https://github.com/apache/cloudstack/pull/3012#issuecomment-436582691
I think you should change the view to include this even when it is deleted,
instead of changing the joining table/vi
