5 ms·

Edited my response above a bit. We're going to be adding Windows support this year but have been concentrating on *nix operating systems as that's the core of

Edited my response above a bit. We're going to be adding Windows support this year but have been concentrating on *nix operating systems as that's the core of our user base. Definitely would like feedback on what specifically on Windows you are managing and for what use cases.

karlmdavis 13y ago
Well, I've got two main use cases for configuration management tools: 1) managing CI build farms, and 2) managing my home network. Both of those environments are mixed-OS. The build farms are composed of a Jenkins master with multiple slaves of various OSes: Ubuntu, RHEL, and Windows. My home network is running Kerberos and OpenAFS (amongst many other random things [1]) on Ubuntu and Windows. > We don't believe in hiding too many OS details from you -- for instance, not only do package names vary between distributions but think about how Apache is managed so very differently between Ubuntu and CentOS -- in fact, we've observed in many cases that trying to pave over those things can make content a lot harder to work on. I don't know... the Puppet module for Apache [2] seems to do a reasonably good job of managing this. Admittedly, pretty much none of the "main" Puppet modules support Windows, but the underlying resource system absolutely does, so adding that support is just a matter of submitting pull requests to the modules. [1] Everything's documented here: https://justdavis.com/karl/it/ https://justdavis.com/karl/it/ [2] https://forge.puppetlabs.com/puppetlabs/apache https://forge.puppetlabs.com/puppetlabs/apache
- mpdehaan2 13y ago
  Yeah that's in a module. This would be akin to a role in Ansible. If you are looking at the core language for either, it doesn't hide those things but you can put whatever logic you want in the role/playbook/manifest/etc. Hope this explains things! Thanks for more info.

karlmdavis 13y ago

Well, I've got two main use cases for configuration management tools: 1) managing CI build farms, and 2) managing my home network. Both of those environments are mixed-OS. The build farms are composed of a Jenkins master with multiple slaves of various OSes: Ubuntu, RHEL, and Windows. My home network is running Kerberos and OpenAFS (amongst many other random things [1]) on Ubuntu and Windows. > We don't believe in hiding too many OS details from you -- for instance, not only do package names vary between distributions but think about how Apache is managed so very differently between Ubuntu and CentOS -- in fact, we've observed in many cases that trying to pave over those things can make content a lot harder to work on. I don't know... the Puppet module for Apache [2] seems to do a reasonably good job of managing this. Admittedly, pretty much none of the "main" Puppet modules support Windows, but the underlying resource system absolutely does, so adding that support is just a matter of submitting pull requests to the modules. [1] Everything's documented here: https://justdavis.com/karl/it/ https://justdavis.com/karl/it/ [2] https://forge.puppetlabs.com/puppetlabs/apache https://forge.puppetlabs.com/puppetlabs/apache

mpdehaan2 13y ago
Yeah that's in a module. This would be akin to a role in Ansible. If you are looking at the core language for either, it doesn't hide those things but you can put whatever logic you want in the role/playbook/manifest/etc. Hope this explains things! Thanks for more info.