4 ms·
I agree this seems overly complicated, however I am for anything that helps get away from systemd. > Expect your nodes to go down all the time. Got it. When I
by djsumdog 10y ago
I agree this seems overly complicated, however I am for anything that helps get away from systemd.
> Expect your nodes to go down all the time. Got it.
When I deploy containers, our system (marathon on DCOS) does rolling updates where it scheduled new nodes and then gets rid of the old ones in a rolling/rotating fashion. That's how high availability works. If your nodes go down in a controlled fashion for updates, it shouldn't be a problem.
- peterwwillis 10y agoHA was never about replacing whole nodes just to make minor changes. Rolling updates, sure, when the system isn't complex enough to do updates in place. The thing is, initrd's are always read-only anyway. But i'm annoyed that they're trying to justify this by saying it's good for security or more reliable, etc. It's just a legacy of the old design. And they have tools built into it to let it be managed remotely - but refuse to let this configure it live? So it can still be owned, but just not in a persistent state (unless you find persistent storage).
- sagichmal 10y agoRolling updates of immutable artifacts is, on balance, vastly preferable to updating software in-place with e.g. patches.
- peterwwillis 10y agoAnd is there some evidence-based research or white paper that justifies that claim? Because it sounds like the cargo cult of Google container networks.