-
Epic
-
Resolution: Unresolved
-
Normal
-
None
-
None
-
None
-
None
-
Production/public instance of OSUS should be able to scale without causing issues in a multi-tenant environment- phase2
-
False
-
None
-
False
-
Not Selected
-
To Do
-
56% To Do, 22% In Progress, 22% Done
Epic Goal
We had an incident (outage) in the past where OSUS impacted other applications running in that multi tenant environment along with itself. Refer [1][2] for more details.
We initially created all Jira cards as part of OTA-552. But the epic grew very large. So moving some cards to this epic. The associated Jira cards which are created to improve the ability of OSUS to handle more requests without causing issues with other application in an multi-tenant environment.
Why is this important?
- ...
Scenarios
- ...
Acceptance Criteria
- CI - MUST be running successfully with tests automated
- Release Technical Enablement - Provide necessary release enablement details and documents.
- ...
Dependencies (internal and external)
- ...
Previous Work (Optional):
- ...
Open questions::
- ...
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>
