I would like to get some design advice from the experts we are looking at using DSC for Configuration Management quite extensively inside our client base.
This is the flow of the deployment model that we are looking at:
We currently wrap the Chocolatey DSC module inside a Composite resource. We then pass some custom parameters to the Chocolatey module. The Chocolatey package has some intelligence added to create a “settings file” from the custom parameters. This is then deployed to Load Balanced group of servers. One caveat we have is that the same server can run multiple version of the same software package so we will need to plan for that.
- What is the recommended approach to handle package versions in DSC, seeing as multiple can be run on the same server?
- Is Chocolatey the best resource for this or is there other resources we can look at?
- Is it advisable for the DSC module to host the logic required to build the settings file or should we keep it in the Chocolatey package?
- Any other ideas or advice would be great.