The State of Things

• Hosted devstack get people onboarded faster.

• We need to figure out what paths we can take and get aligned on the improvements we need to make.

• The two things to work on:

  • Tutor

  • Hosted Devstack

• What is the state of things you have been working on:

Connor: has not had time since our last meeting to get anywhere-- I have read into Kyle’s recent bind/mount improvement plugin which I now will coopt for the turn on/off of local items.

Becca:

Working on getting Tutor working for my personal sprint work. Slow going because I keep having to blow everything up and start over, and because things keep timing out.

Kafka plugin works!

Zach:

Discovery site issues: running different-named configurations locally vs in production

Bottom of doc for discovery usage, which Becca REALLY should have looked at

Blocked on some stuff around platform plugins. It’s complicated and hard to explain. Custom xblocks weren’t working

John:

Hosted devstack forever- some folks are already using it. Collecting feedback on provisioning. Working with SRE to satisfy needs for security and such on AMIs (Amazon Machine Image)

Trying to plan for optionality going forward

Proposal

Rebecca Graber (Deactivated)

• Proposal: Put together a doc that we can show to senior management (Julie, probably), with the pros and cons of pursuing further work on hosted devstack vs tutor, and what we think this further work would look like.

  • Proposal: We work on this concept until the next meeting, where we codify it

• What Features/Value can we get?

  • How do they relate to our overall values as both a WG and a larger company

• What value Are we getting?

• What challenges are we facing

  • Theoretically we are supposed to be deprecating devstack by poplar

  • https://github.com/openedx/devstack/issues/907

  • Devstack can be used to work with master but not released images