$customHeader
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

  • XQueue (Kevin Falcone)
    • Removing RabbitMQ, not moving to Redis
    • Upgrade to Django 1.11
    • Going to production tomorrow morning
    • It's available but off by default in Devstack
    • PDF certificates go through XQueue, but edX doesn't use PDF certificates, so please test
    • Bug fixes!
  • General build process (John Mark Walker)
    • Want a community-driven process for regular build and test
    • Docker images, AMI, etc.  Maybe start with Bitnami?
    • Sven Marnach: the problem is how to configure and customize downloadable builds
    • Fred: Bitnami uses their own stack of infrastructure, very different than our typical stack
      • Omar: Bitnami also patches files in surprising ways
    • What would be the way to do it the right way?
    • People want a ready-to-go Docker image
      • Have people tried the regisb/FUN dockerfiles?
      • Some have tried, it's not quite ready for production, but a promising start
      • Paver vs Makefile issues
    • The goal here is to help newbies with deployment
    • edX DevOps would like to move logic into Makefiles and then use those from Ansible or Dockerfiles
    • Corey will make a DevOps Hopes and Dreams wiki page to lay out their best thoughts now about the path forward
    • Brian Beggs will link to a Platform "roadmap" page also....
  • Django 1.11 upgrade (Brian Beggs)
    • Going to production on Thursday this week
      • An index on auth_user has to be rebuilt due to a column length change
      • A waffle flag will prevent updates to auth_user during the migration
      • A few minutes of downtime at the end of the migration
      • Migrating from 1.8 to Django 1.11 has a defect that forces all the indexes on the auth_user table to be rebuilt
        • Django has a bug report about it
        • We'll do an intermediate migration to 1.10 to avoid the bug
    • Python 3 upgrade process will begin soon
      • Will probably take 18-24 months
      • Energize the community somehow?
    • Tox and travis are pervasive now, to help with these transition efforts
  • Hawthorn
    • Will not have an intermediate migration to 1.10
    • Brian's guess: 2MM rows, 10's of minutes?
  • No labels