Skip to content

Aleph-vm 0.4.0 alpha1

Pre-release
Pre-release
Compare
Choose a tag to compare
@hoh hoh released this 26 Jan 11:02
· 175 commits to main since this release
0.4.0a1
c171880
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.

We are excited to share a first look into the next version of our computing platform !

ℹ️ alpha release: This new release introduces many new features that we would like to share with the community as soon as possible, but may not be rock solid yet. Community feedback on early releases is very important to us, especially with a large and diverse ecosystem of nodes.

Improvements and New Features

  • We've introduced the capability to start VM Instances via QEMU in addition to Firecracker.
  • Users can use Pay-as-you-go instead or in addition to holding token to pay for virtual machines.
  • A revamped diagnostic page shows more information and documentation for troubleshooting.
  • Operators can now configure the sampling rate for Sentry's performance analysis via the settings.

Fixes

  • Instances won't be stopped or restarted when updating the VM orchestrator.
  • Instances are automatically restarted if the node reboots.
  • Holding token or using the pay-as-you-go is now required for all VMs.
  • Better CORS handling and 404 pages on internal paths.
  • And many small bug fixes...

How to upgrade

1. Upgrade the packages

This part did not change, download and install the new package as usual.

On Debian 11 (Bullseye):

rm -f /opt/aleph-vm.debian-11.deb
wget -P /opt https://github.com/aleph-im/aleph-vm/releases/download/0.4.0a1/aleph-vm.debian-11.deb
apt install /opt/aleph-vm.debian-11.deb

On Debian 12 (Bookworm):

rm -f /opt/aleph-vm.debian-12.deb
wget -P /opt https://github.com/aleph-im/aleph-vm/releases/download/0.4.0a1/aleph-vm.debian-12.deb
apt install /opt/aleph-vm.debian-12.deb

On Ubuntu 22.04 (Jammy Jellyfish):

rm -f /opt/aleph-vm.ubuntu-22.04.deb
sudo wget -P /opt https://github.com/aleph-im/aleph-vm/releases/download/0.4.0a1/aleph-vm.ubuntu-22.04.deb
sudo apt install /opt/aleph-vm.ubuntu-22.04.deb

2. Enable Pay-as-you-go (optional)

In order to enable Pay-as-you-go on our Compute Resource Node, you must:

  1. Have IPv6 Egress configured and working.
  2. Add a STREAM REWARD ADDRESS on both the node account page and the settings file.

2.a. Configure IPv6 Egress

Pay-as-you-go requires virtual machines to have IPv6 connectivity from the host.

According to the IPv6 specifications, a system is expected to receive an IPv6 with a /64 mask and all addresses inside that mask
should simply be routed to the host.

Assuming hosting provider follows the specification, the procedure is the following:

  1. Obtain the IPv6 address of your node.
  2. Remove the trailing number after :: if present, for example 2a01:4f8:171:787::2/64 becomes 2a01:4f8:171:787::/64.
  3. Add the IPv6 range you obtained under the setting ALEPH_VM_IPV6_ADDRESS_POOL in the file /etc/aleph-vm/supervisor.env on the node. Example: ALEPH_VM_IPV6_ADDRESS_POOL="2a01:4f8:171:787::/64".
  4. Restart the node with systemctl restart aleph-vm-supervisor.service
  5. Confirm that everything is OK by opening the path /status/check/ipv6 on the CRN's URL

⚠️ While most hosting providers do exactly this, some tend to not do that. Everything worked fine in our tests on Hetzner, but we had to enable NDP Proxy in order to support OVH and we faced weird setups on some other providers.

2.b. Configure the stream reward address

  1. Create an Avalanche (AVAX) wallet.

  2. Open the information of your CRN on the aleph.im account page and enter the address in the section named STREAM REWARD ADDRESS.

    Add the reward address inside the CRN configuration /etc/aleph-vm/supervisor.env in the form of:

    ALEPH_VM_PAYMENT_RECEIVER_ADDRESS="0x0000000000000000000000000000000000000000"

    Where 0x0000000000000000000000000000000000000000 is the address of your wallet.

  3. Restart the node with systemctl restart aleph-vm-supervisor.service

  4. Confirm that the address appears on the path /status/config on the CRN's URL/config

Assets 5
Loading