-
Epic
-
Resolution: Done
-
Normal
-
None
-
None
-
None
-
Production/public instance of OSUS should be able to scale withoaut causing issues
-
False
-
False
-
To Do
-
Impediment
-
0% To Do, 0% In Progress, 100% Done
OCP/Telco Definition of Done
Epic Template descriptions and documentation.
<--- Cut-n-Paste the entire contents of this description into your new Epic --->
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. This epic will will link all the 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>
- causes
-
-
- To Do
-
There are no Sub-Tasks for this issue.