Mixing
How do I update the Nginx configuration file on many identical servers at the same time?
We've got a fleet of Nginx servers on Amazon EC2 where we occasionally need to update the configuration files to implement new settings.
Currently we have the configurations in a custom AMI and if we need to update we have to rebuild the AMI and then EC2 instances. We've got some helper scripts, but it's still quite an effort to do that. Is there is some better way?
amazon-web-services amazon-ec2
edited Jan 16 at 5:00
Peter Mortensen
2,13242124
asked Jan 15 at 3:06
BububuBububu
1607
add a comment |
We've got a fleet of Nginx servers on Amazon EC2 where we occasionally need to update the configuration files to implement new settings.
Currently we have the configurations in a custom AMI and if we need to update we have to rebuild the AMI and then EC2 instances. We've got some helper scripts, but it's still quite an effort to do that. Is there is some better way?
amazon-web-services amazon-ec2
edited Jan 16 at 5:00
Peter Mortensen
2,13242124
asked Jan 15 at 3:06
BububuBububu
1607
3
ansible, saltstack to name a few.
– poige
Jan 15 at 3:12
add a comment |
We've got a fleet of Nginx servers on Amazon EC2 where we occasionally need to update the configuration files to implement new settings.
Currently we have the configurations in a custom AMI and if we need to update we have to rebuild the AMI and then EC2 instances. We've got some helper scripts, but it's still quite an effort to do that. Is there is some better way?
amazon-web-services amazon-ec2
edited Jan 16 at 5:00
Peter Mortensen
2,13242124
asked Jan 15 at 3:06
BububuBububu
1607
We've got a fleet of Nginx servers on Amazon EC2 where we occasionally need to update the configuration files to implement new settings.
Currently we have the configurations in a custom AMI and if we need to update we have to rebuild the AMI and then EC2 instances. We've got some helper scripts, but it's still quite an effort to do that. Is there is some better way?
amazon-web-services amazon-ec2
amazon-web-services amazon-ec2
edited Jan 16 at 5:00
Peter Mortensen
2,13242124
asked Jan 15 at 3:06
BububuBububu
1607
edited Jan 16 at 5:00
Peter Mortensen
2,13242124
asked Jan 15 at 3:06
BububuBububu
1607
edited Jan 16 at 5:00
Peter Mortensen
2,13242124
edited Jan 16 at 5:00
Peter Mortensen
2,13242124
edited Jan 16 at 5:00
Peter Mortensen
2,13242124
2,13242124
asked Jan 15 at 3:06
BububuBububu
1607
asked Jan 15 at 3:06
BububuBububu
1607
asked Jan 15 at 3:06
BububuBububu
1607
1607
3
ansible, saltstack to name a few.
– poige
Jan 15 at 3:12
add a comment |
3
ansible, saltstack to name a few.
– poige
Jan 15 at 3:12
3
3
ansible, saltstack to name a few.
– poige
Jan 15 at 3:12
ansible, saltstack to name a few.
– poige
Jan 15 at 3:12
add a comment |
4 Answers
4
active
oldest
votes
There are a number of concepts that you can leverage.
The key to success is automation
First option is to keep doing what you're doing now, i.e. rebuild the EC2s with every configuration change. Just in a fully automated way.
As you're now doing configuration updates through AMIs you take this one step further and create a pipeline that, upon a configuration file change in some repository, will:
- Automatically build a new AMI - one of the most popular tools to do that is Packer
- Automatically rebuild your Nginx fleet - you should already have all the Nginx servers in an Auto-Scaling Group with an Application Load Balancer in front. If you don't you should as it will make the update as simple as updating the ASG Launch Configuration and waiting for the instances to get re-built from the new AMI.
Second option is to keep the instances in place and only deploy the configuration files, without rebuilding them. Generally you can treat configuration files as code and deploy your configuration changes the same way you would deploy code releases. AWS has many tools to help with that.
AWS Elastic Beanstalk that uses Chef internally and you can script your Nginx updates this way.
AWS Code Deploy which is a fully scriptable deployment tool that integrates well with other parts of the AWS Code Suite:
Code Commit where you can keep your Nginx configuration files in Git.
Code Pipeline that can automatically trigger the deployment whenever a configuration file is updated in Code Commit.
Ansible or Puppet which are popular non-AWS tools that can help you keep all the servers configured the same way.
Once you're comfortable with automating these Nginx configuration updates you may want to extend the automation to the rest of your infrastructure.
There is a great whitepaper Overview of Deployment Options on AWS that will give you a nice overview.
I hope that helps :)
edited Jan 16 at 5:04
Peter Mortensen
2,13242124
answered Jan 15 at 4:16
MLuMLu
8,08712141
An alternative to Ansible or Puppet is Salt, which is designed for a master / minion-type of setup and sort-of optimized for larger-scale deployments.
– Araho
Jan 16 at 8:56
add a comment |
Store your configurations on EFS, and mount EFS in the location Nginx configurations are expected. Alternately put them on Amazon S3 and run a sync occasionally, or use s3fs (beware s3fs may not be good enough for production use).
When you need change your configuration, increase your autoscaling group desired size to double what you need to trigger new instances with the new configuration, and then back down to what you need which will remove the old instances. Alternately just do a rolling reboot of the servers.
Another option is to just push the new configurations to your server using a basic automation tool, like AWS code deploy.
The fully automated options above are technically better and cleaner, but if you rarely change configurations and want an easy solution this could help.
edited Jan 16 at 5:06
Peter Mortensen
2,13242124
answered Jan 15 at 8:20
TimTim
17.6k41848
add a comment |
AWS Run Command
https://docs.aws.amazon.com/systems-manager/latest/userguide/execute-remote-commands.html
Or you could use Opsworks
https://aws.amazon.com/opsworks/
answered Jan 15 at 19:40
Chris_WorkChris_Work
565
This is almost exactly the use-case for Run Command and Systems Manager
– danimal
Jan 15 at 22:38
add a comment |
Rebuilding the AMIs or creating a fully fledged deployment pipelines like the others suggest just for a config file change seems like an overkill. You should use Ansible to push out changes and to keep all your nodes in sync. There are many Ansible modules that can help you automate the common tasks.
answered Jan 15 at 10:35
I-P-XI-P-X
1389
One benefit of immutable infrastructure is you know that you don't have any "pet" servers that are fragile and must be maintained. That gives you confidence that you can create more servers in prod / DR / testing without issue.
– Tim
Jan 15 at 18:16
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "2"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f949082%2fhow-do-i-update-the-nginx-configuration-file-on-many-identical-servers-at-the-sa%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
4 Answers
4
active
oldest
votes
4 Answers
4
active
oldest
votes
active
oldest
votes
active
oldest
votes
There are a number of concepts that you can leverage.
The key to success is automation
First option is to keep doing what you're doing now, i.e. rebuild the EC2s with every configuration change. Just in a fully automated way.
As you're now doing configuration updates through AMIs you take this one step further and create a pipeline that, upon a configuration file change in some repository, will:
- Automatically build a new AMI - one of the most popular tools to do that is Packer
- Automatically rebuild your Nginx fleet - you should already have all the Nginx servers in an Auto-Scaling Group with an Application Load Balancer in front. If you don't you should as it will make the update as simple as updating the ASG Launch Configuration and waiting for the instances to get re-built from the new AMI.
Second option is to keep the instances in place and only deploy the configuration files, without rebuilding them. Generally you can treat configuration files as code and deploy your configuration changes the same way you would deploy code releases. AWS has many tools to help with that.
AWS Elastic Beanstalk that uses Chef internally and you can script your Nginx updates this way.
AWS Code Deploy which is a fully scriptable deployment tool that integrates well with other parts of the AWS Code Suite:
Code Commit where you can keep your Nginx configuration files in Git.
Code Pipeline that can automatically trigger the deployment whenever a configuration file is updated in Code Commit.
Ansible or Puppet which are popular non-AWS tools that can help you keep all the servers configured the same way.
Once you're comfortable with automating these Nginx configuration updates you may want to extend the automation to the rest of your infrastructure.
There is a great whitepaper Overview of Deployment Options on AWS that will give you a nice overview.
I hope that helps :)
edited Jan 16 at 5:04
Peter Mortensen
2,13242124
answered Jan 15 at 4:16
MLuMLu
8,08712141
An alternative to Ansible or Puppet is Salt, which is designed for a master / minion-type of setup and sort-of optimized for larger-scale deployments.
– Araho
Jan 16 at 8:56
add a comment |
There are a number of concepts that you can leverage.
The key to success is automation
First option is to keep doing what you're doing now, i.e. rebuild the EC2s with every configuration change. Just in a fully automated way.
As you're now doing configuration updates through AMIs you take this one step further and create a pipeline that, upon a configuration file change in some repository, will:
- Automatically build a new AMI - one of the most popular tools to do that is Packer
- Automatically rebuild your Nginx fleet - you should already have all the Nginx servers in an Auto-Scaling Group with an Application Load Balancer in front. If you don't you should as it will make the update as simple as updating the ASG Launch Configuration and waiting for the instances to get re-built from the new AMI.
Second option is to keep the instances in place and only deploy the configuration files, without rebuilding them. Generally you can treat configuration files as code and deploy your configuration changes the same way you would deploy code releases. AWS has many tools to help with that.
AWS Elastic Beanstalk that uses Chef internally and you can script your Nginx updates this way.
AWS Code Deploy which is a fully scriptable deployment tool that integrates well with other parts of the AWS Code Suite:
Code Commit where you can keep your Nginx configuration files in Git.
Code Pipeline that can automatically trigger the deployment whenever a configuration file is updated in Code Commit.
Ansible or Puppet which are popular non-AWS tools that can help you keep all the servers configured the same way.
Once you're comfortable with automating these Nginx configuration updates you may want to extend the automation to the rest of your infrastructure.
There is a great whitepaper Overview of Deployment Options on AWS that will give you a nice overview.
I hope that helps :)
edited Jan 16 at 5:04
Peter Mortensen
2,13242124
answered Jan 15 at 4:16
MLuMLu
8,08712141
An alternative to Ansible or Puppet is Salt, which is designed for a master / minion-type of setup and sort-of optimized for larger-scale deployments.
– Araho
Jan 16 at 8:56
add a comment |
There are a number of concepts that you can leverage.
The key to success is automation
First option is to keep doing what you're doing now, i.e. rebuild the EC2s with every configuration change. Just in a fully automated way.
As you're now doing configuration updates through AMIs you take this one step further and create a pipeline that, upon a configuration file change in some repository, will:
- Automatically build a new AMI - one of the most popular tools to do that is Packer
- Automatically rebuild your Nginx fleet - you should already have all the Nginx servers in an Auto-Scaling Group with an Application Load Balancer in front. If you don't you should as it will make the update as simple as updating the ASG Launch Configuration and waiting for the instances to get re-built from the new AMI.
Second option is to keep the instances in place and only deploy the configuration files, without rebuilding them. Generally you can treat configuration files as code and deploy your configuration changes the same way you would deploy code releases. AWS has many tools to help with that.
AWS Elastic Beanstalk that uses Chef internally and you can script your Nginx updates this way.
AWS Code Deploy which is a fully scriptable deployment tool that integrates well with other parts of the AWS Code Suite:
Code Commit where you can keep your Nginx configuration files in Git.
Code Pipeline that can automatically trigger the deployment whenever a configuration file is updated in Code Commit.
Ansible or Puppet which are popular non-AWS tools that can help you keep all the servers configured the same way.
Once you're comfortable with automating these Nginx configuration updates you may want to extend the automation to the rest of your infrastructure.
There is a great whitepaper Overview of Deployment Options on AWS that will give you a nice overview.
I hope that helps :)
edited Jan 16 at 5:04
Peter Mortensen
2,13242124
answered Jan 15 at 4:16
MLuMLu
8,08712141
There are a number of concepts that you can leverage.
The key to success is automation
First option is to keep doing what you're doing now, i.e. rebuild the EC2s with every configuration change. Just in a fully automated way.
As you're now doing configuration updates through AMIs you take this one step further and create a pipeline that, upon a configuration file change in some repository, will:
- Automatically build a new AMI - one of the most popular tools to do that is Packer
- Automatically rebuild your Nginx fleet - you should already have all the Nginx servers in an Auto-Scaling Group with an Application Load Balancer in front. If you don't you should as it will make the update as simple as updating the ASG Launch Configuration and waiting for the instances to get re-built from the new AMI.
Second option is to keep the instances in place and only deploy the configuration files, without rebuilding them. Generally you can treat configuration files as code and deploy your configuration changes the same way you would deploy code releases. AWS has many tools to help with that.
AWS Elastic Beanstalk that uses Chef internally and you can script your Nginx updates this way.
AWS Code Deploy which is a fully scriptable deployment tool that integrates well with other parts of the AWS Code Suite:
Code Commit where you can keep your Nginx configuration files in Git.
Code Pipeline that can automatically trigger the deployment whenever a configuration file is updated in Code Commit.
Ansible or Puppet which are popular non-AWS tools that can help you keep all the servers configured the same way.
Once you're comfortable with automating these Nginx configuration updates you may want to extend the automation to the rest of your infrastructure.
There is a great whitepaper Overview of Deployment Options on AWS that will give you a nice overview.
I hope that helps :)
edited Jan 16 at 5:04
Peter Mortensen
2,13242124
answered Jan 15 at 4:16
MLuMLu
8,08712141
edited Jan 16 at 5:04
Peter Mortensen
2,13242124
edited Jan 16 at 5:04
Peter Mortensen
2,13242124
edited Jan 16 at 5:04
Peter Mortensen
2,13242124
2,13242124
answered Jan 15 at 4:16
MLuMLu
8,08712141
answered Jan 15 at 4:16
MLuMLu
8,08712141
answered Jan 15 at 4:16
MLuMLu
8,08712141
8,08712141
An alternative to Ansible or Puppet is Salt, which is designed for a master / minion-type of setup and sort-of optimized for larger-scale deployments.
– Araho
Jan 16 at 8:56
add a comment |
An alternative to Ansible or Puppet is Salt, which is designed for a master / minion-type of setup and sort-of optimized for larger-scale deployments.
– Araho
Jan 16 at 8:56
An alternative to Ansible or Puppet is Salt, which is designed for a master / minion-type of setup and sort-of optimized for larger-scale deployments.
– Araho
Jan 16 at 8:56
An alternative to Ansible or Puppet is Salt, which is designed for a master / minion-type of setup and sort-of optimized for larger-scale deployments.
– Araho
Jan 16 at 8:56
add a comment |
Store your configurations on EFS, and mount EFS in the location Nginx configurations are expected. Alternately put them on Amazon S3 and run a sync occasionally, or use s3fs (beware s3fs may not be good enough for production use).
When you need change your configuration, increase your autoscaling group desired size to double what you need to trigger new instances with the new configuration, and then back down to what you need which will remove the old instances. Alternately just do a rolling reboot of the servers.
Another option is to just push the new configurations to your server using a basic automation tool, like AWS code deploy.
The fully automated options above are technically better and cleaner, but if you rarely change configurations and want an easy solution this could help.
edited Jan 16 at 5:06
Peter Mortensen
2,13242124
answered Jan 15 at 8:20
TimTim
17.6k41848
add a comment |
Store your configurations on EFS, and mount EFS in the location Nginx configurations are expected. Alternately put them on Amazon S3 and run a sync occasionally, or use s3fs (beware s3fs may not be good enough for production use).
When you need change your configuration, increase your autoscaling group desired size to double what you need to trigger new instances with the new configuration, and then back down to what you need which will remove the old instances. Alternately just do a rolling reboot of the servers.
Another option is to just push the new configurations to your server using a basic automation tool, like AWS code deploy.
The fully automated options above are technically better and cleaner, but if you rarely change configurations and want an easy solution this could help.
edited Jan 16 at 5:06
Peter Mortensen
2,13242124
answered Jan 15 at 8:20
TimTim
17.6k41848
add a comment |
Store your configurations on EFS, and mount EFS in the location Nginx configurations are expected. Alternately put them on Amazon S3 and run a sync occasionally, or use s3fs (beware s3fs may not be good enough for production use).
When you need change your configuration, increase your autoscaling group desired size to double what you need to trigger new instances with the new configuration, and then back down to what you need which will remove the old instances. Alternately just do a rolling reboot of the servers.
Another option is to just push the new configurations to your server using a basic automation tool, like AWS code deploy.
The fully automated options above are technically better and cleaner, but if you rarely change configurations and want an easy solution this could help.
edited Jan 16 at 5:06
Peter Mortensen
2,13242124
answered Jan 15 at 8:20
TimTim
17.6k41848
Store your configurations on EFS, and mount EFS in the location Nginx configurations are expected. Alternately put them on Amazon S3 and run a sync occasionally, or use s3fs (beware s3fs may not be good enough for production use).
When you need change your configuration, increase your autoscaling group desired size to double what you need to trigger new instances with the new configuration, and then back down to what you need which will remove the old instances. Alternately just do a rolling reboot of the servers.
Another option is to just push the new configurations to your server using a basic automation tool, like AWS code deploy.
The fully automated options above are technically better and cleaner, but if you rarely change configurations and want an easy solution this could help.
edited Jan 16 at 5:06
Peter Mortensen
2,13242124
answered Jan 15 at 8:20
TimTim
17.6k41848
edited Jan 16 at 5:06
Peter Mortensen
2,13242124
edited Jan 16 at 5:06
Peter Mortensen
2,13242124
edited Jan 16 at 5:06
Peter Mortensen
2,13242124
2,13242124
answered Jan 15 at 8:20
TimTim
17.6k41848
answered Jan 15 at 8:20
TimTim
17.6k41848
answered Jan 15 at 8:20
TimTim
17.6k41848
17.6k41848
add a comment |
add a comment |
AWS Run Command
https://docs.aws.amazon.com/systems-manager/latest/userguide/execute-remote-commands.html
Or you could use Opsworks
https://aws.amazon.com/opsworks/
answered Jan 15 at 19:40
Chris_WorkChris_Work
565
This is almost exactly the use-case for Run Command and Systems Manager
– danimal
Jan 15 at 22:38
add a comment |
AWS Run Command
https://docs.aws.amazon.com/systems-manager/latest/userguide/execute-remote-commands.html
Or you could use Opsworks
https://aws.amazon.com/opsworks/
answered Jan 15 at 19:40
Chris_WorkChris_Work
565
This is almost exactly the use-case for Run Command and Systems Manager
– danimal
Jan 15 at 22:38
add a comment |
AWS Run Command
https://docs.aws.amazon.com/systems-manager/latest/userguide/execute-remote-commands.html
Or you could use Opsworks
https://aws.amazon.com/opsworks/
answered Jan 15 at 19:40
Chris_WorkChris_Work
565
AWS Run Command
https://docs.aws.amazon.com/systems-manager/latest/userguide/execute-remote-commands.html
Or you could use Opsworks
https://aws.amazon.com/opsworks/
answered Jan 15 at 19:40
Chris_WorkChris_Work
565
answered Jan 15 at 19:40
Chris_WorkChris_Work
565
answered Jan 15 at 19:40
Chris_WorkChris_Work
565
answered Jan 15 at 19:40
Chris_WorkChris_Work
565
565
This is almost exactly the use-case for Run Command and Systems Manager
– danimal
Jan 15 at 22:38
add a comment |
This is almost exactly the use-case for Run Command and Systems Manager
– danimal
Jan 15 at 22:38
This is almost exactly the use-case for Run Command and Systems Manager
– danimal
Jan 15 at 22:38
This is almost exactly the use-case for Run Command and Systems Manager
– danimal
Jan 15 at 22:38
add a comment |
Rebuilding the AMIs or creating a fully fledged deployment pipelines like the others suggest just for a config file change seems like an overkill. You should use Ansible to push out changes and to keep all your nodes in sync. There are many Ansible modules that can help you automate the common tasks.
answered Jan 15 at 10:35
I-P-XI-P-X
1389
One benefit of immutable infrastructure is you know that you don't have any "pet" servers that are fragile and must be maintained. That gives you confidence that you can create more servers in prod / DR / testing without issue.
– Tim
Jan 15 at 18:16
add a comment |
Rebuilding the AMIs or creating a fully fledged deployment pipelines like the others suggest just for a config file change seems like an overkill. You should use Ansible to push out changes and to keep all your nodes in sync. There are many Ansible modules that can help you automate the common tasks.
answered Jan 15 at 10:35
I-P-XI-P-X
1389
One benefit of immutable infrastructure is you know that you don't have any "pet" servers that are fragile and must be maintained. That gives you confidence that you can create more servers in prod / DR / testing without issue.
– Tim
Jan 15 at 18:16
add a comment |
Rebuilding the AMIs or creating a fully fledged deployment pipelines like the others suggest just for a config file change seems like an overkill. You should use Ansible to push out changes and to keep all your nodes in sync. There are many Ansible modules that can help you automate the common tasks.
answered Jan 15 at 10:35
I-P-XI-P-X
1389
Rebuilding the AMIs or creating a fully fledged deployment pipelines like the others suggest just for a config file change seems like an overkill. You should use Ansible to push out changes and to keep all your nodes in sync. There are many Ansible modules that can help you automate the common tasks.
answered Jan 15 at 10:35
I-P-XI-P-X
1389
answered Jan 15 at 10:35
I-P-XI-P-X
1389
answered Jan 15 at 10:35
I-P-XI-P-X
1389
answered Jan 15 at 10:35
I-P-XI-P-X
1389
1389
One benefit of immutable infrastructure is you know that you don't have any "pet" servers that are fragile and must be maintained. That gives you confidence that you can create more servers in prod / DR / testing without issue.
– Tim
Jan 15 at 18:16
add a comment |
One benefit of immutable infrastructure is you know that you don't have any "pet" servers that are fragile and must be maintained. That gives you confidence that you can create more servers in prod / DR / testing without issue.
– Tim
Jan 15 at 18:16
One benefit of immutable infrastructure is you know that you don't have any "pet" servers that are fragile and must be maintained. That gives you confidence that you can create more servers in prod / DR / testing without issue.
– Tim
Jan 15 at 18:16
One benefit of immutable infrastructure is you know that you don't have any "pet" servers that are fragile and must be maintained. That gives you confidence that you can create more servers in prod / DR / testing without issue.
– Tim
Jan 15 at 18:16
add a comment |
Thanks for contributing an answer to Server Fault!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f949082%2fhow-do-i-update-the-nginx-configuration-file-on-many-identical-servers-at-the-sa%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
3
ansible, saltstack to name a few.
– poige
Jan 15 at 3:12