1.7.2

We are excited to announce our release for aleph-vm in version 1.7.2!

This update primarily focus on improving network stability and performance through crucial bug fixes related to instance network connectivity, HAProxy configurations, and timeout handling.

Bug Fixes:

• Instance Network on Server Reboot: Fixed an issue where the instance network would not work after a server reboot. (PR #823)
• HAProxy Fallback Server and Other Fixes: Addressed problems with the HAProxy fallback server configuration and other related issues, ensuring better service continuity. (PR #822)
• Gradual Increase in Waiting Time (GH-814): Fixed a bug that caused a gradual increase in waiting time, likely improving responsiveness. (PR #819)
• HAProxy Domain Mapping Issue: Resolved a specific issue with how HAProxy handles domain mapping. (PR #826)

Improvements:

• Increased Server Timeout: The server timeout has been increased, potentially leading to more robust connections and fewer timeouts. (PR #825)
• SSH Support for Custom domain HaProxy now handle SSH traffic redirection to your instance.

This update primarily focuses on enhancing the network resilience and stability of the Aleph VM. Key fixes include addressing network connectivity after reboots, improving HAProxy configurations for better failover, and resolving issues with waiting times and domain mapping. The increased server timeout also contributes to a more stable user experience.

What's Changed

• Fix Instance network not working on server reboot by @olethanh in #823
• Fix HaProxy fallback server and others fixes by @olethanh in #822
• fix GH-814 gradual increase in waiting time by @aliel in #819
• Increase Server timeout by @nesitor in #825
• Fix issue with HaProxy domain mapping by @olethanh in #826

Full Changelog: 1.7.1...1.7.2

How to upgrade

1. Upgrade the packages

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

On Debian 12 (Bookworm):

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

On Ubuntu 22.04 (Jammy Jellyfish):

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

On Ubuntu 24.04 (Noble Numbat):

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

2A. Apply last HAProxy Configuration (if you already did the migration to HAProxy.)

If your server was previously configured with last version, and you are having issues with metrics and IPv6, only apply last version configuration on HAProxy and restart it, this should solve the issue.

ln -fs /etc/haproxy/haproxy-aleph.cfg /etc/haproxy/haproxy.cfg
sudo systemctl restart haproxy
sudo systemctl restart aleph-vm-supervisor

Alternatively if the migration still has issue run the automatic configuration script documented below, it should fix them.

2B. Migrate from Caddy to HAProxy Configuration (if you did not migrate to HAProxy beforehand)

If your server was previously configured with Caddy, you can migrate to the HAProxy + Certbot setup using the steps
below. This configuration supports HTTPS and provides a secure reverse-proxy setup. The existing Caddy setup will remain
intact until you have tested and verified the HAProxy setup. Once verified, you may optionally remove the Caddy
package.

Automated setup via script

You can automate the migation using that script:

wget https://gist.githubusercontent.com/olethanh/0572b5d53af97fb7565f1847e01cd4f0/raw/816290af5b7092f523a51d95217016ac4f982e3e/setup_haproxy.sh
chmod +x setup_haproxy.sh
./setup_haproxy.sh

Manual migrations.

Alternatively, you can do the migration manually

Step 1: Stop the aleph-vm-supervisor Service

Before making changes, stop the aleph-vm-supervisor service managed by systemd to ensure a smooth migration process.

sudo systemctl stop aleph-vm-supervisor

Verify that the service has stopped:

sudo systemctl status aleph-vm-supervisor

Step 2: Stop Caddy Without Removing Its Configuration

Stop Caddy to prevent conflicts. Do not remove its configuration yet, so you can revert to Caddy if needed.

sudo systemctl stop caddy
sudo systemctl disable caddy

Check that Caddy is no longer running:

ps aux | grep caddy

Step 3: Install HAProxy

Follow this link with the instructions to install and setup HAProxy:
For Debian: https://docs.aleph.cloud/nodes/compute/installation/debian-12/#_4-install-a-reverse-proxy
For Ubuntu: https://docs.aleph.cloud/nodes/compute/installation/ubuntu-24.04/#_4-install-a-reverse-proxy

1.7.1

We are excited to announce our release for aleph-vm in version 1.7.1!

This update brings an important bug fix solve an issue with HAProxy and IPv6 connectivity.

What's Changed

• Fix HaProxy config for ipv6 and logging by @olethanh in #821

Full Changelog: 1.7.0...1.7.1

How to upgrade

1. Upgrade the packages

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

On Debian 12 (Bookworm):

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

On Ubuntu 22.04 (Jammy Jellyfish):

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

On Ubuntu 24.04 (Noble Numbat):

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

2. Migrate from Caddy to HAProxy Configuration (ONLY if the previous version installed is lowed or equal than 1.6.0)

If your server was previously configured with Caddy, you can migrate to the HAProxy + Certbot setup using the steps
below. This configuration supports HTTPS and provides a secure reverse-proxy setup. The existing Caddy setup will remain
intact until you have tested and verified the HAProxy setup. Once verified, you may optionally remove the Caddy
package.

Step 1: Stop the aleph-vm-supervisor Service

Before making changes, stop the aleph-vm-supervisor service managed by systemd to ensure a smooth migration process.

sudo systemctl stop aleph-vm-supervisor

Verify that the service has stopped:

sudo systemctl status aleph-vm-supervisor

Step 2: Stop Caddy Without Removing Its Configuration

Stop Caddy to prevent conflicts. Do not remove its configuration yet, so you can revert to Caddy if needed.

sudo systemctl stop caddy
sudo systemctl disable caddy

Check that Caddy is no longer running:

ps aux | grep caddy

Step 3: Install HAProxy

Follow this link with the instructions to install and setup HAProxy:
For Debian: https://docs.aleph.cloud/nodes/compute/installation/debian-12/#_4-install-a-reverse-proxy
For Ubuntu: https://docs.aleph.cloud/nodes/compute/installation/ubuntu-24.04/#_4-install-a-reverse-proxy

Alternatively, you can automate the installation using that script:

wget https://gist.githubusercontent.com/olethanh/0572b5d53af97fb7565f1847e01cd4f0/raw/816290af5b7092f523a51d95217016ac4f982e3e/setup_haproxy.sh
chmod +x setup_haproxy.sh
./setup_haproxy.sh

3. Apply last HAProxy Configuration (ONLY if the previous version installed was equal to 1.7.0)

If your server was previously configured with last version, and you are having issues with metrics and IPv6, only apply last version configuration on HAProxy and restart it, this should solve the issue.

sudo mv etc/haproxy/haproxy-aleph.cfg /etc/haproxy/haproxy.cfg
sudo systemctl restart haproxy

1.7.0

We are excited to announce our release for aleph-vm in version 1.7.0!

This update brings significant new networking capabilities like IPv4 custom domains support for ports 80 and 443, and an important bug fix to improve stability and reliability.

✨ New Features & Enhancements

• Feature: Added support for IPv4 domains (#816).

🐞 Bug Fixes

• Fix: A fix was implemented for the /about/usage/system path on certain architectures (#818).

What's Changed

• Fix /about/usage/system on some arch by @olethanh in #818
• Aleph 565 ipv4 domain support by @olethanh in #816
• domain support haproxy config fix by @olethanh in #820

Full Changelog: 1.6.0...1.7.0

How to upgrade

1. Upgrade the packages

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

On Debian 12 (Bookworm):

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

On Ubuntu 22.04 (Jammy Jellyfish):

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

On Ubuntu 24.04 (Noble Numbat):

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

2. Migrate from Caddy to HAProxy Configuration (REQUIRED)

If your server was previously configured with Caddy, you can migrate to the HAProxy + Certbot setup using the steps
below. This configuration supports HTTPS and provides a secure reverse-proxy setup. The existing Caddy setup will remain
intact until you have tested and verified the HAProxy setup. Once verified, you may optionally remove the Caddy
package.

Step 1: Stop the aleph-vm-supervisor Service

Before making changes, stop the aleph-vm-supervisor service managed by systemd to ensure a smooth migration process.

sudo systemctl stop aleph-vm-supervisor

Verify that the service has stopped:

sudo systemctl status aleph-vm-supervisor

Step 2: Stop Caddy Without Removing Its Configuration

Stop Caddy to prevent conflicts. Do not remove its configuration yet, so you can revert to Caddy if needed.

sudo systemctl stop caddy
sudo systemctl disable caddy

Check that Caddy is no longer running:

ps aux | grep caddy

Follow this link with the instructions to install and setup HAProxy:
For Debian: https://docs.aleph.cloud/nodes/compute/installation/debian-12/#_4-install-a-reverse-proxy
For Ubuntu: https://docs.aleph.cloud/nodes/compute/installation/ubuntu-24.04/#_4-install-a-reverse-proxy

1.6.0

We are excited to announce our release for aleph-vm in version 1.6.0!

This update brings significant new networking capabilities like IPv4 port forwarding, new API endpoints, and a host of important bug fixes to improve stability and reliability.

✨ New Features & Enhancements

• IPv4 Port Forwarding: The VM now supports IPv4 port forwarding (#806).
• Hardware Capability Endpoint: A new API endpoint has been added to provide detailed CPU (model, vendor, frequency) and memory (clock, size, type) information (#801).
• New Execution List Endpoint: A new endpoint for listing executions has been added, along with logic to retry instances that are not running (#793).

🐞 Bug Fixes

• Networking & Firewall:
  • Fixed an issue with incorrect port directions (#810).
  • Resolved a problem causing duplicate nftables firewall rules (#812).
  • Addressed and solved firewall redirect issues (#813).
• System & Stability:
  • The Grub root device path has been corrected to ensure proper booting (#805).
  • The program warmup timeout has been increased from 1s to 5s to prevent startup issues (#814).
  • A DBUS error that occurred when enabling the controller has been fixed (#815).
• API:
  • API error responses are now guaranteed to be in JSON format (#804).

🛠️ Other Improvements

• The CI/CD pipeline has been fixed (#808).
• The aleph-message dependency has been updated to the latest version (#809).
• The README.md has been updated (#817).

What's Changed

• fix: Grub root device must be placed in a proper location to avoid bo… by @aliel in #805
• ALEPH-512 ensure we always return json for error by @olethanh in #804
• Retry instances not running add new Execution list endpoint by @olethanh in #793
• New capability endpoint to add CPU information (model, vendor, frequency) and memory details (clock, size, type) to API by @olethanh in #801
• Solve CI/CD issue by @nesitor in #808
• ALEPH-551 Implement ipv4 port forwarding by @olethanh in #806
• Use last aleph-message version by @nesitor in #809
• Fix issue on port directions by @olethanh in #810
• Aleph 446 duplicate nftables rule by @olethanh in #812
• Solve firewall redirect issues by @olethanh in #813
• fix: Increase program warmup timeout from 1s to 5s by @aliel in #814
• ALEPH-435 Fix DBUS error when enabling controller by @olethanh in #815
• Update README.md by @clementfrmd in #817

New Contributors

• @clementfrmd made their first contribution in #817

Full Changelog: 1.5.1...1.6.0

How to upgrade

1. Upgrade the packages

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

On Debian 12 (Bookworm):

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

On Ubuntu 22.04 (Jammy Jellyfish):

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

On Ubuntu 24.04 (Noble Numbat):

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

2. Enable GPU support (optional)

In order to enable GPU support on your Compute Resource Node, you must:

1. Ensure that your system have a compatible GPU card.
2. Detach GPU cards from the kernel module drivers and attach it to QEMU vfio drivers.
3. Enable GPU support in the aleph-vm configuration.

Please follow these instructions

Enable GPU in the configuration of aleph-vm, by default in /etc/aleph-vm/supervisor.env. This is not the default yet.

ALEPH_VM_ENABLE_GPU_SUPPORT=True

After launching the server you can check the endpoint
http://localhost:4020/status/config or https://<your-node-domain>/status/config and verify that ENABLE_GPU_SUPPORT has the value true.

1.6.0-rc1

We are excited to announce our release candidate for aleph-vm in version 1.6.0-rc1!

This update brings significant new features like detailed hardware information and IPv4 port forwarding, alongside crucial bug fixes addressing boot issues, API error consistency, and network configuration problems. CI/CD stability and aleph-message dependency updates also contribute to a more robust system.

New Features:

• Execution List Endpoint & Instance Retries: Added a new endpoint to list executions and implemented retry mechanisms for instances that are not running. (PR #793)
• Detailed Capability Endpoint: Introduced a new capability endpoint that provides comprehensive CPU information (model, vendor, frequency) and memory details (clock, size, type) via the API. (PR #801)
• IPv4 Port Forwarding: Implemented IPv4 port forwarding functionality (ALEPH-551). (PR #806)

Bug Fixes:

• Grub Root Device Placement: Fixed an issue where the Grub root device was not placed in a proper location, leading to boot problems. (PR #805)
• JSON Error Returns: Ensured that errors consistently return JSON responses (ALEPH-512). (PR #804)
• CI/CD Issue: Resolved a problem affecting the CI/CD pipeline. (PR #808)
• Port Direction Issues: Fixed issues related to port directions. (PR #810)
• Duplicate NFTables Rule: Addressed the problem of duplicate NFTables rules (ALEPH-446). (PR #812)
• Firewall Redirect Issues: Solved issues with firewall redirects. (PR #813)

Improvements:

• aleph-message Version Update: Updated to the latest aleph-message version. (PR #809)

What's Changed

• fix: Grub root device must be placed in a proper location to avoid bo… by @aliel in #805
• ALEPH-512 ensure we always return json for error by @olethanh in #804
• Retry instances not running add new Execution list endpoint by @olethanh in #793
• New capability endpoint to add CPU information (model, vendor, frequency) and memory details (clock, size, type) to API by @olethanh in #801
• Solve CI/CD issue by @nesitor in #808
• ALEPH-551 Implement ipv4 port forwarding by @olethanh in #806
• Use last aleph-message version by @nesitor in #809
• Fix issue on port directions by @olethanh in #810
• Aleph 446 duplicate nftables rule by @olethanh in #812
• Solve firewall redirect issues by @olethanh in #813

Full Changelog: 1.5.1...1.6.0-rc1

How to upgrade

1. Upgrade the packages

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

On Debian 12 (Bookworm):

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

On Ubuntu 22.04 (Jammy Jellyfish):

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

On Ubuntu 24.04 (Noble Numbat):

sudo rm -f /opt/aleph-vm.ubuntu-24.04.deb
sudo wget -P /opt https://github.com/aleph-im/aleph-vm/releases/download/1.6.0-rc1/aleph-vm.ubuntu-24.04.deb
sudo apt install /opt/aleph-vm.ubuntu-24.04.deb

2. Enable GPU support (optional)

In order to enable GPU support on your Compute Resource Node, you must:

1. Ensure that your system have a compatible GPU card.
2. Detach GPU cards from the kernel module drivers and attach it to QEMU vfio drivers.
3. Enable GPU support in the aleph-vm configuration.

Please follow these instructions

Enable GPU in the configuration of aleph-vm, by default in /etc/aleph-vm/supervisor.env. This is not the default yet.

ALEPH_VM_ENABLE_GPU_SUPPORT=True

After launching the server you can check the endpoint
http://localhost:4020/status/config or https://<your-node-domain>/status/config and verify that ENABLE_GPU_SUPPORT has the value true.

1.5.1

We are excited to announce our release for aleph-vm in version 1.5.0!

This new release of aleph-vm fixes issues with disk space calculations.

What's Changed

• Fix reported disk space being too low. by @olethanh in #802
• Fix reserved space calculation by @olethanh in #803

Full Changelog: 1.5.0...1.5.1

How to upgrade

1. Upgrade the packages

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

On Debian 12 (Bookworm):

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

On Ubuntu 22.04 (Jammy Jellyfish):

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

On Ubuntu 24.04 (Noble Numbat):

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

2. Enable GPU support (optional)

In order to enable GPU support on your Compute Resource Node, you must:

1. Ensure that your system have a compatible GPU card.
2. Detach GPU cards from the kernel module drivers and attach it to QEMU vfio drivers.
3. Enable GPU support in the aleph-vm configuration.

Please follow these instructions

Enable GPU in the configuration of aleph-vm, by default in /etc/aleph-vm/supervisor.env. This is not the default yet.

ALEPH_VM_ENABLE_GPU_SUPPORT=True

After launching the server you can check the endpoint
http://localhost:4020/status/config or https://<your-node-domain>/status/config and verify that ENABLE_GPU_SUPPORT has the value true.

1.5.0

We are excited to announce our release for aleph-vm in version 1.5.0!

This new release of aleph-vm brings significant improvements to the Aleph VM, including the new GPU reservation system and in-VM reboot functionality. It also addresses several important bug fixes related to CI stability, GPU detection, network configuration, VM lifecycle, and volume downloads. The upgrade of Firecracker and aleph-message, along with the Pydantic migration, further enhances the platform.

New Features

• GPU Reservation System: Implemented a system for reserving GPUs. (PR #776)
• VM Reboot from Inside: Allowed users to reboot their VMs from within the VM itself. (PR #790)
• Operator Authentication Improvements: Enhanced operator authentication with better HTTP error reporting. (PR #788)

Bug Fixes

• Random CI Failures: Fixed random failures in the Continuous Integration (CI) pipeline and merged workflows. (PR #787)
• GPU x-vga Detection: Corrected the detection of x-vga for GPUs. (PR #786)
• ndppd Proxy Interface Loading: Fixed an issue where the ndppd proxy was not loading existing interfaces on supervisor restart. (PR #783)
• VM Lifecycle and Blocking Resources: Addressed issues related to the VM lifecycle and blocking resources. (PR #789)
• Volume Download from Connector: Fixed a problem with downloading volumes from the connector. (PR #796)
• Pydantic TypeAdapter Issue: Solved an issue related to Pydantic's TypeAdapter. (PR #794)
• Confidential VM Cleanup (ALEPH-517): Fixed an issue related to the cleanup of confidential VMs. (PR #797)
• Confidential and GPU Instance Stopping (ALEPH-518): Resolved a bug where confidential and GPU instances were stopping immediately after starting. (PR #798)
• Message Requirements Casting: Solved a casting issue with message requirements. (PR #800)
• Internet Check Failure: Fixed an issue causing the internet check to fail. (PR #799)

Improvements

• Hatch Formatting: Performed some cleanup using hatch fmt. (PR #782)
• Usage System: Removed reserved usage tracking for volumes in the usage system. (PR #784)
• Misc Stability Improvements: Implemented various stability improvements (OL ALEPH-166). (PR #719)
• Firecracker Upgrade: Upgraded Firecracker from version 1.5.0 to 1.7.0. (PR #771)
• Pydantic Migration: Migrated the project from Pydantic V1 to V2. (PR #791)
• Confidential VM Locale: Updated locale settings to en_US UTF-8 during the setup of confidential VMs. (PR #792)
• aleph-message Upgrade: Upgraded the aleph-message dependency to version 1.0.0. (PR #795)

What's Changed

• CI: Fix random failures. Merge workflows by @olethanh in #787
• Bit of clean up with hatch fmt by @olethanh in #782
• Gpu Reservation system by @olethanh in #776
• Fix x-vga detection on GPUs by @nesitor in #786
• Fix: ndppd proxy not loading existing interfaces on supervisor restart by @nesitor in #783
• Usage system: remove reserved usage for volumes by @olethanh in #784
• Ol aleph 166 misc stability by @olethanh in #719
• Fix: Upgrade Firecracker 1.5.0 -> 1.7.0 by @hoh in #771
• Fix VM lifecycle and blocking resource. by @olethanh in #789
• enh: allow user to reboot from inside the VM by @olethanh in #790
• enh: Operator auth. Better http error by @olethanh in #788
• Migrate Pydantic V1 to V2 by @nesitor in #791
• Solve Pydantic TypeAdapter issue by @nesitor in #794
• Confidentials: Update locale settings to en_US UTF-8 during setup by @aliel in #792
• FIX downloading volume from connector by @olethanh in #796
• Upgrade aleph-message==1.0.0 version dependency by @nesitor in #795
• Fix ALPEH-517 confidential clean up by @olethanh in #797
• ALEPH-518 Fix Confidential and GPU instance stopping after start by @olethanh in #798
• Solve message requirements casting issue by @nesitor in #800
• Fix internet check failure by @olethanh in #799

Full Changelog: 1.4.2...1.5.0

How to upgrade

1. Upgrade the packages

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

On Debian 12 (Bookworm):

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

On Ubuntu 22.04 (Jammy Jellyfish):

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

On Ubuntu 24.04 (Noble Numbat):

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

2. Enable GPU support (optional)

In order to enable GPU support on your Compute Resource Node, you must:

1. Ensure that your system have a compatible GPU card.
2. Detach GPU cards from the kernel module drivers and attach it to QEMU vfio drivers.
3. Enable GPU support in the aleph-vm configuration.

Please follow these instructions

Enable GPU in the configuration of aleph-vm, by default in /etc/aleph-vm/supervisor.env. This is not the default yet.

ALEPH_VM_ENABLE_GPU_SUPPORT=True

After launching the server you can check the endpoint
http://localhost:4020/status/config or https://<your-node-domain>/status/config and verify that ENABLE_GPU_SUPPORT has the value true.

1.5.0-rc1

We are excited to announce our release for aleph-vm in version 1.5.0-rc1 !

This new release of aleph-vm brings significant improvements to the Aleph VM, including the new GPU reservation system and in-VM reboot functionality. It also addresses several important bug fixes related to CI stability, GPU detection, network configuration, VM lifecycle, and volume downloads. The upgrade of Firecracker and aleph-message, along with the Pydantic migration, further enhances the platform.

New Features

• GPU Reservation System: Implemented a system for reserving GPUs. (PR #776)
• VM Reboot from Inside: Allowed users to reboot their VMs from within the VM itself. (PR #790)
• Operator Authentication Improvements: Enhanced operator authentication with better HTTP error reporting. (PR #788)

Bug Fixes

• Random CI Failures: Fixed random failures in the Continuous Integration (CI) pipeline and merged workflows. (PR #787)
• GPU x-vga Detection: Corrected the detection of x-vga for GPUs. (PR #786)
• ndppd Proxy Interface Loading: Fixed an issue where the ndppd proxy was not loading existing interfaces on supervisor restart. (PR #783)
• VM Lifecycle and Blocking Resources: Addressed issues related to the VM lifecycle and blocking resources. (PR #789)
• Volume Download from Connector: Fixed a problem with downloading volumes from the connector. (PR #796)
• Pydantic TypeAdapter Issue: Solved an issue related to Pydantic's TypeAdapter. (PR #794)

Improvements

• Hatch Formatting: Performed some cleanup using hatch fmt. (PR #782)
• Usage System: Removed reserved usage tracking for volumes in the usage system. (PR #784)
• Misc Stability Improvements: Implemented various stability improvements (OL ALEPH-166). (PR #719)
• Firecracker Upgrade: Upgraded Firecracker from version 1.5.0 to 1.7.0. (PR #771)
• Pydantic Migration: Migrated the project from Pydantic V1 to V2. (PR #791)
• Confidential VM Locale: Updated locale settings to en_US UTF-8 during the setup of confidential VMs. (PR #792)
• aleph-message Upgrade: Upgraded the aleph-message dependency to version 1.0.0. (PR #795)

What's Changed

• CI: Fix random failures. Merge workflows by @olethanh in #787
• Bit of clean up with hatch fmt by @olethanh in #782
• Gpu Reservation system by @olethanh in #776
• Fix x-vga detection on GPUs by @nesitor in #786
• Fix: ndppd proxy not loading existing interfaces on supervisor restart by @nesitor in #783
• Usage system: remove reserved usage for volumes by @olethanh in #784
• Ol aleph 166 misc stability by @olethanh in #719
• Fix: Upgrade Firecracker 1.5.0 -> 1.7.0 by @hoh in #771
• Fix VM lifecycle and blocking resource. by @olethanh in #789
• enh: allow user to reboot from inside the VM by @olethanh in #790
• enh: Operator auth. Better http error by @olethanh in #788
• Migrate Pydantic V1 to V2 by @nesitor in #791
• Solve Pydantic TypeAdapter issue by @nesitor in #794
• Confidentials: Update locale settings to en_US UTF-8 during setup by @aliel in #792
• FIX downloading volume from connector by @olethanh in #796
• Upgrade aleph-message==1.0.0 version dependency by @nesitor in #795

Full Changelog: 1.4.2...1.5.0-rc1

How to upgrade

1. Upgrade the packages

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

On Debian 12 (Bookworm):

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

On Ubuntu 22.04 (Jammy Jellyfish):

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

On Ubuntu 24.04 (Noble Numbat):

sudo rm -f /opt/aleph-vm.ubuntu-24.04.deb
sudo wget -P /opt https://github.com/aleph-im/aleph-vm/releases/download/1.5.0-rc1/aleph-vm.ubuntu-24.04.deb
sudo apt install /opt/aleph-vm.ubuntu-24.04.deb

2. Enable GPU support (optional)

In order to enable GPU support on your Compute Resource Node, you must:

1. Ensure that your system have a compatible GPU card.
2. Detach GPU cards from the kernel module drivers and attach it to QEMU vfio drivers.
3. Enable GPU support in the aleph-vm configuration.

Please follow these instructions

Enable GPU in the configuration of aleph-vm, by default in /etc/aleph-vm/supervisor.env. This is not the default yet.

ALEPH_VM_ENABLE_GPU_SUPPORT=True

After launching the server you can check the endpoint
http://localhost:4020/status/config or https://<your-node-domain>/status/config and verify that ENABLE_GPU_SUPPORT has the value true.

1.4.2

We are excited to announce our release for aleph-vm in version 1.4.2 !

This new release of aleph-vm addresses various bugs and improves the stability and performance. It includes fixes for packaging issues, concurrency problems, outdated dependencies, and improvements to error handling and caching.

Bug Fixes

• Ubuntu 22.02 Packaging Issue: Attempted to fix a packaging issue on Ubuntu 22.02. (PR #763)
• stdout Caching Concurrency Issues: Fixed concurrency issues caused by stdout caching. (PR #762)
• update_allocation Error Handling: Improved error handling in the update_allocation function. (PR #764)
• Outdated python-cpuid Version: Corrected the usage of an outdated version of python-cpuid. (PR #766)
• Supervisor Restart on Kubo Crash: Fixed an issue where the supervisor was restarted when Kubo crashed. (PR #767)
• References to api1.aleph.im: Removed references to the slow server api1.aleph.im. (PR #769)
• Buggy Settings Aggregate Cache: Fixed a buggy implementation of the settings aggregate cache. (PR #781)
• Missing Type Annotation: Added a missing type annotation. (PR #773)

Improvements

• Kubo Upgrade: Upgraded Kubo. (PR #778)
• IPv6 Subnet Allowance: Allowed /56 subnets for the IPv6 pool. (PR #761)

Dependency Updates

• sentry-sdk Update: Updated sentry-sdk from 1.31 to 2.8.0. (PR #765)

Other Changes

• aleph-message Package Version Increment: Incremented the aleph-message package version. (PR #774)

What's Changed

• Attempt to fix the packaging issue on Ubuntu 22.02 by @olethanh in #763
• Fix: stdout caching caused concurrency issues by @hoh in #762
• Fix update_allocation error handling code by @olethanh in #764
• Fix: Used old versionof python-cpuid by @hoh in #766
• Fix: Supervisor was restarted when Kubo crashed by @hoh in #767
• Fix: Remove references to slow server api1.aleph.im by @hoh in #769
• Chore(deps): Bump sentry-sdk from 1.31 to 2.8.0 by @dependabot in #765
• Increment aleph-message package version by @nesitor in #774
• Fix: Missing type annotation by @Antonyjin in #773
• Hoh upgrade kubo by @hoh in #778
• Fix buggy settings aggregate cache implementation by @olethanh in #781
• Allow /56 subnet for ipv6 pool by @olethanh in #761

Full Changelog: 1.4.1...1.4.2

How to upgrade

1. Upgrade the packages

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

On Debian 12 (Bookworm):

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

On Ubuntu 22.04 (Jammy Jellyfish):

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

On Ubuntu 24.04 (Noble Numbat):

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

2. Enable GPU support (optional)

In order to enable GPU support on your Compute Resource Node, you must:

1. Ensure that your system have a compatible GPU card.
2. Detach GPU cards from the kernel module drivers and attach it to QEMU vfio drivers.
3. Enable GPU support in the aleph-vm configuration.

Please follow these instructions

Enable GPU in the configuration of aleph-vm, by default in /etc/aleph-vm/supervisor.env. This is not the default yet.

ALEPH_VM_ENABLE_GPU_SUPPORT=True

After launching the server you can check the endpoint
http://localhost:4020/status/config or https://<your-node-domain>/status/config and verify that ENABLE_GPU_SUPPORT has the value true.

1.4.1

We are excited to announce our release for aleph-vm in version 1.4.1 !

This new release of aleph-vm fixes bugs related to persistent executions, pricing, and network checks.

Bug Fixes

• load_persistent_executions Start Error: Fixed a start error in the load_persistent_executions function. (PR #759)
• Notify Endpoint Pricing: Resolved a pricing calculation issue on the /notify endpoint. (PR #758)
• DiagnosticVM IPv4 Check: Fixed an issue in DiagnosticVM to force IPv4 connection on the /internet check. (PR #760)

Full List

• Fix start error in load_persistent_executions by @olethanh in #759
• Solve pricing calculation issue on Notify endpoint by @nesitor in #758
• Fix DiagnosticVM, force ipv4 connexion on /internet check by @olethanh in #760

Full Changelog: 1.4.0...1.4.1

How to upgrade

1. Upgrade the packages

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

On Debian 12 (Bookworm):

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

On Ubuntu 22.04 (Jammy Jellyfish):

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

On Ubuntu 24.04 (Noble Numbat):

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

2. Enable GPU support (optional)

In order to enable GPU support on your Compute Resource Node, you must:

1. Ensure that your system have a compatible GPU card.
2. Detach GPU cards from the kernel module drivers and attach it to QEMU vfio drivers.
3. Enable GPU support in the aleph-vm configuration.

Please follow these instructions

Enable GPU in the configuration of aleph-vm, by default in /etc/aleph-vm/supervisor.env. This is not the default yet.

ALEPH_VM_ENABLE_GPU_SUPPORT=True

After launching the server you can check the endpoint
http://localhost:4020/status/config or https://<your-node-domain>/status/config and verify that ENABLE_GPU_SUPPORT has the value true.