-
Notifications
You must be signed in to change notification settings - Fork 41
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
Release 2506
distribution
#2207
Comments
Upgrade VM in place processPrepare the upgradeMake a manual snapshot of the data disk in GCP: export SNAPSHOT_ID=mithril-release-preprod-...
export SOURCE_DISK=mithril-release-preprod-data
gcloud compute snapshots create $SNAPSHOT_ID --source-disk $SOURCE_DISK --snapshot-type STANDARD --source-disk-zone europe-west1-b Then connect to the VM: export VM=aggregator.release-preprod.api.mithril.network
ssh curry@$VM Once connected, create a temp directory: export TMP_DIR=/home/curry/tmp
mkdir -p $TMP_DIR Make a clean stop of the Cardano nodes: docker ps --format '{{.Names}}' | grep cardano > $TMP_DIR/docker-ps-cardano.txt
cat $TMP_DIR/docker-ps-cardano.txt | xargs -I '{}' docker stop '{}' Run the terraform deployment to upgrade the VMRun the deployment with the correct GitHub actions workflow that will upgrade the VM in place. Check that the data disk is properly mountedOnce the VM has been modified in place, check that all the data disk is properly mounted: lsblk | grep sdb | grep "/home/curry/data" Case 1: the disk is properly mountedIf the previous command returns an entry, the data disk is mounted to the data folder and there is nothing more to do. Case 2: the disk is not properly mountedOtherwise, the data disk must be mounted. First, stop all the remaining containers: docker stop reverse-proxy
docker ps --format '{{.Names}}' > $TMP_DIR/docker-ps-all.txt
cat $TMP_DIR/docker-ps-all.txt | xargs -I '{}' docker stop '{}' Then mount the data disk to the data folder: sudo mount -o discard,defaults /dev/sdb /home/curry/data/ And make sure that the disk is now correctly mounted: lsblk | grep sdb | grep "/home/curry/data" Then restart all the containers: cat $TMP_DIR/docker-ps-cardano.txt | xargs -I '{}' docker start '{}'
docker start reverse-proxy CleanupDelete the temporary folder: rm -rf $TMP_DIR |
Why
In order to deploy new features, improvements and bug fixes, we need to release a new distribution.
What
Create and release a new distribution
2506
Important
ubuntu-20
builders in CI #2216release-preprod
VM frome2-highmem-2
toe2-highmem-4
10.1.4
pre-release-preview
release-preprod
release-mainnet
pre-release-preview
release-preprod
release-mainnet
pre-release-preview
release-preprod
release-mainnet
Distribution +1:
Note
How
Phase 1: Prepare distribution
crates.io
(mithril-common
,mithril-client
)networks.json
must be updated following the runbookCHANGELOG.md
(set the distribution version)Phase 2: Rollout pre-release distribution
2506.0-pre
pre-release distribution on thepre-release-preview
networkpre-release-preview
with processpre-release-preview
is working as expectedpre-release-preview
next
have been published on npm registry3
signers running the new version (could be more if era change is tested) over at least2
epochsPhase 3: Rollout release distribution
2506.0
release distribution on thepre-release-preview
networkpre-release-preview
is working as expectedrelease-preprod
as the VM will be updated with process2506.0
release-mainnet
with processrelease-mainnet
is working as expectedrelease-preprod
has been updated properly with processrelease-preprod
with processrelease-preprod
is working as expectedrelease-preprod
if neededlatest
have been published on npm registryrelease-mainnet
release-preprod
CHANGELOG.md
(updating the release date of the distribution)2506
The text was updated successfully, but these errors were encountered: