Skip to content

Latest commit

 

History

History
472 lines (405 loc) · 17.4 KB

DEVNETS.md

File metadata and controls

472 lines (405 loc) · 17.4 KB
Raw

Deploying Devnets

In the world of Avalanche, we refer to short-lived, test Subnets as Devnets.

Step 1: Install avalanche-ops

avalanche-ops provides a command-line interface to setup nodes and install Custom VMs on both custom networks and on Fuji using AWS CloudFormation.

You can view a full list of pre-built binaries on the latest release page.

Option 1: Install avalanche-ops on Mac

rm -f /tmp/avalancheup-aws
wget "https://github.com/ava-labs/avalanche-ops/releases/download/latest/avalancheup-aws.aarch64-apple-darwin"
mv ./avalancheup-aws.aarch64-apple-darwin /tmp/avalancheup-aws
chmod +x /tmp/avalancheup-aws
/tmp/avalancheup-aws --help

Option 2: Install avalanche-ops on Linux

rm -f /tmp/avalancheup-aws
wget "https://github.com/ava-labs/avalanche-ops/releases/download/latest/avalancheup-aws.x86_64-linux-gnu"
mv ./avalancheup-aws.x86_64-linux-gnu /tmp/avalancheup-aws
chmod +x /tmp/avalancheup-aws
/tmp/avalancheup-aws --help

Step 2: Install and Configure aws-cli

Next, install the AWS CLI. This is used to manipulate CloudFormation.

Once you've installed the AWS CLI, run aws configure to set the access key to use while deploying your devnet.

Step 3: Install token-cli

export ARCH_TYPE=$(uname -m)
echo ${ARCH_TYPE}
export OS_TYPE=$(uname | tr '[:upper:]' '[:lower:]')
echo ${OS_TYPE}
export HYPERSDK_VERSION="0.0.7"
rm -f /tmp/token-cli
wget "https://github.com/ava-labs/hypersdk/releases/download/v${HYPERSDK_VERSION}/hypersdk_${HYPERSDK_VERSION}_${OS_TYPE}_${ARCH_TYPE}.tar.gz"
mkdir tmp-hypersdk
tar -xvf hypersdk_${HYPERSDK_VERSION}_${OS_TYPE}_${ARCH_TYPE}.tar.gz -C tmp-hypersdk
rm -rf hypersdk_${HYPERSDK_VERSION}_${OS_TYPE}_${ARCH_TYPE}.tar.gz
mv tmp-hypersdk/token-cli /tmp/token-cli
rm -rf tmp-hypersdk

Step 4: Download tokenvm

tokenvm is currently compiled with GOAMD=v1. If you want to significantly improve the performance of cryptographic operations, you should consider building with v3+.

export HYPERSDK_VERSION="0.0.7"
rm -f /tmp/tokenvm
wget "https://github.com/ava-labs/hypersdk/releases/download/v${HYPERSDK_VERSION}/hypersdk_${HYPERSDK_VERSION}_linux_amd64.tar.gz"
mkdir tmp-hypersdk
tar -xvf hypersdk_${HYPERSDK_VERSION}_linux_amd64.tar.gz -C tmp-hypersdk
rm -rf hypersdk_${HYPERSDK_VERSION}_linux_amd64.tar.gz
mv tmp-hypersdk/tokenvm /tmp/tokenvm
rm -rf tmp-hypersdk

Note: We must install the linux build because that is compatible with the AWS deployment target. If you use Graivtron CPUs, make sure to use arm64 here.

Step 5: Plan Local Network Deploy

Now we can spin up a new network of 6 nodes with some defaults:

  • avalanche-ops supports Graviton-based processors (ARM64). Use --arch-type arm64 to run nodes in ARM64 CPUs.
  • avalanche-ops supports EC2 Spot instances for cost savings. Use --instance-mode=spot to run instances in spot mode.
  • avalanche-ops supports multi-region deployments. Use --auto-regions 3 to distribute node across 3 regions.
/tmp/avalancheup-aws default-spec \
--arch-type amd64 \
--rust-os-type ubuntu20.04 \
--anchor-nodes 3 \
--non-anchor-nodes 3 \
--regions us-west-2 \
--instance-mode=on-demand \
--instance-types=c5.4xlarge \
--ip-mode=ephemeral \
--metrics-fetch-interval-seconds 60 \
--network-name custom \
--avalanchego-release-tag v1.10.1 \
--create-dev-machine \
--keys-to-generate 5

The default-spec (and apply) command only provisions nodes, not Custom VMs. The Subnet and Custom VM installation are done via install-subnet-chain sub-commands that follow.

NOTE: The --auto-regions 3 flag only lists the pre-defined regions and evenly distributes anchor and non-anchor nodes across regions in the default spec output. It is up to the user to change the regions and spec file based on the regional resource limits (e.g., pick the regions with higher EIP limits). To see what regions available in your AWS account, simply run the aws account list-regions command, or look at the dropdown menu of your AWS console.

Profiling avalanchego

If you'd like to profile avalanchego's CPU and RAM, provide the following flags to the command above:

avalancheup-aws default-spec \
...
--avalanchego-profile-continuous-enabled \
--avalanchego-profile-continuous-freq 1m \
--avalanchego-profile-continuous-max-files 10

Using Custom avalanchego Binaries

The default command above will download the avalanchego public release binaries from GitHub. To test your own binaries, use the following flags to upload to S3. These binaries must be built for the target remote machine platform (e.g., build for aarch64 and Linux to run them in Graviton processors):

avalancheup-aws default-spec \
...
--upload-artifacts-avalanchego-local-bin ${AVALANCHEGO_BIN_PATH}

It is recommended to specify your own artifacts to avoid flaky github release page downloads.

Restricting Instance Types

By default, avalanche-ops will attempt to use all available instance types of a given size (scoped by --instance-size) in a region in your cluster. If you'd like to restrict which instance types are used (and override --instance-size), you can populate the --instance-types flag. You can specify a single instance type (--instance-types=c5.2xlarge) or a comma-separated list (--instance-types=c5.2xlarge,m5.2xlarge).

avalanchego will use at least <expected block size> * (2048[bytesToIDCache] + 2048[decidedBlocksCache]) for caching blocks. This overhead will be significantly reduced when this issue is resolved.

Increasing Rate Limits

If you are attempting to stress test the Devnet, you should disable CPU, Disk, and Bandwidth rate limiting. You can do this by adding the following lines to avalanchego_config in the spec file:

avalanchego_config:
  ...
  proposervm-use-current-height: true
  throttler-inbound-validator-alloc-size: 10737418240
  throttler-inbound-at-large-alloc-size: 10737418240
  throttler-inbound-node-max-processing-msgs: 100000
  throttler-inbound-bandwidth-refill-rate: 1073741824
  throttler-inbound-bandwidth-max-burst-size: 1073741824
  throttler-inbound-cpu-validator-alloc: 100000
  throttler-inbound-disk-validator-alloc: 10737418240000
  throttler-outbound-validator-alloc-size: 10737418240
  throttler-outbound-at-large-alloc-size: 10737418240
  snow-mixed-query-num-push-vdr: 10
  consensus-on-accept-gossip-validator-size: 10
  consensus-on-accept-gossip-non-validator-size: 0
  consensus-on-accept-gossip-peer-size: 10
  consensus-accepted-frontier-gossip-peer-size: 0
  consensus-app-concurrency: 512
  network-compression-type: none

Supporting All Metrics

By default, avalanche-ops does not support ingest all metrics into AWS CloudWatch. To ingest all metrics, change the configured filters in upload_artifacts.prometheus_metrics_rules_file_path to:

filters:
  - regex: ^*$

Step 6: Apply Local Network Deploy

The default-spec command itself does not create any resources, and instead outputs the following apply and delete commands that you can copy and paste:

# first make sure you have access to the AWS credential
aws sts get-caller-identity

# "avalancheup-aws apply" would not work...
# An error occurred (ExpiredToken) when calling the GetCallerIdentity operation: The security token included in the request is expired

# "avalancheup-aws apply" will work with the following credential
# {
#   "UserId": "...:[email protected]",
#   "Account": "...",
#   "Arn": "arn:aws:sts::....:assumed-role/name/[email protected]"
# }
# run the following to create resources
vi /home/ubuntu/aops-custom-****-***.yaml

avalancheup-aws apply \
--spec-file-path /home/ubuntu/aops-custom-****-***.yaml

# run the following to delete resources
/tmp/avalancheup-aws delete \
--delete-cloudwatch-log-group \
--delete-s3-objects \
--delete-ebs-volumes \
--delete-elastic-ips \
--spec-file-path /home/ubuntu/aops-custom-****-***.yaml

That is, apply creates AWS resources, whereas delete destroys after testing is done.

If you see the following command, that is expected (it means avalanche-ops is reusing a S3 bucket it previously created):

[2023-03-23T23:49:01Z WARN  aws_manager::s3] bucket already exists so returning early (original error 'service error')

SECURITY: By default, the SSH and HTTP ports are open to public. Once you complete provisioning the nodes, go to EC2 security group to restrict the inbound rules to your IP.

