Bug 1296463

Summary: [RFE] Tenant/Project level chargeback
Product: Red Hat CloudForms Management Engine Reporter: Chen <cchen>
Component: ReportingAssignee: Libor Pichler <lpichler>
Status: CLOSED ERRATA QA Contact: Nandini Chandra <nachandr>
Severity: high Docs Contact:
Priority: high    
Version: 5.5.0CC: jhardy, mfeifer, obarenbo, simaishi, ssainkar
Target Milestone: GAKeywords: FutureFeature
Target Release: 5.6.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: tenant_cfme:chargeback
Fixed In Version: 5.6.0.1 Doc Type: Enhancement
Doc Text:
There was a feature request for Tenant/Project level chargeback in CloudForms. As CloudForms supports multi-tenancy, it should be able to chargeback according to the tenant. This update adds the option Tenant in ChargeBack >Assignments; as a result you can now set a rate to a specific tenant.
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-06-29 15:26:06 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Chen 2016-01-07 10:32:08 UTC
1. Proposed title of this feature request
RFE: Tenant/Project level chargeback
 

2. Who is the customer behind the request?

Account name: 	Sega Games #Acct: 5629336

SRM customer: no

TAM customer: no

Tactical : no

Strategic Customer: no

Is PoC: yes

This customer is very important because it is the first Japan Cloudforms PoC.

 
3. What is the nature and description of the request?

The customer wants a tenant/project level chargeback. 
 

4. Why does the customer need this? (List the business requirements here)

As CFME supports multi-tenant, it is reasonable that we should be able to chargeback according to the tenant.


5. How would the customer like to achieve this? (List the functional requirements here)

By adding one more option in the chargeback assignments.


6. For each functional requirement listed in question 5, specify how Red Hat

and the customer can test to confirm the requirement is successfully implemented.

By adding one more option and implement the feature.


7. Is there already an existing RFE upstream or in Red Hat bugzilla?

No


8. Does the customer have any specific timeline dependencies?

The PoC deadline is 15th Jan.


9. Is the sales team involved in this request and do they have any additional input?

Yes


10. List any affected packages or components.

cfme-5.5.0.13-2.el7cf.x86_64
 
11. Would the customer be able to assist in testing this functionality if implemented?

Yes

Comment 4 Nandini Chandra 2016-05-20 19:40:25 UTC
Verified in 5.6.0.6

Comment 6 errata-xmlrpc 2016-06-29 15:26:06 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2016:1348