Skip to content

Conversation

@nathanejohnson
Copy link

No description provided.

sc.setJoinParameters("offerings", "accountId", accountId);
sc.setJoinParameters("offerings", "type", VirtualMachine.Type.User);
sc.setJoinParameters("offerings", "state", new Object[] {State.Destroyed, State.Error, State.Expunging});
sc.setJoinParameters("offerings", "displayVm", 1);

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What does this field actually mean? Is it used to hide "system" vms, or vms created by a root admin on behalf of the account? At first glance it would seem that we would want to include all VM's, not just those with the displayVm flag switched.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's an arbitrary name to reference when assigning where clause parameters below that. The join is on vm_instance treacle ultimately, so that's suitable shorthand.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Crap, I didn't change it below to vms

@dcarbone
Copy link

lgtm

When using custom offerings where cpu and memory are specified
with user_vm_details, these totals wouldn't be correctly reflected
in resource_count table.  This should correct that.
@nathanejohnson nathanejohnson force-pushed the bug/fixCPUAndMemoryCounts branch from 089675b to 5c5cefb Compare September 13, 2018 12:22
@dcarbone
Copy link

@nathanejohnson was this one merged with something else or does it still need to be done?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants