not entirely sure if this is the right subforum to ask this question, but I was wondering if there's a part of the schema that allows for a (generic) way to start/stop/configure software on the BMC? (And by extension, on the host, but that would just be out of curiosity)
I'm thinking of configuration management daemons, custom provisioning clients, things like that. I'm aware that there is the NetworkProtocol subtree, but that is a very opinionated way of doing things and not exactly what I'm looking for.
If I'm completely on the wrong path here, I'd appreciate any links to further reading that is not the specification
It's not defined in the schema today. There is a "Reset" Action in Manager to allow a reboot/restart of the BMC, but not individual controls of processes/services. In general we'd probably want to define "features" to enable/disable to avoid implementation-dependent properties (no interoperability on process names, etc.). So yes, ManagerNetworkProtocol does do some of that for purely protocol-level features, not for generic processes.
There's nothing for control of host-OS-based processes. I'm sure we'd get much support for doing that in the standard - but I'm curious what the use case is?