To enable prospective customers to easily try out the RHODS service without any costs, we want to enable a developer sandbox option for RHODS. This differs from a trial offering in Red Hat Marketplace in various aspects including:

• Customers would need to pay for underlying infrastructure (AWS) costs in trials whereas the sandbox would have no costs.
• Trials will be for a longer period (eg. 30-60 days) vs. sandbox (14 days).
• Sandbox users would be part of one sandbox cluster vs. having their own cluster in trials.
• The sandbox will likely have much more limited access to ISV partner offerings.

As part of the overall sandbox effort, we will add a RHODS page on the developer site similar to the RHOSAK one here: https://developers.redhat.com/developer-sandbox/activities/connecting-to-your-managed-kafka-instance  The work to enable this content will be managed in a separate effort.

Requirements:

1. The system must enable users to create an account and log in to their sandbox environment.
2. The system must limit user access to 14 days.
3. After the user sandbox period expires, the system must clean up all user resources created during the sandbox period.
4. The sandbox must be able to scale to support up to (TBD: 500) concurrent users.
5. The sandbox dashboard should have the following changes relative to the standard RHODS service: a) Restrict ability to sign up for any ISV partner offerings (hide explore tab?); b) Restrict ability to select container size and GPUs in spawner page
6. The system must have the following services automatically enabled (available in enabled tab): a) RHOAM; b) RHOSAK
7. TBD: The system must provide sample Jupyter notebooks with associated data sets (eg. csv files) to enable experimentation with sample use cases. 
8. Red Hat employees must be able to track metrics for: a) number of active sandbox users; b) total number of sandbox users over defined date range (including total since start of sandbox); c) date of last use per user; d) avg. usage hours per day 

Questions:

1. Do we keep support link?
2. Do we want to make any ISV offerings available?
3. Do we keep all ISV doc in resources tab? Maybe just leave it so users can discover what's available

Link to working doc: https://docs.google.com/document/d/1tdIntcbBGL8x63BcXbtzr8voA2HJPafMbyzLBnGeq1A/edit#heading=h.f3ef56eokswv