Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Upgrade to 0.4.0 [documentation] #1048

Closed
Tracked by #1009
danlester opened this issue Feb 11, 2022 · 1 comment · Fixed by #1087
Closed
Tracked by #1009

Upgrade to 0.4.0 [documentation] #1048

danlester opened this issue Feb 11, 2022 · 1 comment · Fixed by #1087

Comments

@danlester
Copy link
Contributor

danlester commented Feb 11, 2022

We need to work out communications to help upgrade to version 0.4.0. This could be a combination of release notes and docs.

There are general upgrade docs ready to be released but these are not specific to 0.4.0 which may need special consideration especially in light of #1040.

My suggested process

Assumes #1047 and #957 have been merged.

Backup and move existing URL

Using the old version of qhub:

  1. Perform manual backups (Complication: after release the docs will include details about Keycloak, but the only thing relevant will just be Zipping up the NFS files).

  2. Rename the existing domain

This will allow the existing cluster to remain alive in case it is needed, but the idea would be not to have it in use from now on.

In the qhub-config.yaml for example:

project_name: myqhub
domain: qhub.myproj.com

could become:

project_name: myqhub
domain: qhub-old.myproj.com

Run qhub deploy using the existing (old) version of qhub.

Upgrade the config file

Now we need to go back to the original qhub-config.yaml file which contained the original domain.

Run the general upgrade docs process up to the point before redeployment.

Actually, I've noticed that steps 5 and 6 are specific to the 0.4.0 upgrade, so should probably be marked as such. They could be moved to 0.4.0-specific documentation, but of course they may also be required if someone upgrades directly from 0.3.14 -> 0.4.1.

You should end up with a new qhub-config.yaml file and a qhub-users-import.json.

Rename the project

Need to rename the project to avoid clashes with the existing (old) cluster. The domain should remain as the preferred main one that was always in use previously.

For example:

project_name: myqhub
domain: qhub.myproj.com

could become:

project_name: myqhubnew
domain: qhub.myproj.com

Deploy and restore backups

When attempting to redeploy, it should first fail due to prevent_deploy flag needing to be removed for safety.

After deployment, carry out steps 5 and 6 of the general upgrade docs (OAuth URL updates if relevant, plus inport Keycloak users).

Change the Keycloak root password at /auth URL - don't update the qhub-config.yaml file to reflect this.

Restore NFS from backup - docs needed...

Also need to chown all uids immediately after restore while the 'restore pod' is mounted:

chown -R 1000:100 /mnt/home
@magsol
Copy link
Contributor

magsol commented Feb 16, 2022

Too technical for release notes, too specific for upgrade notes. Where should this go in the docs?

@trallard trallard moved this to Needs Triage 🔍 in QHub Project Mangement 🚀 Feb 17, 2022
@trallard trallard pinned this issue Feb 21, 2022
@trallard trallard moved this from Needs Triage 🔍 to In Progress 🏃🏽‍♀️ in QHub Project Mangement 🚀 Feb 21, 2022
@trallard trallard unpinned this issue Feb 22, 2022
Repository owner moved this from In Progress 🏃🏽‍♀️ to Done 💪🏾 in QHub Project Mangement 🚀 Feb 24, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants