Epic Goal

Fleet admins need a proper tool for planning their RHACM Hub (s). 

Why is this important?

A single hub may suffice in smaller environments, but as the scope of deployment grows to regional and global levels, real concrete numbers need to form the basis for capital expenditure, datacenter hardware layout, networking infrastructure, cloud costs, and so on.

Scenarios

1. As a fleet admin, I would like to enter a few numbers, as estimates to my base plan, and be provided an output that says 'my numbers are OK'
2. As a fleet admin, I am also not sure of what numbers I should be looking at, so please inform me via sufficient documentation, of my planning starting points.
3. As a fleet admin, I perhaps already have a hub or multiple hubs deployed, and I would like to know if they are properly sized. 
4. As a fleet admin, ultimately I am lazy and clueless. Please help me discover what me needs are in an intuitive way.

Acceptance Criteria

1. A public portal accessible across regions.
2. Do not retain customer specific data as part of the calculator tooling.
3. If there is an intersection of data that already exists within RH console/cloud redhat, please make it possible to read from that.

Dependencies (internal and external)

1. ...

Previous Work (Optional):

1. https://sizer.ocs.ninja/

Open questions:

1. …

Done Checklist

• CI - CI is running, tests are automated and merged.
• Release Enablement <link to Feature Enablement Presentation>
• DEV - Upstream code and tests merged: <link to meaningful PR or GitHub
  Issue>
• DEV - Upstream documentation merged: <link to meaningful PR or GitHub
  Issue>
• DEV - Downstream build attached to advisory: <link to errata>
• QE - Test plans in Polarion: <link or reference to Polarion>
• QE - Automated tests merged: <link or reference to automated tests>
• DOC - Downstream documentation merged: <link to meaningful PR>