[ipmifatwa]

Open up your computer, pull out the bmc, throw it in the garbage. If you are reliant on these things then you are still in a pet-computer world and you’ll benefit greatly by moving to the cattle model. This article has a section on why you need a bmc but doesn’t succeed in advocating for it. It’s another computer inside your main computer with its own set of flaws, bugs, and costs.

[bradfitz]

Actually, a good BMC lets you automate your fleet of machines and treat them like cattle, rebooting/reimaging on demand.

[Lammy]

> a good BMC

I hope to see such a thing some day. The code quality and support lifecycles for these things are horrendous.

[ipmifatwa]

Cattle is when you DGAF that 1% of your machines failed to reboot. A tech can deal with it whenever.

[MoosePirate]

How are you rebooting your cattle though if not via the BMC?

[tbyehl]

More importantly, how do those cattle become cattle in the first place without BMC? How do you turn them into another breed of cattle without BMC?

Not that it can't be done... but that's a system dependent on the hardware doing the right thing, as opposed to a system that can tell the hardware what to do every step of the way.

[gpapilion]

There are other solutions, like network pdus. It’s different but does the same job.

[tedivm]

I'm also curious how they're reimaging those machines.

[ipmifatwa]

What's wrong with PXE boot?

[AdamJacobMuller]

How are you triggering the machine to PXE boot? How are you recovering from situations where the machine becomes unresponsive or needs someone to look at a console to see why a failure occurred?