Bug 1215202
| Summary: | Custom billing provider needs to be customizable within the broker service. | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Phil Festoso <philfest> |
| Component: | RFE | Assignee: | Mike Barrett <mbarrett> |
| Status: | CLOSED WONTFIX | QA Contact: | |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 2.2.0 | CC: | erich, jokerman, libra-onpremise-devel, mbarrett, mmccomas, philfest |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-04-14 19:46:58 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: | |
| Embargoed: | |||
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days |
1. Proposed title of this feature request Custom billing provider needs to be customizable within the broker service. 2. Who is the customer behind the request? Account: United Health Care 620335 TAM customer: yes SRM customer: no Strategic: yes 3. What is the nature and description of the request? Customer would like to implement a billing/chargebacks solution. 4. Why does the customer need this? (List the business requirements here) Having the ability to bill their customers for usage is crucial to the business (ROI, etc). 5. How would the customer like to achieve this? (List the functional requirements here) Provide extensible API so customers can implement plugable billing solution. (We seem to have inherited some Online code that's caused some confusion. See support case for example 01430072. Customer file case in response trying to get oo-admin-ctl-usage --sync to work. 6. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented. Customer would create billing solution and test the --sync feature of oo-admin-ctl-usage. (Or whatever is made available) 7. Is there already an existing RFE upstream or in Red Hat Bugzilla? No 8. Does the customer have any specific timeline dependencies and which release would they like to target (i.e. RHEL5, RHEL6)? They would like to see this feature is OSEv2 9. Is the sales team involved in this request and do they have any additional input? Yes, they are involved and will likely have more to say. 10. List any affected packages or components. 11. Would the customer be able to assist in testing this functionality if implemented? Yes