Decipher0771

Yes. Your machines would have one main IP address, and one virtual IP address that would be assigned to either machine depending on the priority or health check status. That IP can be on the same physical interface, or a separate one. It’s very flexible, pretty standard config for high availability setups.

Keepalived to set up a floating IP between two proxy hosts. The VIP is where the traffic points to, the two hosts act as active/passive HA.

I think the universal consensus is that outside of a very specific use case: multiple VDI desktops that share the same image, ZFS dedupe is completely useless at best and will destroy your dataset at worst by causing to be unmountable on any system that has less RAM than needed. In every other use case, the savings are not worth the trouble.

Even in the VDI use case, unless you have MANY copies of said disk images(like 5+ copies of each), it’s still not worth the increase in system resources needed to use ZFS dedupe.

It’s one of those “oooh shiny” nice features that everyone wants to use, but will regret it nearly every time.

Neat……but dnsdist would be my go to tool for doing this instead. It’s actually built for it, has more options, and probably doesn’t have as many host networking docker deployment limitations.

Big elk stack?

Just an A record, you just need the domain query to resolve to your IP.

No, it’s Trump first, America is just a piggy bank for him to plunder.

I was in a similar boat, and ended up buying a used convertible tablet from eBay instead. Much more Linux friendly, 12” Toshiba Dynabook. Might be a better option.

Between the gerrymandering, electoral college, stacked courts in case it was close, the whole thing was rigged already. All the land outvoted the people.

Yes, but it’ll likely still be faster, just not as dramatically. Half of 4-94x is still 2-47x faster.

http://vgmusic.com/

Where do you live, Alberta? Or one of the maritimes??