Document 'safe' hardware type used for testing

gluwa · Jan 20, 2023 · 82da234 · 82da234
1 parent 9d249eb
commit 82da234
Show file tree

Hide file tree

Showing 2 changed files with 13 additions and 0 deletions.
diff --git a/.github/workflows/runtime-upgrade.yml b/.github/workflows/runtime-upgrade.yml
@@ -134,6 +134,11 @@ jobs:
         run: |
           chmod a+x ./target/release/creditcoin-node
 
+      - name: Check if runner machine meets chain's requirements
+        continue-on-error: true
+        run: |
+          ./scripts/check-hardware.sh
+
       - name: Download try-runtime snapshots data for Creditcoin
         run: |
             echo "INFO: SNAPSHOT_URL=${{ env.SNAPSHOT_URL }}"

diff --git a/docs/miner-setup.md b/docs/miner-setup.md
@@ -4,6 +4,14 @@
 
 - Working [Docker](https://www.docker.com) installation
 
+**Notes:**
+
+For testing runtime upgrade/migrations Gluwa is using a 4 vCPU, 32 GiB RAM,
+Memory optimized virtual machine in Azure. The size spec is `Standard_E4as_v4`.
+See the `vmSize` parameter in
+[.github/runner.bicep](https://github.com/gluwa/creditcoin/blob/dev/.github/runner.bicep)
+for reference.
+
 ## Setup Steps
 
 1) In order to receive mining rewards you will need an account on the Creditcoin network. Each account has an address and a balance associated with it. The account is backed by a keypair. You can use an existing ECDSA keypair (e.g. from pre-Creditcoin 2.0) or you can generate a new keypair. You can use [subkey](https://docs.substrate.io/v3/tools/subkey/) to retrieve the account address from an existing private key (e.g. from pre-Creditcoin 2.0) or to generate a new keypair.