Versions Compared

Key

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

...

  • OCM-specific instructions for developing with Tutor, including instructions for edx-platform, enterprise, and course_discovery: Using Tutor for local development

  • Several issues created for and then solved by the Tutor team at tCRIL (easier mounting, fixing RCM)

Remaining Work

Pros

  • 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

Cons

  • (I’ve started tracking blockers under the 2u-blocker label: https://github.com/overhangio/2u-tutor-adoption/labels/2u-blocker -Kyle)

  • Tutor is not fully optimized for development and still suffers from some slowness and missing features

    • For example, the default of rebuilding the image every time you want to run the service is very slow, especially as it for some reason it needs to collect assets every time

  • High activation energy cost to switching the entire OCM organization off devstack

  • Context switching between Tutor and Devstack is costly time-wise

    • Sometimes prune all images, which takes a while

Creating a cloud-hosted devstack

...

  • Finish and merge the Apple Silicon fixes

  • Establish migration plan for developers upgrading mysql locally

  • Switch from Ansible-using images from the configuration repo to simpler images generated from Dockerfiles in each service repo - https://github.com/openedx/devstack/issues/943

...

Completed Work

Remaining Work

Pros

Cons

  • Installing everything on a VM is an anti-pattern

Related projects

...