...
If you have Amazon S3 credentials:
Code Block aws --profile=edx s3 cp package.box s3://edx-static/vagrant-images/zebrwood-devstack-2016-02-17.box --acl public-read aws --profile=edx s3 cp package.box s3://edx-static/vagrant-images/zebrawood-fullstack-2016-02-17.box --acl public-read
- If you don't have Amazon S3 credentials:
- Upload the file to Google Drive
- Tell Devops, they will move it to Amazon S3.
Update box directory
Update the wiki page that lists the boxes: Open edX Releases.
- Add the new box, and a new row in the table if need be. Be careful when editing URLs that you change both the text and the link.
- Add the SHA1 hash of the box file, from "shasum package.box"
- Click the torrent URLs to make sure they work. If they 404, then the file doesn't exist, or has the wrong permissions. If you get "The s3.amazonaws.com page isn’t working. s3.amazonaws.com didn’t send any data," then click it again until it gives you a file of about 220Kb. Amazon takes a while to get the torrent file going.
In a devstack
Upload the strings to Transifex with:
| Code Block |
|---|
paver i18n_release_push |
Testing
This section is a bit disorganized. Use judiciously.
Test upgrade to master (??)
Create a devstack VM and a fullstack VM from the previous Open edX release:
| Code Block |
|---|
$ export OPENEDX_RELEASE="open-release/yucca.latest" # or whatever the previous release was.
$ vagrant up
... lots of output ...
# You don't need to make a snapshot, but it's really handy
$ VBoxManage list vms
"yucca_full_default_1451410759822_16267" {e7764d74-6f2f-49d2-8fab-4e8715272338}
"yucca_default_1452008513561_29129" {6e796982-7ed3-4dc3-9243-aacc0f47db29}
$ VBoxManage snapshot "yucca_default_1452008513561_29129" take pristine
# Later you can reset to this point with: $ VBoxManage snapshot "yucca_default_1452008513561_29129" restore pristine |
NOTE: Not sure this is good advice: For each one, try upgrading edx-platform to the "master" commit on edx-platform:
| Code Block | ||
|---|---|---|
| ||
cd /edx/app/edx_ansible/edx_ansible
sudo git checkout master
sudo git pull
cd playbooks/edx-east/
/edx/app/edx_ansible/venvs/edx_ansible/bin/ansible-playbook -i localhost, -c local edxapp.yml -e "@/edx/app/edx_ansible/server-vars.yml" |
...
In a devstack
Upload the strings to Transifex with:
| Code Block |
|---|
paver i18n_release_push |
Testing
This section is a bit disorganized. Use judiciously.
Test upgrade to master (??)
Create a devstack VM and a fullstack VM from the previous Open edX release:
| Code Block |
|---|
$ export OPENEDX_RELEASE="open-release/yucca.latest" # or whatever the previous release was.
$ vagrant up
... lots of output ...
# You don't need to make a snapshot, but it's really handy
$ VBoxManage list vms
"yucca_full_default_1451410759822_16267" {e7764d74-6f2f-49d2-8fab-4e8715272338}
"yucca_default_1452008513561_29129" {6e796982-7ed3-4dc3-9243-aacc0f47db29}
$ VBoxManage snapshot "yucca_default_1452008513561_29129" take pristine
# Later you can reset to this point with: $ VBoxManage snapshot "yucca_default_1452008513561_29129" restore pristine |
NOTE: Not sure this is good advice: For each one, try upgrading edx-platform to the "master" commit on edx-platform:
| Code Block | ||
|---|---|---|
| ||
cd /edx/app/edx_ansible/edx_ansible
sudo git checkout master
sudo git pull
cd playbooks/edx-east/
/edx/app/edx_ansible/venvs/edx_ansible/bin/ansible-playbook -i localhost, -c local edxapp.yml -e "@/edx/app/edx_ansible/server-vars.yml" |
If it fails, work with devops to figure out what's going wrong and how to fix it. Note that the above ansible command seems to only work for fullstack, since devstack doesn't have a /edx/app/edx_ansible/server-vars.yml file. Still trying to figure out how to test this with devstack.
...
| Code Block |
|---|
tag_release --doit --tag --skip-invalid --override-ref you/test/zebrawood.1rc1.1 open-release/zebrawood.1rc1 # for release candidate # or: tag_release --doit --tag --skip-invalid --override-ref you/test/zebrawood.1.1 open-release/zebrawood.1 # for release |
It's tempting to do this before creating the Vagrant box. In practice, the first time you create the Vagrant box, it will probably fail, and you'll need to make some fixes. Therefore, it's better to wait until everything works properly before you make the tagIt's tempting to do this before creating the Vagrant box. In practice, the first time you create the Vagrant box, it will probably fail, and you'll need to make some fixes. Therefore, it's better to wait until everything works properly before you make the tag.
Update box directory
Update the wiki page that lists the boxes: Open edX Releases.
- Add the new box, and a new row in the table if need be. Be careful when editing URLs that you change both the text and the link.
- Add the SHA1 hash of the box file, from "shasum package.box"
- Click the torrent URLs to make sure they work. If they 404, then the file doesn't exist, or has the wrong permissions. If you get "The s3.amazonaws.com page isn’t working. s3.amazonaws.com didn’t send any data," then click it again until it gives you a file of about 220Kb. Amazon takes a while to get the torrent file going.
Announce to the community
...