Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Strongly recommended and supported by tCRIL

    • We get on-call help from Kyle and Regis who are very interested in us adopting Tutor.

  • Consistent with most of the Open edX community

...

Creating a cloud-hosted devstack

Completed Work

  • Functional infrastructure for launching an EC2 instance running devstack

Remaining Work

  • Monitoring and automation to avoid unnecessary cost of cloud devstack instances that outlive their usefulness (some of this may be cribbed from existing code for sandbox management)

Pros:

  • Removes issues of 2U hosted macs having problems with sudo, etc

  • Allows for prebuilt AMI snapshots with complex data without having to wait for data provisioning at launch time

  • Potentially shareable, which makes Dev lives very easy

  • Could be used in conjunction with Tutor using same cloud-hosting tech

Cons

  • Incurs cloud hosting costs per instance deployed

  • That cost increases the need to throw away and rebuild dev environments, which can make it difficult to retain custom sets of test data until other tooling (like for OEP-37: Dev Data) matures

  • Another service which needs to be maintained (namely, the infrastructure for launching and managing these VMs)

Continuing incremental improvements to local devstack

Completed Work

  • Branch that solves the most acute pain points on Apple Silicon laptops

Remaining Work

Pros

  • People’s lives are made easier, work at 2U is sped up when Devstack works better/ isn’t broken

Cons

  • Duplicates effort from the Open edX community going into Tutor

  • Makes it harder to collaborate with Open edX developers who have already switched to Tutor (sometimes out of necessity)

Improving sandboxes for development

Completed Work

Remaining Work

Pros

Cons

Related projects

Concerns

  • Staffing - What are the top priorities? What’s important enough to preempt other projects in progress?

...