Skip to content

Files

Latest commit

58cc683 · Jan 14, 2025

History

History

aep-49

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
Jan 14, 2025
aep title author status type category created updated estimated-completion roadmap
49
Virtual Machines
Artur Troian (@troian)
Draft
Standard
Core
2024-12-01
2025-01-11
2026-02-20
major

Summary

The concept of virtual machines (VMs) for the Akash Network revolves around leveraging decentralized cloud computing resources to deploy, manage, and scale Virtual Machines securely and cost-effectively.

This AEP will be extended via Github discussion and updated with the results and further details.

Motivation

Not all workloads are containerized. Many enterprises and users rely on legacy applications that run exclusively on VMs. By supporting VMs, Akash can:

  • Enable the migration of legacy applications without requiring extensive re-architecting.
  • Attract customers from industries reliant on VM-based infrastructures, such as finance and healthcare.

Specification

There are a few options to support VMs on Akash:

  • KubeVirt is a Kubernetes extension designed to manage and run virtual machines (VMs) alongside containerized workloads within a Kubernetes cluster. At this moment, KubeVirt seems to be most viable option as Akash deployments run on Kubernetes. This also implies minimal to no changes to the current deployment model.
  • QEMU is a full system emulator and virtualizer.
  • Firecracker is a fast and lightweight virtualization solution.

Both QEMU and Firecracker will require changes to the current deployment model as well as designing and developing new provider stack.

Copyright

All content herein is licensed under Apache 2.0.