the real "killer app" of "workload orchestration" is the active control loops, configured (somewhat naturally) declaratively. Ansible and other configuration m

the real "killer app" of "workload orchestration" is the active control loops, configured (somewhat naturally) declaratively. Ansible and other configuration managers and provisioning tools - as far as I know - had no way to do this. (they had policy conformance checks and whatnot, but fundamentally they did not make it easy to get to the desired good state, they ran on-demand and had to rely on ad-hoc information gathering, which made them slooooow and brittle)