1. Working with DSC in the context of 3rd party CM tooling. Part 8: Puppet Server

    In this post I’m going to install a Puppet Server (Master) and try to have my previously installed Puppet agent hooked up to it. From there I’m going to try to have the manifest I previously created to be assigned to the agent. I have no up front knowledge on this at all so if this post feels a bit more pieced together than the previous ones, my apologies :) …


  2. Working with DSC in the context of 3rd party CM tooling. Part 7: Puppet notifications

    Like Chef, Puppet also support the concept of notifications. A change event on one resource triggers an action on another resource. Support for this kind of functionality helps with keeping resources monotonic and within the boundaries of the technology domain that is being governed by the resource. For example: a Website resource doesn’t have to restart a service, as the service resource can be notified of the change event that requires the restart and handles that job that obviously belongs to the service resource domain. It also keeps you from writing custom resources when an existing resource doesn’t do that one thing you need but could be handled using a notification to another resource. …


  3. Working with DSC in the context of 3rd party CM tooling. Part 6: Puppet intro

    In this post I start my investigation on how to get started with puppet. Again (as with the chef series), the main objective is to see how puppet can improve the experience on using DSC, so the investigation will mainly focus on the integration / interaction between the two. …


  4. Working with DSC in the context of 3rd party CM tooling. Part 5: Chef Client Settings

    In the last few post we looked at a wide range of Chef functionalities that offer a rich experience when working with DSC resources. They key here is that you don’t use the DSC LCM at all. Basically we interchange the LCM for the chef client and have it consume DSC resources while ignoring everything else. …


  5. Working with DSC in the context of 3rd party CM tooling. Part 4: Chef bootstrapping

    In this post I’ll continue my investigation on using DSC with Chef. In this post I’ll look at how we can onboard new nodes more easily (without the need to log into them interactively) and have them apply a run-list immediately (have the initial convergence to be part of the Chef agent install or VM deployment process). There won’t be much DSC content in this post but it is good to know how to get your nodes into management and have a configuration bootstrapped! …