Restore pavics_thredds.ipynb change for Magpie upgrade strike II #218
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…new-broken-magpie-so-we-can-test-magpie-fix
|
Check out this pull request on See visual diffs & provide feedback on Jupyter Notebooks. Powered by ReviewNB |
… is done with Magpie upgrade
…utput change on each run (for Jenkins)
huard
approved these changes
Apr 19, 2021
tlvu
added a commit
to bird-house/birdhouse-deploy
that referenced
this pull request
Apr 19, 2021
…e-upgrade-so-we-can-work-on-a-fix Magpie upgrade strike II Strike II of this original PR #107. Matching notebook fix Ouranosinc/pavics-sdi#218 Performed test upgrade on staging (Medus) using prod (Boreas) Magpie DB, everything went well and Jenkins passed (http://jenkins.ouranos.ca/job/ouranos-staging/job/medus.ouranos.ca/80/parameters/). This Jenkins build uses the corresponding branch in Ouranosinc/pavics-sdi#218 and with `TEST_MAGPIE_AUTH` enabled. Manual upgrade migration procedure: 1. Save `/data/magpie_persist` folder from prod `pavics.ouranos.ca`: `cd /data; tar czf magpie_persist.prod.tgz magpie_persist` 2. scp `magpie_persist.prod.tgz` to `medus` 3. login to `medus` 4. `cd /path/to/birdhouse-deploy/birdhouse` 3. `./pavics-compose.sh down` 4. `git checkout master` 5. `cd /data` 2. `rm -rf magpie_persist` 3. `tar xzf magpie_persist.prod.tgz` # restore Magpie DB with prod version 4. `cd /path/to/birdhouse-deploy/birdhouse` 5. `./pavics-compose.sh up -d` 3. Update `env.local` `MAGPIE_ADMIN_PASSWORD` with prod passwd for Twitcher to be able to access Magpie since we juste restore the Magpie DB from prod 4. `./pavics-compose.sh restart twitcher` # for Twitcher to get new Magpie admin passwd 4. Baseline working state: trigger Jenkins test suite, ensure all pass except `pavics_thredds.ipynb` that requires new Magpie 5. Baseline working state: view existing services permissions on group Anonymous (https://medus.ouranos.ca/magpie/ui/groups/anonymous/default) 6. `git checkout restore-previous-broken-magpie-upgrade-so-we-can-work-on-a-fix` # This current branch 7. `./pavics-compose.sh up -d` # upgrade to new Magpie 8. `docker logs magpie`: check no DB migration error 9. Trigger Jenkins test suite again
tlvu
deleted the
restore-change-for-new-broken-magpie-so-we-can-test-magpie-fix
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Matching PAVICS deployment PR bird-house/birdhouse-deploy#142
See original PR for more info #209