propellor/src/Propellor/Property/ControlHeir.hs, branch master gnusosa's centralized propellor repository for hosts spin-up. https://git.gnusosa.net/propellor/atom?h=master 2015-10-21T19:35:52Z Rewrote Propellor.Property.ControlHeir one more time, renaming it to Propellor.Property.Conductor. 2015-10-21T19:35:52Z Joey Hess joeyh@joeyh.name 2015-10-21T19:08:41Z urn:sha1:84413dd508f20e4f62293b4c925962b8dfe2987e Wow, really.. So, this gets back to having properties that are added to hosts to say what they conduct. I think that conducts webservers `before` conducts dnsserver is an important thing to be able to express. Untested except for eyeballing the resulting Host data. refactor 2015-10-21T03:37:21Z Joey Hess joeyh@joeyh.name 2015-10-21T03:37:21Z urn:sha1:0e39d53352b982022747e451676bc6a66e3d9acc simplify privdata propigation to spin from controller 2015-10-21T03:33:19Z Joey Hess joeyh@joeyh.name 2015-10-21T03:33:19Z urn:sha1:745f42c1499749345c32736342959584587c9b57 reword 2015-10-21T01:42:52Z Joey Hess joeyh@joeyh.name 2015-10-21T01:42:52Z urn:sha1:2f9c0bf950e9e879ca374ab8fc523c5486f156bd build warnings 2015-10-21T01:33:22Z Joey Hess joeyh@joeyh.name 2015-10-21T01:33:22Z urn:sha1:c1e0a968668c6469524337ac73c19ea0f495a62c The Propellor.Property.Spin added in the last release is replaced with a very different Propellor.Property.ControlHeir. 2015-10-21T01:28:49Z Joey Hess joeyh@joeyh.name 2015-10-21T01:28:49Z urn:sha1:51a831c56ec42a9702ac8eb6980d9b9947a5ad30 Rethought it because it turned out that propigating the PrivData rendered the loop detection pointless, because when there was a loop, each host included the other's PrivData, which in turn lead to a loop. And, it was not possible to break that loop. So, changed from adding properties to hosts to a top-down hierarchy that makes changes as needed when applied to the hosts. Which makes it easy to detect and break loops. Aka: The Ur Quan know what they're up to.