 |
Colton Myers |
at Jan 12, 2015 at 7:37 pm
|
⇧ | 
| |
Sorry for the late reply, catching up after the holidays.
It's really personal preference. I prefer option 1 or option 2, personally, because managing top data in a branching multi-environment setup can be hairy, since topfiles are compiled across environments.
But any of these options would work.
--
Colton Myers
Platform Engineer, SaltStack
@basepi on Github/Twitter/IRC
On Dec 23, 2014, at 3:43 AM, peter ducai wrote:hi all,
we have several networks with few servers (overall less then 50) and thus i'm curious what is best practice to setup salt for them
1. one master server and rest done through top file (for example one jenkins state for installation but several jenkins-job states for each environment/team/subnet)
or
2. master for each subnet/environment
or
3. branching (via GIT/SVN) state files for each team/environment separately.
thanks for any suggestions
--
You received this message because you are subscribed to the Google Groups "Salt-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to salt-users+
[email protected] For more options, visit
https://groups.google.com/d/optout <
https://groups.google.com/d/optout>.
--
You received this message because you are subscribed to the Google Groups "Salt-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
[email protected].
For more options, visit
https://groups.google.com/d/optout.
