On 04/05/2012 10:17 AM, Aleksey Tsalolikhin wrote: > I'd like to suggest removing cf_promises_validated from failsafe.cf > as it raises the barrier to entry for new users. People really trip > over that. (That's from my training experience.)
I like doing the optimization on that from the get go. I do think it needs to be highlighted more frequently on how it affects policy updates. When I am doing internal training with CFEngine I explain that to death because it is clever and not exactly obvious for new users. > It's a clever optimization for high-scale users but it adds complexity > perhaps unnecessarily at the lower end (hundreds of servers) and it > adds a dependency on time synchronization which breaks policy > distribution if the clock on the server is behind. They are adding a date or timestamp to the file in 3.3.0 so we can use digest to check for differences instead of relying on time synchronization. > More organizations use CFEngine to manage tens or hundreds of servers; > there are less organizations using it to manage > thousands, and even less tens of thousands of servers. So we have > an optimization for a few people at the high end making it harder for the > many people at the low end to start using the product. -- Nick Anderson <n...@cmdln.org> _______________________________________________ Help-cfengine mailing list Help-cfengine@cfengine.org https://cfengine.org/mailman/listinfo/help-cfengine
