ansible 操作aws target group

2020/05/14 | Ansible 入门 | Zhiming Zhang | 暂无评论 | 2228 views

最近发现alb越来越多，平时如果需要重启某台机器，最安全的方式还是先把这台机器从target group中移除，这样确保流量不会发送到我们的目标主机，然后重启结束以后再放回去

# Register an IP address target to a target group
- elb_target:
    target_group_name: myiptargetgroup
    target_id: i-1234567
    state: present

# Register an instance target to a target group
- elb_target:
    target_group_name: mytargetgroup
    target_id: i-1234567
    state: present

# Deregister a target from a target group
- elb_target:
    target_group_name: mytargetgroup
    target_id: i-1234567
    state: absent

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

# Register an IP address target to a target group

- elb_target:

target_group_name: myiptargetgroup

target_id: i-1234567

state: present

# Register an instance target to a target group

- elb_target:

target_group_name: mytargetgroup

target_id: i-1234567

state: present

# Deregister a target from a target group

- elb_target:

target_group_name: mytargetgroup

target_id: i-1234567

state: absent

然后我们可以用elb_target_info 模块来获取当前主机所在的target group

通过crontab来执行ansible-playbook 自动加载ssh-key的问题

2019/12/09 | Ansible 入门 | Zhiming Zhang | 暂无评论 | 3683 views

有时候我们的ansible-playbook我们希望定时执行以确保线上环境的状态，例如，每天定时执行一次，保证nginx的配置文件是最新的这个时候，我们就要面临一个问题，如何让ansible-playbook使用指定的key来执行,例如

*/1 * * * * /home/ansible/ansible-playbook test.yml

1	/1 * * * /home/ansible/ansible-playbook test.yml

ansible是无法自动加载.s……

ansible set_fact loop 仅保留最后一个值的问题

2019/12/03 | Ansible 入门,ansible实战 | Zhiming Zhang | 暂无评论 | 2919 views

ansible 中set_fact 支持循环，with_items，但是变量并不是append 例如：第一个set_fact部分用的是with_items，但是，我们打印的结果中只有最后一次循环中的赋值

---
#source your credential first： export AWS_PROFILE=poc
#confirm the origin host have the iam role setting , security group setting
#copy the userdata into the j2 file and make necessary change
#ansible-playbook create_new_instance_from_old_one.yml -e "origin_host_id=i-095ea1e9b5ea236b0" -e "region=us-east-1" -e "new_host_name=jeremy-test-playbook-instance11"
- name: test set fact with
  hosts: localhost
  vars:
    security_group_new_append: []
    security_group_dict:
      - group_id: "groupid_abc_1"
        group_name: "Name_1"
      - group_id: "groupid_abc_2"
        group_name: "Name_2"
      - group_id: "groupid_abc_3"
        group_name: "Name_3"

  tasks:

  - name: this is a test
    debug:
      msg: "this is the test message from localhost"

  - name: set fact
    set_fact:
      security_group_new: "{{ item.group_name }}"
    with_items: "{{ security_group_dict  }}"

  - name : show me the security_group_new
    debug:
      var: security_group_new

  - name: set fact
    set_fact:
      security_group_new_append: "{{ security_group_new_append + [item.group_name] }}"
    with_items: "{{ security_group_dict  }}"

  - name : show me the security_group_new
    debug:
      var: security_group_new_append

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

---

#source your credential first： export AWS_PROFILE=poc

#confirm the origin host have the iam role setting , security group setting

#copy the userdata into the j2 file and make necessary change

#ansible-playbook create_new_instance_from_old_one.yml -e "origin_host_id=i-095ea1e9b5ea236b0" -e "region=us-east-1" -e "new_host_name=jeremy-test-playbook-instance11"

- name: test set fact with

hosts: localhost

vars:

security_group_new_append: []

security_group_dict:

- group_id: "groupid_abc_1"

group_name: "Name_1"

- group_id: "groupid_abc_2"

group_name: "Name_2"

- group_id: "groupid_abc_3"

group_name: "Name_3"

tasks:

- name: this is a test

debug:

msg: "this is the test message from localhost"

- name: set fact

set_fact:

security_group_new: "{{ item.group_name }}"

with_items: "{{ security_group_dict }}"

- name : show me the security_group_new

debug:

var: security_group_new

- name: set fact

set_fact:

security_group_new_append: "{{ security_group_new_append + [item.group_name] }}"

with_items: "{{ security_group_dict }}"

- name : show me the security_group_new

debug:

var: security_group_new_append

但是如果我们使用第二个task ，就可以在输出结果中打印……

ansible filter (编写你自己的ansible filter)

2019/12/02 | Ansible 入门,ansible实战 | Zhiming Zhang | 暂无评论 | 5748 views

有时候我们写自己的playbook的时候变量处理真的是特别让人头大，有些变量的操作在python中就很简单，但是放到ansible playbook中就会很麻烦，所以，我们今天来看一下如何编写自己的ansible filter来帮助我们处理一下变量直接看例子吧：

#!/usr/bin/python
class FilterModule(object):
    def filters(self):
        return {
            'a_filter': self.a_filter,
            'another_filter': self.b_filter
        }

    def a_filter(self, a_variable):
        a_new_variable = a_variable + ' CRAZY NEW FILTER'
        return a_new_variable

1

2

3

4

5

6

7

8

9

10

11

#!/usr/bin/python

class FilterModule(object):

def filters(self):

return {

'a_filter': self.a_filter,

'another_filter': self.b_filter

}

def a_filter(self, a_variable):

a_new_variable = a_variable + ' CRAZY NEW FILTER'

return a_new_variable

我们来分……

ansible 邮件通知

2019/10/21 | Ansible 入门 | Zhiming Zhang | 暂无评论 | 2947 views

有事后，我们可能想通过邮件来接收一些通知，例如：我们每隔3个小时会自动跑一遍Playbook来确保HTTP处于运行状态，如果HTTP不处于运行状态，我们希望ansible帮我启动它，并发邮件通知我（这不是ansible的常规用法，非战斗人员请紧急撤离，一般这种监控都是分钟级别的，不可能存在HTTP挂了30分钟的情况）这个时候我们如果想……

ansible playbook 常用filter selectattr

2019/06/25 | Ansible 入门,运维 | Zhiming Zhang | 暂无评论 | 3891 views

随着ansilbe playbook 用的越来越多，我们也开始接触许多高级filter 例如selectattr 举个例子：

---
users:
  - name: john
    email: john@example.com
  - name: jane
    email: jane@example.com
  - name: fred
    email: fred@example.com
    password: 123!abc

1

2

3

4

5

6

7

8

9

---

users:

- name: john

email: john@example.com

- name: jane

email: jane@example.com

- name: fred

email: fred@example.com

password: 123!abc

如果我们执行如下的task

- set_fact:
  emails: "{{ users | selectattr('password', 'undefined') | map(attribute='email') | list }}"

1 2	- set_fact: emails: "{{ users \| selectattr('password', 'undefined') \| map(attribute='email') \| list }}"

首先，我们定义的users会被传递给selectatt……

zabbix容器监控基础篇 ansible-playbook cronjob

2019/03/22 | Ansible 入门,基本知识,运维 | Zhiming Zhang | 暂无评论 | 3496 views

我们的日常监控，除了zabbix自带的，就是我们自定义的脚本了，脚本每隔10分钟或者1个小时检查一次，并将检查的结果反馈给zabbix， zabbix再通过短信，邮件，微信，pagerduty将报警信息发送到我们SRE人员手中，其中重要一种实现方式就是使用cronjob 如何部署呢？通过playbook 看几个例子： [crayon-64……

ansible-playbook 里的判断与循环

2019/03/13 | Ansible 入门 | Zhiming Zhang | 暂无评论 | 4191 views

ansible-playbook我们经常用到template，也就是平时j2文件，我们很多时候都需要通过判断输出一些东西例如：

{% if the_name == 'abc' %}

{{ domain}}

{% endif %}

1

2

3

4

5

{% if the_name == 'abc' %}

{% endif %}

还有for循环：

{% for domain in g_abc %} {{ domain}}.{{ oso_name }}.503error.com {% endfor %}

1	{% for domain in g_abc %} {{ domain}}.{{ oso_name }}.503error.com {% endfor %}

ansible-playbook shell模块转义大括号 {{}} 单引号

2019/03/07 | Ansible 入门 | Zhiming Zhang | 1 条评论 | 8714 views

今天发现要在shell命令中使用大括号{{}} 刚开始的playbook如下：

#!/usr/bin/ansible-playbook
#############################
- hosts: localhost
  remote_user: root
  gather_facts: false

  tasks:

  - name: "{{ check_command }}"
    shell: /usr/bin/oc get secrets -n namespace secrentname --template '{{ index .data "abc.crt" }}' | base64 -d | openssl x509 -noout -text|grep After
    register: ssl_out
    - debug: var=ssl_out

1

2

3

4

5

6

7

8

9

10

11

12

#!/usr/bin/ansible-playbook

#############################

- hosts: localhost

remote_user: root

gather_facts: false

tasks:

- name: "{{ check_command }}"

shell: /usr/bin/oc get secrets -n namespace secrentname --template '{{ index .data "abc.crt" }}' | base64 -d | openssl x509 -noout -text|grep After

register: ssl_out

- debug: var=ssl_out

发现有两个问题，单引号需要转义，大括号需要转义 ansible 的shell模块中对于单引号的转义很简单”，两个连续的单引号就可以了但是对于大括号则需要：{{ ‘{{&……

ansible register 无视when 条件执行

2019/02/16 | Ansible 入门 | Zhiming Zhang | 暂无评论 | 7843 views

先来看一段ansible代码：

- name: test
  hosts: localhost
  gather_facts: no
  vars:
    test_name: 'real_name'
    flag: false
  tasks:
    - name: retrieve node's hostname
      shell: "hostname"
      register: test_name
      when: flag | bool

    - debug:
        var: test_name

1

2

3

4

5

6

7

8

9

10

11

12

13

14

- name: test

hosts: localhost

gather_facts: no

vars:

test_name: 'real_name'

flag: false

tasks:

- name: retrieve node's hostname

shell: "hostname"

register: test_name

when: flag | bool

- debug:

var: test_name

正常来说，我们认为会输出结果会是’real_name’，因为第一个任务因为when的条件判断并没有执行但是，结果是什么呢？

ansible-playbook 1.yaml
 [WARNING]: provided hosts list is empty, only localhost is available. Note that the implicit localhost does not match 'all'


PLAY [test] *************************************************************************************************************************************************************************

TASK [retrieve node's hostname] *****************************************************************************************************************************************************
skipping: [localhost]

TASK [debug] ************************************************************************************************************************************************************************
ok: [localhost] => {
    "test_name": {
        "changed": false,
        "skip_reason": "Conditional result was False",
        "skipped": true
    }
}

PLAY RECAP **************************************************************************************************************************************************************************
localhost                  : ok=1    changed=0    unreachable=0    failed=0

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

ansible-playbook 1.yaml

[WARNING]: provided hosts list is empty, only localhost is available. Note that the implicit localhost does not match 'all'

PLAY [test] *************************************************************************************************************************************************************************

TASK [retrieve node's hostname] *****************************************************************************************************************************************************

skipping: [localhost]

TASK [debug] ************************************************************************************************************************************************************************

ok: [localhost] => {

"test_name": {

"changed": false,

"skip_reason": "Conditional result was False",

"skipped": true

}

PLAY RECAP **************************************************************************************************************************************************************************

localhost : ok=1 changed=0 unreachable=0 failed=0

并没有，难道是skip了？……

熟悉Ansible,Docker,Zabbix,Python,Shell,Iptables的这么一个devops

分类目录：Ansible 入门

ansible 操作aws target group

通过crontab来执行ansible-playbook 自动加载ssh-key的问题

ansible set_fact loop 仅保留最后一个值的问题

ansible filter (编写你自己的ansible filter)

ansible 邮件通知

ansible playbook 常用filter selectattr

zabbix容器监控基础篇 ansible-playbook cronjob

ansible-playbook 里的判断与循环

ansible-playbook shell模块转义大括号 {{}} 单引号

ansible register 无视when 条件执行