Releases: aleph-im/aleph-vm
0.2.2 Updated internals
This release upgrades Firecracker to 1.1.0, the Linux Kernel to 5.10, and fixes bugs in the VM supervisor.
What's Changed
- Doc: Use v 0.2.1 instead of 0.1.10 by @hoh in #188
- Fix: Lib
packaging
was not added to Dockerfile by @hoh in #192 - Fix: Concurrent requests could result in a different counter value by @hoh in #193
- Chore: Update firecracker to 1.1.0 by @hoh in #203
- Internal: Raise exception VmInitNotConnected when VM init cannot be reached by @hoh in #201
- Fix: Settings with implicit annotations were not displayed by @hoh in #200
- Fix: Recording VM usage crashed if process had stopped beforehand by @hoh in #198
- Fix: A VM would not restart if the init process crashes by @hoh in #199
- Chore: Update kernel to 5.10 by @hoh in #202
Full Changelog: 0.2.1...0.2.2
How to upgrade
On Debian:
rm -f /opt/aleph-vm.debian-11.deb
wget -P /opt https://github.com/aleph-im/aleph-vm/releases/download/0.2.2/aleph-vm.debian-11.deb
apt install /opt/aleph-vm.debian-11.deb
On Ubuntu:
rm -f /opt/aleph-vm.ubuntu-20.04.deb
sudo wget -P /opt https://github.com/aleph-im/aleph-vm/releases/download/0.2.2/aleph-vm.ubuntu-20.04.deb
sudo apt install /opt/aleph-vm.ubuntu-20.04.deb
0.2.1 Stability matters
This minor release improves the stability of the software. The main visible change is the switch to use the Aleph Load Balancer with official Aleph nodes by default instead of the api2.aleph.im server. This improves the reliability of Compute Resource Nodes by providing multiple nodes to connect to.
Operators
- Change: Use the load balancer instead of api2 by @hoh in #184
- Feature: User could not easily access the current version of the software by @hoh in #180
Developers
- Fix: Developer Dockerfile was obsolete and broken by @hoh in #172
- Feature: Developer could not run custom command in container by @hoh in #171
Other changes
- Fix: Cargo.toml file was missing from Rust example by @hoh in #175
- Fix: Database access during benchmarks errored by @hoh in #173
- Fix: Getting version from git crashed when git was missing or on shallow clone by @hoh in #170
- [Doc] Fix typos by @odesenfans in #178
- Fix: Users could not tell if redacted fields were empty by @hoh in #168
- Fix: Incomplete file download could lead to inconsistent state by @hoh in #177
- Fix: Process metrics crashed if process was already stopped by @hoh in #169
- Fix and cleanup vm_connector by @hoh in #179
- Fix: Response body requires bytes, was given str by @hoh in #182
- Fix: AttributeError crashed VM teardown by @hoh in #183
- Feature: Load balancer could not distinguish outdated supervisors by @hoh in #181
- Internal: Enhance typing by @hoh in #185
- Allow to run CI in a Droplet for nested virtualization by @hoh in #186
- Fix: Software version could not be fetched from apt by @hoh in #187
Full Changelog: 0.2.0...0.2.1
How to upgrade
On Debian:
rm -f /opt/aleph-vm.debian-11.deb
wget -P /opt https://github.com/aleph-im/aleph-vm/releases/download/0.2.1/aleph-vm.debian-11.deb
apt install /opt/aleph-vm.debian-11.deb
On Ubuntu:
rm -f /opt/aleph-vm.ubuntu-20.04.deb
sudo wget -P /opt https://github.com/aleph-im/aleph-vm/releases/download/0.2.1/aleph-vm.ubuntu-20.04.deb
sudo apt install /opt/aleph-vm.ubuntu-20.04.deb
0.2.0 Resource monitoring
This new release introduces the monitoring of the resources used by VMs, changes where files are stored on the system, and introduces multiple fixes and improvements.
Monitoring of VM resources
Execution times of VMs that stopped can be fetched on https://{host}/about/executions/records
. Resource usage of running VMs can be fetched after authentication on https://{host}/about/executions
.
Execution times are stored by default in /var/lib/aleph/vm/executions.sqlite3
(settings.EXECUTION_DATABASE
).
Breaking changes
- Aleph-VM files are now stored in
/var/lib/aleph/vm
:/srv/jailer
→/var/lib/aleph/vm/jailer
/var/tmp/aleph/volumes
→/var/lib/aleph/vm/volumes
- The supervisor cache moved from
/tmp/aleph/vm_supervisor
to/var/cache/aleph/vm
3b0d93a
Other changes
- Expose the version of aleph-vm in HTTP header
server
by @hoh in #151 - Dependency: Upgrade Firecracker to v1.0.0 by @hoh in #159
- Hoh small fixes by @hoh in #152
- Problem: Developers had no easy way to know which Python dependencies to use by @hoh in #153
- Build(deps): Bump psutil from 5.5.1 to 5.6.6 in /packaging by @dependabot in #156
- Build(deps): Bump aiohttp from 3.6.2 to 3.7.4 in /packaging by @dependabot in #155
- Cleanup: Remove unnecessary type annotations by @hoh in #154
- Fix: Querying index with HTTP HEAD raised 500 due to AssertionError by @hoh in #149
- Fix minor upgrade issues by @hoh in #157
- Cleanup: Use
black
formatter by @hoh in #161 - Hoh fix srv jailer by @hoh in #162
- Fix: Package postrm/postinst failed if directory was missing by @hoh in #163
Full Changelog: 0.1.10...0.2.0
How to upgrade
First read the Breaking changes section above and adjust your customized system configuration if relevant.
On Debian:
rm -f /opt/aleph-vm.debian-11.deb
wget -P /opt https://github.com/aleph-im/aleph-vm/releases/download/0.2.0/aleph-vm.debian-11.deb
apt install /opt/aleph-vm.debian-11.deb
On Ubuntu:
rm -f /opt/aleph-vm.ubuntu-20.04.deb
sudo wget -P /opt https://github.com/aleph-im/aleph-vm/releases/download/0.2.0/aleph-vm.ubuntu-20.04.deb
sudo apt install /opt/aleph-vm.ubuntu-20.04.deb
0.1.10 Reliability fixes
In short
This minor release improves the reliability of the VM Supervisor and fixes some bugs.
We recommend everyone to upgrade.
New features
Operators can use the new setting SENTRY_DSN
to configure the supervisor to report errors to a Sentry project (self-hosted or cloud).
How to upgrade
On Debian:
rm -f /opt/aleph-vm.debian-11.deb
wget -P /opt https://github.com/aleph-im/aleph-vm/releases/download/0.1.10/aleph-vm.debian-11.deb
apt install /opt/aleph-vm.debian-11.deb
On Ubuntu:
rm -f /opt/aleph-vm.ubuntu-20.04.deb
sudo wget -P /opt https://github.com/aleph-im/aleph-vm/releases/download/0.1.10/aleph-vm.ubuntu-20.04.deb
sudo apt install /opt/aleph-vm.ubuntu-20.04.deb
What's Changed
- Hoh fix teardown interfaces by @hoh in #131
- Feature: Add support for error monitoring on Sentry by @hoh in #133
- Fix: Unhandled error class during shutdown by @hoh in #135
- [Doc] Fix typos by @odesenfans in #136
- Fix: Users could not identify missing hash by @hoh in #146
- Fix: VM resource seconds field was ignored by @hoh in #144
- Fix: Sentry DSN appeared in clear in the logs by @hoh in #142
- Doc: Package installation was difficult to follow by @hoh in #141
- Fix: forget_vm called twice when VM init times out by @hoh in #138
New Contributors
- @odesenfans made their first contribution in #136
Full Changelog: 0.1.9...0.1.10
Fix package upgrade
Upgrading a Debian package was erasing the settings configured by the administrator. This minor release fixes this issue.
What's Changed
Full Changelog: 0.1.8...0.1.9
How to upgrade
On Debian 11, as root
wget -P /opt https://github.com/aleph-im/aleph-vm/releases/download/0.1.9/aleph-vm.debian-11.deb
apt install /opt/aleph-vm.debian-0.1.9.deb
On Ubuntu 20.04:
sudo wget -P /opt https://github.com/aleph-im/aleph-vm/releases/download/0.1.9/aleph-vm.ubuntu-20.04.deb
sudo apt install /opt/aleph-vm.ubuntu-20.04.deb
Important fixes and smaller Debian packages
This is a release with important bug fixes and reliability issues, and improves the packaging operations.
The main issue this fixes is the "Too many open files" issue some operators encountered.
It also fixes reliability issues in persistent volumes that were not properly synced before the shutdown of the VM.
A test runtime rootfs is not included in the packages anymore, bringing package sizes back to an acceptable size of 13.5 MB instead of ~200 MB. Package version numbers are automatically generated from Git.
What's Changed
- Fix: Redis connections were accumulating by @hoh in #111
- Fix: A directory with the numerical id of the VM was not deleted by @hoh in #113
- Feature: Admin could not distinguish guest_api among running processes by @hoh in #112
- Internal: Package
firecracker
was not mounted in development container by @hoh in #114 - Fix: VM were not properly shutdowm, persistent volumes could be corrupted by @hoh in #115
- Feature: Publish artifacts from GH actions by @hoh in #117
Full Changelog: 0.1.7...0.1.8
Index page with new diagnostic tools
New installation packages, fixed issue related to missing fake data files
0.1.6-1 Doc: Fix README, creating Caddyfile requires sudo
New installation packages
Run Aleph VMs in reaction to Aleph messages
This release is a new milestone in the VM executor: A VM can be triggered in reaction to Aleph messages.