Cloud Virtualization: Red Hat, AWS Firecracker, and Ubicloud internals
1–10 of 17 posts
Re: Cloud Virtualization: Red Hat, AWS Firecracker, and Ubicloud internals
#2[dead]
Re: Cloud Virtualization: Red Hat, AWS Firecracker, and Ubicloud internals
#3[deleted]
Re: Cloud Virtualization: Red Hat, AWS Firecracker, and Ubicloud internals
#4Ubicloud is built on Ruby, interesting take for 2025.
Re: Cloud Virtualization: Red Hat, AWS Firecracker, and Ubicloud internals
#5Ubicloud is built on Ruby, interesting take for 2025.
Yes, it is. :) Our CTO, Daniel, described why we chose Ruby for our control plane in a blog post.
https://www.ubicloud.com/blog/building-infrastructure-contro...
On the data plane side, we use different open source components and our choice of programming language depends on them. For example for virtualization, we rely on Linux KVM and the Cloud Hypervisor. The former is in C and the latter in Rust.
Re: Cloud Virtualization: Red Hat, AWS Firecracker, and Ubicloud internals
#6Ubicloud is built on Ruby, interesting take for 2025.
May you live in interesting times.
Re: Cloud Virtualization: Red Hat, AWS Firecracker, and Ubicloud internals
#7Qemu's response to Firecracker is microvm:
Re: Cloud Virtualization: Red Hat, AWS Firecracker, and Ubicloud internals
#8We use Ubicloud for our GHA runners, because we have a very extensive test suite and need the extra parallelisation. Extremely easy to roll out from GHA, reduced our CI costs from CircleCI by 80% and we've been very pleased. Thanks for the great product!
Re: Cloud Virtualization: Red Hat, AWS Firecracker, and Ubicloud internals
#9Ubicloud is built on Ruby, interesting take for 2025.
May you live in interesting times.
Is there an actual underlying message to this or is this just wordplay? Don't know much about Ruby, but what I do know doesn't suggest it would make our (already all too "interesting") times even more "interesting".
Re: Cloud Virtualization: Red Hat, AWS Firecracker, and Ubicloud internals
#10Author of "All you need to know about KVM userspace" here! I am happy that you liked it. Some things have changed since then, some have not...
Red Hat is now shipping Kata Containers, which does not (much to my dismay) use Libvirt, and also KubeVirt which uses Libvirt but not for sandboxing (only to drive QEMU; Kubernetes takes care of the sandboxing by running one VM per pod). But the original architecture is still in use and new users appeared such as cockpit-machine and crun-vm.
Another super interesting project for KVM userspace is libkrun which, among other things, is being used for gaming on Arm Mac's. :)
Firecracker's scope has grown somewhat, in particular it supports snapshots for warm start of VMs.
QEMU's microvm didn't have a huge success but recently Amazon contributed support for running Nitro enclaves in QEMU, which reuses a lot of the microvm code.
Some Rust components have been developed to build virtio devices out of process (for example virtiofsd). QEMU is also experimenting with devices written in Rust, and I expect to have two almost-entirely-safe-Rust devices (converted from C) within a month or two.