Discovery for testing EC2 and Containerized LMS/Studio in parallel

[robrap]

This ticket is for discovery on how to test the containerized LMS/Studio before an official cut-over.

For example, SRE is working on standing up a containerized version of Studio in Stage, while the Stage environment still points to the EC2 version of Studio.

The following questions are about how to test the new containerized version of Studio (and LMS), before switching over all end users to the new containerized version.

• Do we need a new sub-environment within Stage (and then maybe Prod and Edge), and how deep does it need to go?
  • Does it need a separate domain and/or ELB?
  • Do we need new MFEs, or would we use /etc/hosts?
  • Do we need duplicate backend services for service-to-service calls to test calls back to the LMS? Or will this not be tested until the final cutover (per environment)?
  • Could we use a sandbox with nginx as a proxy?
  • Do we basically need a containerized-stage environment with all parts duplicated?
  • Could existing nginx in stage/edge/prod choose the LMS/Studio based on IP, or percent rollout, or other?
  • Other possible solutions?