Automation with Ansible, Salt etc - at what point?
-
@scottalanmiller said in Automation with Ansible, Salt etc - at what point?:
@pete-s said in Automation with Ansible, Salt etc - at what point?:
Ansible seems to be the least complicated to get started with so I guess that'll be as good as anything.
Syntactically yes.
Salt has the simpler architecture, because it is clients reaching the server, not the server reaching the clients.
That’s the main thing I like about salt. But damn, if the minion service is hosed for whatever reason can be a real pain.
-
@black3dynamite said in Automation with Ansible, Salt etc - at what point?:
@scottalanmiller said in Automation with Ansible, Salt etc - at what point?:
@pete-s said in Automation with Ansible, Salt etc - at what point?:
Ansible seems to be the least complicated to get started with so I guess that'll be as good as anything.
Syntactically yes.
Salt has the simpler architecture, because it is clients reaching the server, not the server reaching the clients.
That’s the main thing I like about salt. But damn, if the minion service is hosed for whatever reason can be a real pain.
SaltStack can do agentless as well, like Ansible.
-
@obsolesce said in Automation with Ansible, Salt etc - at what point?:
@black3dynamite said in Automation with Ansible, Salt etc - at what point?:
@scottalanmiller said in Automation with Ansible, Salt etc - at what point?:
@pete-s said in Automation with Ansible, Salt etc - at what point?:
Ansible seems to be the least complicated to get started with so I guess that'll be as good as anything.
Syntactically yes.
Salt has the simpler architecture, because it is clients reaching the server, not the server reaching the clients.
That’s the main thing I like about salt. But damn, if the minion service is hosed for whatever reason can be a real pain.
SaltStack can do agentless as well, like Ansible.
Ansible uses winrm to manage Windows. Can Salt do the same? Because Salt agentless uses SSH, so I would need to setup ssh server on Windows.
https://docs.saltstack.com/en/getstarted/ssh/index.html -
@black3dynamite said in Automation with Ansible, Salt etc - at what point?:
@obsolesce said in Automation with Ansible, Salt etc - at what point?:
@black3dynamite said in Automation with Ansible, Salt etc - at what point?:
@scottalanmiller said in Automation with Ansible, Salt etc - at what point?:
@pete-s said in Automation with Ansible, Salt etc - at what point?:
Ansible seems to be the least complicated to get started with so I guess that'll be as good as anything.
Syntactically yes.
Salt has the simpler architecture, because it is clients reaching the server, not the server reaching the clients.
That’s the main thing I like about salt. But damn, if the minion service is hosed for whatever reason can be a real pain.
SaltStack can do agentless as well, like Ansible.
Ansible uses winrm to manage Windows. Can Salt do the same? Because Salt agentless uses SSH, so I would need to setup ssh server on Windows.
https://docs.saltstack.com/en/getstarted/ssh/index.htmlWhy would you want to do that, though? The agent is the key reason to be on Salt in the first place.
-
If you don't want the agent, why not use Ansible?
-
@black3dynamite said in Automation with Ansible, Salt etc - at what point?:
@obsolesce said in Automation with Ansible, Salt etc - at what point?:
@black3dynamite said in Automation with Ansible, Salt etc - at what point?:
@scottalanmiller said in Automation with Ansible, Salt etc - at what point?:
@pete-s said in Automation with Ansible, Salt etc - at what point?:
Ansible seems to be the least complicated to get started with so I guess that'll be as good as anything.
Syntactically yes.
Salt has the simpler architecture, because it is clients reaching the server, not the server reaching the clients.
That’s the main thing I like about salt. But damn, if the minion service is hosed for whatever reason can be a real pain.
SaltStack can do agentless as well, like Ansible.
Ansible uses winrm to manage Windows. Can Salt do the same? Because Salt agentless uses SSH, so I would need to setup ssh server on Windows.
https://docs.saltstack.com/en/getstarted/ssh/index.htmlOh för Windows no. Definitely use the agent with windows it's way more secure.
-
@scottalanmiller said in Automation with Ansible, Salt etc - at what point?:
@black3dynamite said in Automation with Ansible, Salt etc - at what point?:
@obsolesce said in Automation with Ansible, Salt etc - at what point?:
@black3dynamite said in Automation with Ansible, Salt etc - at what point?:
@scottalanmiller said in Automation with Ansible, Salt etc - at what point?:
@pete-s said in Automation with Ansible, Salt etc - at what point?:
Ansible seems to be the least complicated to get started with so I guess that'll be as good as anything.
Syntactically yes.
Salt has the simpler architecture, because it is clients reaching the server, not the server reaching the clients.
That’s the main thing I like about salt. But damn, if the minion service is hosed for whatever reason can be a real pain.
SaltStack can do agentless as well, like Ansible.
Ansible uses winrm to manage Windows. Can Salt do the same? Because Salt agentless uses SSH, so I would need to setup ssh server on Windows.
https://docs.saltstack.com/en/getstarted/ssh/index.htmlWhy would you want to do that, though? The agent is the key reason to be on Salt in the first place.
I'm all good with using the agent. But until I figured out the problem I'm having the agent on my Windows machines, Ansible will be used.
-
@black3dynamite said in Automation with Ansible, Salt etc - at what point?:
@scottalanmiller said in Automation with Ansible, Salt etc - at what point?:
@black3dynamite said in Automation with Ansible, Salt etc - at what point?:
@obsolesce said in Automation with Ansible, Salt etc - at what point?:
@black3dynamite said in Automation with Ansible, Salt etc - at what point?:
@scottalanmiller said in Automation with Ansible, Salt etc - at what point?:
@pete-s said in Automation with Ansible, Salt etc - at what point?:
Ansible seems to be the least complicated to get started with so I guess that'll be as good as anything.
Syntactically yes.
Salt has the simpler architecture, because it is clients reaching the server, not the server reaching the clients.
That’s the main thing I like about salt. But damn, if the minion service is hosed for whatever reason can be a real pain.
SaltStack can do agentless as well, like Ansible.
Ansible uses winrm to manage Windows. Can Salt do the same? Because Salt agentless uses SSH, so I would need to setup ssh server on Windows.
https://docs.saltstack.com/en/getstarted/ssh/index.htmlWhy would you want to do that, though? The agent is the key reason to be on Salt in the first place.
I'm all good with using the agent. But until I figured out the problem I'm having the agent on my Windows machines, Ansible will be used.
Oh, I guess I missed that. The agent on Windows is not working? We've not seen that issue, we have a lot of Windows agents.
-
@black3dynamite said in Automation with Ansible, Salt etc - at what point?:
@scottalanmiller said in Automation with Ansible, Salt etc - at what point?:
@black3dynamite said in Automation with Ansible, Salt etc - at what point?:
@obsolesce said in Automation with Ansible, Salt etc - at what point?:
@black3dynamite said in Automation with Ansible, Salt etc - at what point?:
@scottalanmiller said in Automation with Ansible, Salt etc - at what point?:
@pete-s said in Automation with Ansible, Salt etc - at what point?:
Ansible seems to be the least complicated to get started with so I guess that'll be as good as anything.
Syntactically yes.
Salt has the simpler architecture, because it is clients reaching the server, not the server reaching the clients.
That’s the main thing I like about salt. But damn, if the minion service is hosed for whatever reason can be a real pain.
SaltStack can do agentless as well, like Ansible.
Ansible uses winrm to manage Windows. Can Salt do the same? Because Salt agentless uses SSH, so I would need to setup ssh server on Windows.
https://docs.saltstack.com/en/getstarted/ssh/index.htmlWhy would you want to do that, though? The agent is the key reason to be on Salt in the first place.
I'm all good with using the agent. But until I figured out the problem I'm having the agent on my Windows machines, Ansible will be used.
I've got the agent deployed across 700 win7, Win10, win server, and Hyper-V servers at work. All working, installed via chocolatey.
What is the issue you are having?
Edit: 50-100 of those 700 are Linux and no chocolatey.
-
@obsolesce said in Automation with Ansible, Salt etc - at what point?:
@black3dynamite said in Automation with Ansible, Salt etc - at what point?:
@scottalanmiller said in Automation with Ansible, Salt etc - at what point?:
@black3dynamite said in Automation with Ansible, Salt etc - at what point?:
@obsolesce said in Automation with Ansible, Salt etc - at what point?:
@black3dynamite said in Automation with Ansible, Salt etc - at what point?:
@scottalanmiller said in Automation with Ansible, Salt etc - at what point?:
@pete-s said in Automation with Ansible, Salt etc - at what point?:
Ansible seems to be the least complicated to get started with so I guess that'll be as good as anything.
Syntactically yes.
Salt has the simpler architecture, because it is clients reaching the server, not the server reaching the clients.
That’s the main thing I like about salt. But damn, if the minion service is hosed for whatever reason can be a real pain.
SaltStack can do agentless as well, like Ansible.
Ansible uses winrm to manage Windows. Can Salt do the same? Because Salt agentless uses SSH, so I would need to setup ssh server on Windows.
https://docs.saltstack.com/en/getstarted/ssh/index.htmlWhy would you want to do that, though? The agent is the key reason to be on Salt in the first place.
I'm all good with using the agent. But until I figured out the problem I'm having the agent on my Windows machines, Ansible will be used.
I've got the agent deployed across 700 win7, Win10, win server, and Hyper-V servers at work. All working, installed via chocolatey.
What is the issue you are having?
Edit: 50-100 of those 700 are Linux.
Its probably something stupid on my part but It's only happening on some of my Windows 10 1803 machines. They are installed via chocolatey too.
The service gets stuck in a paused state. It is working great on the other Windows 10, 7, servers, Hyper-V and Linux. -
@black3dynamite said in Automation with Ansible, Salt etc - at what point?:
@obsolesce said in Automation with Ansible, Salt etc - at what point?:
@black3dynamite said in Automation with Ansible, Salt etc - at what point?:
@scottalanmiller said in Automation with Ansible, Salt etc - at what point?:
@black3dynamite said in Automation with Ansible, Salt etc - at what point?:
@obsolesce said in Automation with Ansible, Salt etc - at what point?:
@black3dynamite said in Automation with Ansible, Salt etc - at what point?:
@scottalanmiller said in Automation with Ansible, Salt etc - at what point?:
@pete-s said in Automation with Ansible, Salt etc - at what point?:
Ansible seems to be the least complicated to get started with so I guess that'll be as good as anything.
Syntactically yes.
Salt has the simpler architecture, because it is clients reaching the server, not the server reaching the clients.
That’s the main thing I like about salt. But damn, if the minion service is hosed for whatever reason can be a real pain.
SaltStack can do agentless as well, like Ansible.
Ansible uses winrm to manage Windows. Can Salt do the same? Because Salt agentless uses SSH, so I would need to setup ssh server on Windows.
https://docs.saltstack.com/en/getstarted/ssh/index.htmlWhy would you want to do that, though? The agent is the key reason to be on Salt in the first place.
I'm all good with using the agent. But until I figured out the problem I'm having the agent on my Windows machines, Ansible will be used.
I've got the agent deployed across 700 win7, Win10, win server, and Hyper-V servers at work. All working, installed via chocolatey.
What is the issue you are having?
Edit: 50-100 of those 700 are Linux.
Its probably something stupid on my part but It's only happening on some of my Windows 10 1803 machines. They are installed via chocolatey too.
The service gets stuck in a paused state. It is working great on the other Windows 10, 7, servers, Hyper-V and Linux.I think that means it has no contact with the salt master.