NOTE: In rare cases, you may encounter aws-sdk-rust#611 where AWS SDK call hangs, which blocks node bootstraps. If a node takes too long to start, connect to that instance (e..g, use SSM sesson from your AWS console), and restart the agent with the command sudo systemctl restart avalanched-aws.

Step 7: Generate Configs

Now that the network and nodes are up, let's install two subnets, each of which runs its own tokenvm. Use the following commands to do so (similar to scripts/run.sh):

rm -rf /tmp/avalanche-ops
mkdir /tmp/avalanche-ops

cat <<EOF > /tmp/avalanche-ops/tokenvm-subnet-config.json
{
  "proposerMinBlockDelay": 0,
  "gossipOnAcceptPeerSize": 0,
  "gossipAcceptedFrontierPeerSize": 0
}
EOF
cat /tmp/avalanche-ops/tokenvm-subnet-config.json

cat <<EOF > /tmp/avalanche-ops/allocations.json
[{"address":"token1rvzhmceq997zntgvravfagsks6w0ryud3rylh4cdvayry0dl97nsjzf3yp", "balance":1000000000000000}]
EOF

/tmp/token-cli genesis generate /tmp/avalanche-ops/allocations.json \
--genesis-file /tmp/avalanche-ops/tokenvm-genesis.json \
--max-block-units 400000000 \
--window-target-units 100000000000 \
--window-target-blocks 40
cat /tmp/avalanche-ops/tokenvm-genesis.json

cat <<EOF > /tmp/avalanche-ops/tokenvm-chain-config.json
{
  "mempoolSize": 10000000,
  "mempoolPayerSize": 10000000,
  "mempoolExemptPayers":["token1rvzhmceq997zntgvravfagsks6w0ryud3rylh4cdvayry0dl97nsjzf3yp"],
  "streamingBacklogSize": 10000000,
  "gossipMaxSize": 32768,
  "gossipProposerDepth": 1,
  "buildProposerDiff": 10,
  "verifyTimeout": 5,
  "trackedPairs":["*"],
  "logLevel": "info",
  "preferredBlocksPerSecond": 4
}
EOF
cat /tmp/avalanche-ops/tokenvm-chain-config.json

Profiling tokenvm

If you'd like to profile tokenvm's CPU and RAM, add the following line to the tokenvm-chain-config.json file above:

{
  ...
  "continuousProfilerDir": "/var/log/tokenvm-profile"
}

Step 8: Install Chains

You can run the following commands to spin up 2 tokenvm Devnets. Make sure to replace the *** fields, IP addresses, key, and node-ids-to-instance-ids with your own data:

/tmp/avalancheup-aws install-subnet-chain \
--log-level info \
--s3-region us-west-2 \
--s3-bucket <TODO> \
--s3-key-prefix <TODO> \
--chain-rpc-url <TODO> \
--key <TODO> \
--primary-network-validate-period-in-days 16 \
--subnet-validate-period-in-days 14 \
--subnet-config-local-path /tmp/avalanche-ops/tokenvm-subnet-config.json \
--subnet-config-remote-dir /data/avalanche-configs/subnets \
--vm-binary-local-path /tmp/tokenvm \
--vm-binary-remote-dir /data/avalanche-plugins \
--chain-name tokenvm1 \
--chain-genesis-path /tmp/avalanche-ops/tokenvm-genesis.json \
--chain-config-local-path /tmp/avalanche-ops/tokenvm-chain-config.json \
--chain-config-remote-dir /data/avalanche-configs/chains \
--avalanchego-config-remote-path /data/avalanche-configs/config.json \
--ssm-doc <TODO> \
--target-nodes <TODO>

Example Params

--ssm-docs '{"us-west-2":"aops-custom-202304-2ijZSP-ssm-install-subnet-chain"...
--target-nodes '{"NodeID-HgAmXckXzDcvxv9ay71QT9DDtEKZiLxP4":{"region":"eu-west-1","machine_id":"i-0e68e051796b88d16"}...

Step 9: Initialize token-cli

You can import the demo key and the network configuration from avalanche-ops using the following commands:

/tmp/token-cli key import demo.pk
/tmp/token-cli chain import-ops <chainID> <avalanche-ops spec file path>
/tmp/token-cli key balance --check-all-chains

If you previously used token-cli, you may want to delete data you previously ingested into it. You can do this with the following command:

rm -rf .token-cli

Step 10: Start Integrated Block Explorer

To view activity on each Subnet you created, you can run the token-cli's integrated block explorer. To do this, run the following command:

/tmp/token-cli chain watch --hide-txs

If you don't plan to load test the devnet, you may wush to just run the following command to get additional transaction details:

/tmp/token-cli chain watch

Step 11: Run Load

Once the network information is imported, you can then run the following command to drive an arbitrary amount of load:

/tmp/token-cli spam run

