-
Visit https://packit-dev.dide.ic.ac.uk/ and take not of all the instances you want to migrate.
-
Check the group and permission structure of each instance. We don't migrate those so they will need to be recreated.
-
Export all the instances into separate tarballs using the following command (once per instance):
ssh root@packit-dev.dide.ic.ac.uk tar -C /var/lib/outpack/reside-dev -Jc .outpack > reside-dev.tar.xz -
Destroy and re-create the VM
- Remote desktop onto the host machine (
wpia-reside1) - Open command prompt
- Change directory to
D:\reside-hyperv-scripts\packit-dev - Run
vagrant destroy - Run
vagrant up - Leave the Windows host
- Remote desktop onto the host machine (
-
Upgrade Ubuntu from 22.04 to 24.04
- SSH into the new VM
ssh vagrant@wpia-packit-dev.dide.ic.ac.uk - Run
sudo apt-get dist-upgrade - Reboot the VM
- Edit
/etc/update-manager/release-upgradesand setPrompt=lts - Run
sudo do-release-upgrade, say yes to everything except about overwriting the sudoers file - Let the upgrader restart when it is done
- SSH into the new VM
-
Run the initial provisioning on the machine
uv run pyinfra src/infra/inventory.py infra.run --limit wpia-packit-dev.dide.ic.ac.uk -
Restore your instance data:
cat reside-dev.tar.xz | ssh vagrant@packit-dev.dide.ic.ac.uk docker run --rm -i -v packit-outpack-reside-dev:/outpack alpine tar -C /outpack -Jx -
Configure and start packit
ssh vagrant@wpia-packit-dev.dide.ic.ac.uk cd packit-config packit configure packit-dev packit startFirst deployement may take a while to get certificates from Let's Encrypt. You can monitor progress with
docker logs -f packit-acme-buddy. -
Resync packets using the Packit admin UI
-
Notifications
You must be signed in to change notification settings - Fork 0
mrc-ide/packit-config
Folders and files
| Name | Name | Last commit message | Last commit date | |
|---|---|---|---|---|
Repository files navigation
About
No description, website, or topics provided.
Resources
Stars
Watchers
Forks
Releases
No releases published
Packages 0
No packages published