Quantcast
Channel: StudioSysAdmins Message Board
Viewing all articles
Browse latest Browse all 3749

Choosing a conf managment tool for a Windows / Mac Envrionment

$
0
0
Choosing a conf managment tool for a Windows / Mac Envrionment
posted by Greg Dickie on Nov. 6, 2015, 6:10 p.m. (1 day ago)

We are trying to with various levels of success. The managedmac implementation is not complete so we cannot set VNC access for example. We only install munki with puppet and then munki installs everything else. The homebrew module has some issues as well. It mostly works though. We are OSX/Linux, have not tried with windows.

Greg



On Fri, 2015-11-06 at 13:28 -0800, Brandon Lindauer wrote:
I remember reading that puppet doesnt handle OS X software installations well, and that it was easier to offload that onto munki (use puppet to trigger munki). Is this still the case, or does this managedmac library solve that?

Is anyone actively using puppet to manage all aspects of their macs?

On Nov 5, 2015, at 2:25 PM, mathieu xavier <matxdotca@GMAIL.COM> wrote:

Michael,

Another option is Puppet. They support both Windows and OS X. One example of a project that leverages this is Managed Mac from SFU.


They use hiera and yaml and puppet and it seems to work for their Mac management needs. 

More info here:


-x

On Nov 5, 2015, at 9:39 AM, Mikael Spade <content@studiosysadmins.com> wrote:

We have a mixed Mac and Windows envrionment here, with our Windows side already having a python/yaml based pipeline for Maya and Nuke setup, and I am looking to deploy a CM tool for managing it all. After doing some research it seems that the top choices would be Ansible, Salt, or Chef, and I was hoping to hear from others on their experiences with working with any of them in a mixed envronment, or any reasons to choose one over the others.

Here's my basic overview of them:

Ansible would be the easiest to deploy and use, since it also uses python/yaml and is agentless. However, it apparently is lacking in the introspection, logging, and documentation department compared to Salt and Chef. Also, couldn't find many people talking about using it with specifically Windows, so I don't know how it performs with Windows or what its limitations might be. Can also be relatively slow in performance.

Salt is more complex than Ansible, but would still be relatively easy to fit in with our existing python/yaml workflow. However, could find even less about using Salt with Windows than Ansible, so also an unknown in regards to that department in terms of actual use.

Chef would be the most complex and difficult to deploy, in particular since it would require us to get used to using Ruby and JSON. It does seem to have the best support for Windows and documentation of all 3 though.

Any thoughts or suggestions are greatly appreci ated!

To unsubscribe from the list send a blank e-mail to mailto:studiosysadmins-discuss-request@studiosysadmins.com?subject=unsubscribe

To unsubscribe from the list send a blank e-mail to mailto:studiosysadmins-discuss-request@studiosysadmins.com?subject=unsubscribe

To unsubscribe from the list send a blank e-mail to mailto:studiosysadmins-discuss-request@studiosysadmins.com?subject=unsubscribe
--
Greg Dickie
514-983-5400
just a guy
Thread Tags:
  discuss-at-studiosysadmins 

0 Responses   0 Plus One's   0 Comments  
 

We are trying to with various levels of success. The managedmac implementation is not complete so we cannot set VNC access for example. We only install munki with puppet and then munki installs everything else. The homebrew module has some issues as well. It mostly works though. We are OSX/Linux, have not tried with windows.

Greg



On Fri, 2015-11-06 at 13:28 -0800, Brandon Lindauer wrote:
I remember reading that puppet doesnt handle OS X software installations well, and that it was easier to offload that onto munki (use puppet to trigger munki). Is this still the case, or does this managedmac library solve that?

Is anyone actively using puppet to manage all aspects of their macs?

On Nov 5, 2015, at 2:25 PM, mathieu xavier <matxdotca@GMAIL.COM> wrote:

Michael,

Another option is Puppet. They support both Windows and OS X. One example of a project that leverages this is Managed Mac from SFU.


They use hiera and yaml and puppet and it seems to work for their Mac management needs. 

More info here:


-x

On Nov 5, 2015, at 9:39 AM, Mikael Spade <content@studiosysadmins.com> wrote:

We have a mixed Mac and Windows envrionment here, with our Windows side already having a python/yaml based pipeline for Maya and Nuke setup, and I am looking to deploy a CM tool for managing it all. After doing some research it seems that the top choices would be Ansible, Salt, or Chef, and I was hoping to hear from others on their experiences with working with any of them in a mixed envronment, or any reasons to choose one over the others.

Here's my basic overview of them:

Ansible would be the easiest to deploy and use, since it also uses python/yaml and is agentless. However, it apparently is lacking in the introspection, logging, and documentation department compared to Salt and Chef. Also, couldn't find many people talking about using it with specifically Windows, so I don't know how it performs with Windows or what its limitations might be. Can also be relatively slow in performance.

Salt is more complex than Ansible, but would still be relatively easy to fit in with our existing python/yaml workflow. However, could find even less about using Salt with Windows than Ansible, so also an unknown in regards to that department in terms of actual use.

Chef would be the most complex and difficult to deploy, in particular since it would require us to get used to using Ruby and JSON. It does seem to have the best support for Windows and documentation of all 3 though.

Any thoughts or suggestions are greatly appreci ated!

To unsubscribe from the list send a blank e-mail to mailto:studiosysadmins-discuss-request@studiosysadmins.com?subject=unsubscribe

To unsubscribe from the list send a blank e-mail to mailto:studiosysadmins-discuss-request@studiosysadmins.com?subject=unsubscribe

To unsubscribe from the list send a blank e-mail to mailto:studiosysadmins-discuss-request@studiosysadmins.com?subject=unsubscribe
--
Greg Dickie
514-983-5400
just a guy

Viewing all articles
Browse latest Browse all 3749

Trending Articles