#kvm — Public Fediverse posts

What to Consider When Renting a #VPS

This article provides a guide demonstrating what to consider when renting a VPS in .
Introduction
As websites, applications, and online businesses continue to grow, many users eventually outgrow shared ...
Continued 👉 #vpsvirtualization #kvmvps #ssd #kvm

What to Consider When Renting ...

I've always appreciated the simplicity of the BSDs. Power, yes, but without unnecessary complexity.

BastilleBSD and vm-bhyve have been my trusted companions for many years. But whenever I used Linux, I missed them.

That's why, years ago, I started putting together a collection of shell scripts (and some Python, although to a much lesser extent) to create something somewhere in between.

A bit of Bastille, a bit of vm-bhyve, a bit of Proxmox: unprivileged Linux system containers and virtual machines, managed from the command line.

Live backups. And live restore: bringing a workload back online before all its data has finished copying from the backup. Multiple storage backends. Encryption at the storage or individual workload level. Different networks. Isolation of each workload (a bit like illumos zones), with additional layers of protection.

Each container has its own UID/GID mapping. VMs run under separate unprivileged identities, with namespaces, seccomp and resource limits adding further layers of protection.

Pull-based backups from external hosts, with different levels and types of encryption. With raw encrypted ZFS replication, the backup server doesn’t even need the decryption keys. Backups are pulled over SSH by an external server. The workload host holds no credentials to log in to that server.

It also runs on a 1 GB Orange Pi PC 2, where I’ve tested both containers and native ARM64 KVM guests. And on a Orange PI One, armv7 and 512MB, it can run some lxc containers without problems, from the SD, using f2fs.

Simple disaster recovery. Because after those 142 servers went up in flames in Strasbourg, disaster recovery became something I care a lot about.

Currently supported and tested on Alpine Linux, Debian 13 and Armbian. On Debian, LXC containers also run under enforcing AppArmor profiles, adding another layer of protection.

Few commands. Lots of power. And it's called "Jail It!"

I'm not going to release it, at least not for now. I need to focus on my other projects, and Jail It! still needs some cleaning up.

But it works. And it does its job very well.

For containers, there's absolutely nothing running in the background. For VMs, just a small Python helper. No continuously running services. You connect via SSH, run your commands, and that's it.

Still, for anyone curious enough to have a look, I've put together a short demo on Asciinema:

https://asciinema.org/a/BbwGs99U9UJDLAzZ

Well, "short" might be a bit of an exaggeration. It's quite long, but I think it's worth watching all the way to the end.

#Linux #LXC #KVM #FreeBSD #Virtualization #OwnYourData #BSD #SelfHosting #Homelab #SysAdmin #DisasterRecovery

А я ни разу не была в малинках: запихиваем Cozystack в три Raspberry Pi с 8Гб RAM

Три платы Raspberry Pi 5 на столе, а на них — кластер, в котором крутятся контейнеры и виртуальные машины, есть мультитенантность, managed базы данных и всё остальное, что дает Cozystack. Зачем это нужно? Cozystack обычно ставят на стойку серверов в дата-центре, и чтобы просто пощупать платформу, приходится арендовать железо или поднимать виртуалки в облаке. А три малинки стоят как один вечер в ресторане, помещаются в рюкзак и работают от обычной розетки. На них можно учиться, показывать Cozystack на конференциях, отлаживать автоматизации или держать дома маленькое облако.

https://habr.com/ru/companies/aenix/articles/1107100/

#kvm #raspberry #kubernetes #cozystack #aenix #home_lab #kuberoot