Limiting Inflight Txs

To ensure you don't create too large of a backlog on the network, you can add run the following command (defaults to 72000):

/tmp/token-cli spam run --max-tx-backlog 5000

[Optional] Step 12: Viewing Logs

  1. Open the AWS CloudWatch product on your AWS Console
  2. Click "Logs Insights" on the left pane
  3. Use the following query to view all logs (in reverse-chronological order) for all nodes in your Devnet:
fields @timestamp, @message, @logStream, @log
| filter(@logStream not like "avalanche-telemetry-cloudwatch.log")
| filter(@logStream not like "syslog")
| sort @timestamp desc
| limit 20

Note: The "Log Group" you are asked to select should have a similar name as the spec file that was output earlier.

[Optional] Step 13: Viewing Metrics

Option 1: AWS CloudWatch

  1. Open the AWS CloudWatch product on your AWS Console
  2. Click "All Metrics" on the left pane
  3. Click the "Custom Namespace" that matches the name of the spec file

Option 2: Prometheus

To view metrics, first download and install Prometheus using the following commands:

rm -f /tmp/prometheus
wget https://github.com/prometheus/prometheus/releases/download/v2.43.0/prometheus-2.43.0.darwin-amd64.tar.gz
tar -xvf prometheus-2.43.0.darwin-amd64.tar.gz
rm prometheus-2.43.0.darwin-amd64.tar.gz
mv prometheus-2.43.0.darwin-amd64/prometheus /tmp/prometheus
rm -rf prometheus-2.43.0.darwin-amd64

Once you have Prometheus installed, run the following command to auto-generate a configuration file (placed in /tmp/prometheus.yaml by default):

/tmp/token-cli prometheus generate

In a separate terminal, then run the following command to view collected metrics:

/tmp/prometheus --config.file=/tmp/prometheus.yaml

[OPTIONAL] Step 14: SSH Into Nodes

You can SSH into any machine created by avalanche-ops using the SSH key automatically generated during the apply command. The commands for doing so are emitted during apply and look something like this:

ssh -o "StrictHostKeyChecking no" -i aops-custom-202303-21qJUU-ec2-access.key [email protected]

[OPTIONAL] Step 15: Deploy Another Subnet

To test Avalanche Warp Messaging, you must be running at least 2 Subnets. To do so, just replicate the command you ran above with a different --chain-name (and a different set of validators):

/tmp/avalancheup-aws install-subnet-chain \
--log-level info \
--s3-region us-west-2 \
--s3-bucket <TODO> \
--s3-key-prefix <TODO> \
--chain-rpc-url <TODO> \
--key <TODO> \
--primary-network-validate-period-in-days 16 \
--subnet-validate-period-in-days 14 \
--subnet-config-local-path /tmp/avalanche-ops/tokenvm-subnet-config.json \
--subnet-config-remote-dir /data/avalanche-configs/subnets \
--vm-binary-local-path /tmp/tokenvm \
--vm-binary-remote-dir /data/avalanche-plugins \
--chain-name tokenvm2 \
--chain-genesis-path /tmp/avalanche-ops/tokenvm-genesis.json \
--chain-config-local-path /tmp/avalanche-ops/tokenvm-chain-config.json \
--chain-config-remote-dir /data/avalanche-configs/chains \
--avalanchego-config-remote-path /data/avalanche-configs/config.json \
--ssm-doc <TODO> \
--target-nodes <TODO>

Example Params

--ssm-docs '{"us-west-2":"aops-custom-202304-2ijZSP-ssm-install-subnet-chain"...
--target-nodes '{"NodeID-HgAmXckXzDcvxv9ay71QT9DDtEKZiLxP4":{"region":"eu-west-1","machine_id":"i-0e68e051796b88d16"}...

Deploy TokenVM in Fuji network with avalanche-ops

Same as above, except you use --network-name fuji and do not need anchor nodes:

avalancheup-aws default-spec \
--arch-type amd64 \
--rust-os-type ubuntu20.04 \
--non-anchor-nodes 6 \
--regions us-west-2 \
--instance-mode=on-demand \
--instance-size=2xlarge \
--ip-mode=elastic \
--metrics-fetch-interval-seconds 60 \
--network-name fuji

Make sure the nodes are in sync with the chain state before installing subnets/chains with avalancheup-aws install-subnet-chain. You can check the status of the nodes either via HTTP /health endpoints or CloudWatch logs.

Troubleshooting

undefined: Message

If you get the following error, make sure to install gcc before running ./scripts/build.sh:

# github.com/supranational/blst/bindings/go
../../../go/pkg/mod/github.com/supranational/[email protected]/bindings/go/rb_tree.go:130:18: undefined: Message