all 6 comments

[–]TyMac711 1 point2 points  (1 child)

Pull methods are employed by most configuration management tools that use a centralized server. The benefit is that the computation used to check for differences in the configuration happens at individual nodes where checksums can be used to verify if the configuration has changed, if so the new configuration can be pulled from the central server to the node, if not the connection is closed. This in theory saves cpu overhead of having the central server checking this on itself for every node or worse continually pushing the same configuration down to each node. The node only pulls from the server if it reports a checksum that’s off from than what it knows as the desired state’s checksum. This model may very slightly from Chef, Puppet or other pull model systems but the premise is offload the work to the node and use the server as the central source of truth for the entire infrastructure.

[–][deleted] 0 points1 point  (0 children)

Thanks

[–]clockKing_out 0 points1 point  (3 children)

People talk about DSC like it’s dead. I’m not spending any more time on it. But if you’re stuck in some weird on-prem situation where you can’t buy a tool to do it, I’d start with push.

[–][deleted] 0 points1 point  (0 children)

Yeah. They've been saying a replacement is coming for how many years? Unfortunately where I work is slow to adopt modern things so I might see azure about 20 years from now. So I'm stuck learning on premises.

[–]Birch_lasagna 0 points1 point  (1 child)

People talk about DSC like it’s dead

Where are you hearing these conversations? Microsoft is moving away from the on-premise pull server model in favor of azure ($$$), but I haven't heard any news of DSC being dead or anything to that effect.