Hi Ned, everybody,
First, congratulations on the pre-release!
Using OpenCraft.Hosting, we've been testing the process of
* deploying production instances that run Eucalyptus RC1, and
* upgrading production instances from Dogwood to Eucalyptus RC1.
Deploying Eucalyptus RC1 worked really well! With our setup, we only
needed to add a small number of changes on top of the
open-release/eucalyptus/1rc1 release. For most of these changes, we
already have PRs open to submit them to the onfiguration and
edx-platform repos (they are not specific to Eucalyptus; we were using
them for our Dogwood instances as well). The remaining changes are minor
and specific to our setup.
Upgrading from Dogwood to Eucalyptus RC1 went mostly fine, but we did
have to run some of the commands from the update.sh script manually to
complete the process (see below).
For context, our upgrade process is to provision a new server for an
existing instance from scratch using the edx_sandbox.yml playbook
(duplicating the instance's settings), and then switching over the DNS.
The instance uses MySQL and Mongo databases located on a different server.
With this approach, provisioning goes fine up to the
"oauth_client_setup" role, which fails with
"django.db.utils.OperationalError: (1054, "Unknown column
'oauth2_client.logout_uri' in 'field list'")":
https://gist.github.com/itsjeyd/f824918df495586dd21225985cd67ee1
To end up with a working server, we need to run
/edx/bin/edxapp-migrate-lms --fake oauth2_provider zero
/edx/bin/edxapp-migrate-lms --fake-initial
on the new server and then provision another VM for the same instance.
---
Another thing that was nice to see was that switching from using
"courseware_studentmodulehistory" to
"coursewarehistoryextended_studentmodulehistoryextended" for CSMH data
was really easy. For the setup where existing data remains in
"courseware_studentmodulehistory" and new data gets written to
"coursewarehistoryextended_studentmodulehistoryextended", we only had to add
EDXAPP_FEATURES:
ENABLE_CSMH_EXTENDED: true
ENABLE_READING_FROM_MULTIPLE_HISTORY_TABLES: true
to an instance's settings before provisioning a new server. No manual
intervention necessary! :)
---
Thanks for the great work on this release!
--
Tim
@OpenCraft <http://opencraft.com/>
On 07/23/2016 12:27 AM, Ned Batchelder wrote:
Hello Open edX adopters,
The next Open edX release will be Eucalyptus. We have a prerelease
available now for limited use. Eucalyptus 1 RC 1 is the first release
candidate of the first Eucalyptus release (we've changed the numbering
scheme slightly since Dogwood).
This prerelease is only available for fullstack and native installs.
Devstack is not yet supported. An overview of the installation
options is here:
https://openedx.atlassian.net/wiki/display/OpenOPS/Open+edX+Installation+Options
If you want to try this pre-release, please do not do it on a live
machine, or risk live data with it. The OPENEDX_RELEASE tag name to
use is *open-release/eucalyptus/1rc1* . If you want to upgrade from a
previous install, the existing instructions work, but the migrate.sh
script has been renamed to upgrade.sh to better match its function.
Before we release a real Eucalyptus, we will be adding a few more
fixes, and want to hear from you if you discover problems with this
pre-release. We even want to hear if you don't encounter problems! :)
Thanks,
--Ned.
--
You received this message because you are subscribed to the Google
Groups "General Open edX discussion" group.
To view this discussion on the web visit
https://groups.google.com/d/msgid/edx-code/CAGtJPNNv_3QnXO%2Bp7AYt0QMR%3DJMJNbtXMSkK6tNu9qABmy%2BoOA%40mail.gmail.com
<https://groups.google.com/d/msgid/edx-code/CAGtJPNNv_3QnXO%2Bp7AYt0QMR%3DJMJNbtXMSkK6tNu9qABmy%2BoOA%40mail.gmail.com?utm_medium=email&utm_source=footer>.
--
You received this message because you are subscribed to the Google Groups "General
Open edX discussion" group.
To view this discussion on the web visit
https://groups.google.com/d/msgid/edx-code/ec08466b-356e-c6e3-c1d5-7371b5bcf983%40edx.org.
