Uploaded image for project: 'Cost Management'
  1. Cost Management
  2. COST-18

AWS Organizational Unit Support

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Done
    • Icon: Major Major
    • JIRA-MIgration-Old-Issues
    • None
    • None
    • None
    • AWS organizational unit support
    • Done
    • COST-216 - Adding support for hierarchies in clouds
    • COST-216Adding support for hierarchies in clouds
    • 0% To Do, 0% In Progress, 100% Done

      User Story

      As a user I want to view the cost details of a particular AWS Organizational Unit, so that I can provide the finance department a charge or assign that cost to that organizational unit in some way.

      Prioritization / Business Case

      This is a request from the RH PnT group that is trying to use Cost Management to track RH's AWS spending. This feature is a potential use case for other enterprise companies trying to get visibility into their spend.

      Impacts

      • API - Yes
      • Data Backend - Maybe?
      • Docs - Yes
      • UI - Yes
      • UX - Yes

      Related Stories

      * Features that are related (A feature flag or criteria affecting a related feature may have impacts on this feature

      External Dependencies

      * Platform services, etc

      UX Requirements

      • User should be able to view an AWS cost roll up for a particular AWS OU
      • The following are the mocks that were designed out of that discussion: https://marvelapp.com/56c434i

      UI Requirements

      dlabrecq@redhat.com please correct me if I'm wrong in the following:

      • For the group/view by selector, UI will require an API that would return a flat list of all the AWS OU for the account
      • For the filter selector, UI will require an API that would return a list of child AWS OU of the AWS OU that was selected in the group/view by selector.

      Documentation Requirements

      Not applicable

      Backend Requirements

      _ * Are there any prerequisites required before working this epic? _
      aberglun@redhat.com There really isn't, correct?

      QE Requirements

      • We discussed before about having some method potentially in Nise (if that makes sense) to generate OUs and related data for testing

      Release Criteria

      • This epic can only be released when all issues/tasks have been completed
      • The backend can be released without the frontend
      • The frontend cannot be released without the backend
      • QE has qualified this epic according to meeting notes

      https://docs.google.com/document/d/13XBitSowv-oul8sd6TrJQgQjB4Qb0RStqg5u2YOg3uk/edit?usp=sharing

              rhn-support-lcouzens Luke Couzens
              nlcwong Natalie Wong
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

                Created:
                Updated: