...
What new products, applications, services, etc have we built since Ginkgo?
- Catalog service
- Django is in the process of being upgraded to 1.11.X
- Credentials Service
- Django has been updated upgraded to 1.911.xX
- E-Commerce Service
- Django has been upgraded to 1.910.x.X
- Django Oscar has been upgraded to 1.4. (See deployment issues note below.)
- ElastichSearch 1.5 Upgrade is in progress will hopefully land soon(Contact:Feanil)
- Webpack is now supported in edx-platform
...
- ElasticSearch will be upgraded, probably to 1.5 which is what we use in production. This will coincide with changes to the forums service to support the newer version.
- Robert Raposa: In addition to migration documentation, we should remind about "rake search:initialize" and "rake search:validate_index".
- Credentials Service
- The service now requires Python 3.5
- The service has been upgraded to Django 1.11.x
- E-Commerce Service
- The service has been upgraded to Django 1.10.x.
- This change includes a migration that affects the user table. If your users table is large, consider faking migration
core 0032.
- This change includes a migration that affects the user table. If your users table is large, consider faking migration
- Django Oscar has been upgraded to 1.4. (The steps below only apply to existing installations, and can be ignored for new installations.)
- This upgrade requires faking migrations for the
thumbnailapp:./manage.py migrate thumbnail --fake Site maintainers should be aware that one of the migrations includes a change on the guest_email column in the orders table. If your orders table is large 1M+ rows, this migration may lock the table for an extended amount of time. The E-Commerce Service does not normally use the guest_email column. If you have not modified your system to use this column, and wish to avoid the table lock, it is recommended that you fake this migration:
./manage.py migrate orders 0012./manage.py migrate orders 0013 --fake
- This upgrade requires faking migrations for the
- The service has been upgraded to Django 1.10.x.
- Catalog Service
- The service is in the process of been upgraded to Django 1.11.X
- Waffle is used by many repositories to control feature rollout
- Will devtack be docker based, or will we still need vagrant?
- Will native/fullstack require docker?
- Will catalog service be required?
- Are there required upgrades for Django, pip, ...
- Will there be a significant change to the asset pipeline in time for Ginkgo? (Probably not but something to keep an eye on)
- Upgrade to RabbitMQ https://github.com/edx/configuration/pull/3297
- 3.2.1 → 3.6.9
- Upgrading in place on devstacks may be fine (it appears rabbit will upgrade structures on disk when it starts back up)
- Upgrading a cluster is more fun depending on downtime options https://www.rabbitmq.com/clustering.html
- We're using https://www.rabbitmq.com/shovel.html
- Insights
We're planning on upgrading Insights to Django 1.11. As part of this upgrade, we need to follow a delicate procedure to update python-social-auth from the old version in Eucalyptus. Essentially, what we think needs to be scripted in the upgrade is a sequence of migrations documented in python-social-auth/MIGRATING_TO_SOCIAL:
- upgrade to python-social-auth==0.2.21
- run migrations
- upgrade edx-auth-backends, which in turn upgrades a bunch of social-auth-* packages
- run migrations
- In other words, upgrade Insights to version 0.33.0, run migrations, then upgrade Insights to the Ginkgo release, and run migrations again.
...