![project m cobalt legacy hackless project m cobalt legacy hackless](https://i.ytimg.com/vi/1DWidAE_uV0/hqdefault.jpg)
The Fund makes available the results of its work in meetings with decision-makers, reports, articles, and books. (backport to 3.The Milbank Memorial Fund is an endowed national foundation that engages in nonpartisan analysis, study, research and communication on significant issues in health policy.This is a request we've got several times, so here it is. this should be handled through a trigger mechanism when changing some attributes however, we need to be clever as changing the public name of a controller is important for nearly all nodes while changing the public name of a compute node doesn't matter.updating the config on nodes after editing one node (changing alias, public name, availability zone) - including dns config on dns-server.this should be handled through a trigger mechanism.reconfiguring the repos on the nodes when updating the list of repos in crowbar webui.this should be handled through a trigger mechanism when applying a barclamp.updating config of a service, when another service is changed on another node (for instance: making sure the neutron config is up-to-date on nova-compute nodes).we might keep the periodic run just for this if we do that, we would only run this in "ready" state, and instead add a "converging" state that would allow to run all roles.heartbeat through ohai data (from deployer-client role).Currently, periodic chef-client runs are useful for: We want to have Crowbar less invasive, and part of this is to not have chef reconfigure everything every time. Go towards minimum amount of recipes on each chef-client run Conclusion is that we don't need most of the roles on boot.MISSING: crowbar-ceph roles, crowbar-ha roles (especially with drbd).
#Project m cobalt legacy hackless update#
I didn't check dns-client (currently configured to be running for "all" states, sounds wrong), crowbar (only matters for admin server anyway), deployer-client (required for ohai data to be updated), ipmi-discover (might be needed to update the ipmi data on boot), network (this needs some more attention, as there's code to kill NICs not managed by crowbar on boot)
![project m cobalt legacy hackless project m cobalt legacy hackless](https://pbs.twimg.com/media/DXofluqW0AERnDo.jpg)
It seems that we're doing a good job at making the config persistent on disk, without a need for chef: