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

Consider cloud volumes as data storages in chargeback #16638

Merged

Conversation

lpichler
Copy link
Contributor

@lpichler lpichler commented Dec 11, 2017

We can assign rate according to the tag of data storages of Vm:
screen shot 2017-12-12 at 09 00 33

What is data storages ?

for Infra: Vm#storage
for Cloud Vm#cloud_volumes

Variant 'for Cloud Vm#cloud_volumes' was missing and this PR is adding it.

Alternative

We can also add to the assignments option 'Tagged Cloud Volumes' but I think that this is beneficial, user can generate report for cloud and infra in one report.

Next?

Update in same way option 'Selected Datastores' and here cloud volumes as well.

Links

@miq-bot add_label gaprindashvili/yes, chargeback, bug

@miq-bot assign @gtanzillo

@miq-bot miq-bot added the wip label Dec 11, 2017
@lpichler lpichler force-pushed the consider_cloud_volumes_as_datastorages branch from 3bb1a5c to 2db33a4 Compare December 12, 2017 07:44
@miq-bot
Copy link
Member

miq-bot commented Dec 12, 2017

Checked commits lpichler/manageiq@9da6220~...56edf32 with ruby 2.3.3, rubocop 0.47.1, haml-lint 0.20.0, and yamllint 1.10.0
4 files checked, 0 offenses detected
Everything looks fine. 🏆

@lpichler lpichler changed the title [WIP] Consider cloud volumes as data storages in chargeback Consider cloud volumes as data storages in chargeback Dec 12, 2017
@miq-bot miq-bot removed the wip label Dec 12, 2017
@lpichler
Copy link
Contributor Author

@miq-bot add_label gaprindashvili/yes, chargeback, bug

@miq-bot assign @gtanzillo

@gtanzillo gtanzillo added this to the Sprint 76 Ending Jan 1, 2018 milestone Dec 12, 2017
@gtanzillo gtanzillo merged commit 633283e into ManageIQ:master Dec 12, 2017
simaishi pushed a commit that referenced this pull request Dec 14, 2017
…astorages

Consider cloud volumes as data storages in chargeback
(cherry picked from commit 633283e)

https://bugzilla.redhat.com/show_bug.cgi?id=1526039
@simaishi
Copy link
Contributor

Gaprindashvili backport details:

$ git log -1
commit 6a64e476973b3fc02410137c4db3da9eb8ca2582
Author: Gregg Tanzillo <gtanzill@redhat.com>
Date:   Tue Dec 12 11:26:05 2017 -0500

    Merge pull request #16638 from lpichler/consider_cloud_volumes_as_datastorages
    
    Consider cloud volumes as data storages in chargeback
    (cherry picked from commit 633283e3f38e6cf2edf9210ffc8ac7d4a287135b)
    
    https://bugzilla.redhat.com/show_bug.cgi?id=1526039

@lpichler lpichler deleted the consider_cloud_volumes_as_datastorages branch December 14, 2017 17:01
@lpichler
Copy link
Contributor Author

@miq-bot add_label fine/yes

simaishi pushed a commit that referenced this pull request Dec 15, 2017
…astorages

Consider cloud volumes as data storages in chargeback
(cherry picked from commit 633283e)

https://bugzilla.redhat.com/show_bug.cgi?id=1526040
@simaishi
Copy link
Contributor

Fine backport details:

$ git log -1
commit dea4b85641fa98ba89849e3709e3dd8d0a1c68fb
Author: Gregg Tanzillo <gtanzill@redhat.com>
Date:   Tue Dec 12 11:26:05 2017 -0500

    Merge pull request #16638 from lpichler/consider_cloud_volumes_as_datastorages
    
    Consider cloud volumes as data storages in chargeback
    (cherry picked from commit 633283e3f38e6cf2edf9210ffc8ac7d4a287135b)
    
    https://bugzilla.redhat.com/show_bug.cgi?id=1526040

d-m-u pushed a commit to d-m-u/manageiq that referenced this pull request Jun 6, 2018
…s_as_datastorages

Consider cloud volumes as data storages in chargeback
(cherry picked from commit 633283e)

https://bugzilla.redhat.com/show_bug.cgi?id=1526040
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants