Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add sub_metric column to chargeback_rate_detail #93

Merged

Conversation

lpichler
Copy link
Contributor

This is for implementation for chargeback of storage (cloud volume) type.

Metric for allocated storage is now divided according to storage types and we need to store cloud volume type for the ChargebackRateDetail (the be able get metric value and then calculate cost)

So generally: it is adding posibility to divide metric to the small pieces - so this is the why I am calling it 'sub metric'.

In rate editor:

screen shot 2017-10-13 at 15 31 41

(gp2, .. - are cloud volume storage types)

cc @gtanzillo

@miq-bot assign @Fryguy

@gtanzillo gtanzillo self-requested a review October 13, 2017 13:53
For example:
We can have more cloud volume types of for allocated storate metric.
@lpichler lpichler force-pushed the add_sub_metric_to_chargeback_rate_detail branch from 6caf798 to c31f9a4 Compare October 13, 2017 13:59
@miq-bot
Copy link
Member

miq-bot commented Oct 13, 2017

Checked commit lpichler@c31f9a4 with ruby 2.3.3, rubocop 0.47.1, and haml-lint 0.20.0
1 file checked, 0 offenses detected
Everything looks fine. ⭐

Copy link
Member

@gtanzillo gtanzillo left a comment

Choose a reason for hiding this comment

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

👍 LGTM

@lpichler
Copy link
Contributor Author

@Fryguy

@Fryguy Fryguy merged commit 72a96da into ManageIQ:master Oct 23, 2017
@Fryguy Fryguy added this to the Sprint 72 Ending Oct 30, 2017 milestone Oct 23, 2017
@Fryguy Fryguy added the schema label Oct 23, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants