尝试使用ansible在不同的服务器上运行带有不同参数的脚本,例如:
server 192.168.0.1 -> fabric.sh generic1 status
server 192.168.0.2 -> fabric.sh generic2dr status
server 192.168.0.3 -> fabric.sh generic3 status
如何在下面的剧本中使用变量?
当我为每个服务器创建组时,它可以工作,但是效率不高
---
- hosts: esb
remote_user: root
tasks:
- name: Generic_1
become_user: esb
shell: "/home/fabric.sh generic1 status"
主机文件:
[esb]
192.168.0.1
192.168.0.2
192.168.0.3
答案 0 :(得分:1)
您可以在清单中设置每个主机的变量。例如,修改库存,使其看起来像这样:
[esb]
192.168.0.1 fabric_args="generic1 status"
192.168.0.2 fabric_args="generic2dr status"
192.168.0.3 fabric_args="generic3 status"
然后在您的剧本中使用fabric_args
变量:
---
- hosts: esb
remote_user: root
tasks:
- name: Generic_1
become_user: esb
shell: "/home/fabric.sh {{ fabric_args }}"
有关更多信息,请阅读Ansible文档的Using Variables和Working with Inventory部分。
答案 1 :(得分:0)
在Basic inventory旁边有yaml – Uses a specific YAML file as an inventory source。
例如(使变量适合您的需求):
$ cat hosts
all:
hosts:
10.1.0.51:
10.1.0.52:
10.1.0.53:
vars:
ansible_connection: ssh
ansible_user: admin
ansible_become: yes
ansible_become_user: root
ansible_become_method: sudo
ansible_python_interpreter: /usr/local/bin/python3.6
ansible_perl_interpreter: /usr/local/bin/perl
children:
esb:
hosts:
10.1.0.51:
run_string: "fabric.sh generic1 status"
10.1.0.52:
run_string: "fabric.sh generic2dr status"
10.1.0.53:
run_string: "fabric.sh generic3 status"
下面的戏
- hosts: esb
tasks:
- debug:
var: run_string
给予(节略):
ok: [10.1.0.51] => {
"run_string": "generic1 status"
}
ok: [10.1.0.52] => {
"run_string": "generic2dr status"
}
ok: [10.1.0.53] => {
"run_string": "generic3 status"
}