homeassistant

12132 readers

5 users here now

Home Assistant is open source home automation that puts local control and privacy first. Powered by a worldwide community of tinkerers and DIY enthusiasts. Perfect to run on a Raspberry Pi or a local server. Available for free at home-assistant.io

founded 2 years ago

MODERATORS

[email protected]

HA redundancy options (feddit.uk)

submitted 11 months ago by [email protected] to c/homeassistant

17 comments fedilink hide all child comments

I'm currently running HA on a Pi3... it works fine, but it's now a single point of failure.

I have some new hardware arriving to run VMs in and was intending to move HA to it, but now I'm wondering if I can have HA in 2 places for fault tolerance.

I'm aware that there's no built-in failover options, but has anyone done something similar?

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 7 points 11 months ago (1 children)

Correct, OPs needs is describing what kubernetes was made for. Fault tolerant container orchestration. Or any other orchestration framework.

However it's a best to learn and get set up. Migrating all of my containers over took a couple of months of learning and trial and error. Each person has to decide is that level of effort worth it in a home application

[–] [email protected] 2 points 11 months ago* (last edited 11 months ago) (1 children)

Ok, but that's assuming >1 host can be managed that way... can I manage HA on the Pi3 as a backup to my new host with Kubernetes?

Edit: can Proxmox do this too?

[–] [email protected] 2 points 11 months ago (1 children)

You'll need to learn a lot more about kubernetes to decide fully if you want to do it. I'm more or less telling you that yes there are ways to keep it highly available, but they're going to be literally 10x if not more the amount of effort to spin up and probably maintain.

Proxmox has their own flavor of HA that is a lower level of virtualization. They'll be able to failover a specific VM/CT to another node if one fails, but again pros and cons. The major annoyance for both is where do you put your data so 2 separate nodes can access it? Both k8s and proxmox have different approaches.

[–] c10l 2 points 11 months ago (1 children)

K8s and Proxmox operate at different levels. You can run k8s on Proxmox, and that’s what I’ve been (very slowly) building up to at home.

With Proxmox you can failover VMs between nodes as long as storage (including VM boot disk) is external to the nodes. This can be NFS on a NAS, iSCSI, Ceph or many other options.

It’s even possible to failover a USB device (e.g. a Zigbee controller or similar) by attaching one on each node and mapping them using Resource Mappings (search on the announcement post: https://www.proxmox.com/en/about/press-releases/proxmox-virtual-environment-8-0).

This can also be used if you’re deploying k8s on top of Proxmox just as well.

[–] [email protected] 1 points 11 months ago

Ah, ok, thanks... I'll have to dig in to this some more