-
Notifications
You must be signed in to change notification settings - Fork 5
Closed
4 / 44 of 4 issues completedLabels
Epicproduct:infrastructureIssues related to application and operations infrastructureIssues related to application and operations infrastructureproduct:residential
Description
User Story
- As a platform operator I want all of my Open edX environments to be managed in the same way
- I want my edX environments to be adaptive and scalable based on actual usage
- I want to reduce the amount of wasted spend on compute for idle resources
Description/Context
The Learn and xPRO Open edX deployments have been updated to run on the applications Kubernetes clusters. The residential deployment needs to be converted to match that approach but with a dedicated cluster to keep it separate for reasons of load separation and cost reporting.
Acceptance Criteria
- There is a Kubernetes cluster deployed in the MITx Residential VPC environments
- The MITx Residential Open edX deployments are running in their dedicated cluster
- The MITx Residential Staging deployment is consolidated to use the same physical hardware as the MITx Residential Live environment, but with separate logical databases
- MongoDB
- MySQL
- Elasticache
Plan/Design
Sub-issues
Metadata
Metadata
Assignees
Labels
Epicproduct:infrastructureIssues related to application and operations infrastructureIssues related to application and operations infrastructureproduct:residential