使用Ansible自动部署MGR中生成group_replication_group_seeds值的方法

原創 Fan_-_ 2020-06-23 10:03

使用Ansible自动部署MGR中生成group_replication_group_seeds值的方法

生成group_replication_group_seeds值的方法

网卡不统一

之前我是通过groups['mfw_test'] | map('extract', hostvars, ['ansible_all_ipv4_addresses'])这种形式, 去一个inventory group下每一个host的ansible_all_ipv4_addresses

ansible_all_ipv4_address是所有网卡上的ip, 包括手动添加的ip(例如vip)

    "msg": {
        "centos-1": {
            "ansible_all_ipv4_addresses": [
                "192.168.124.136", 
                "172.16.120.10"
            ],

我们可以通过下面的playbook查看hostvars

    - debug:
        msg: "{{ hostvars }}"

上面的情况是没有vip, 也就是

[root@centos-1 ~]# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN qlen 1
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: ens33: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
    link/ether 00:0c:29:b2:18:33 brd ff:ff:ff:ff:ff:ff
    inet 172.16.120.10/24 brd 172.16.120.255 scope global ens33
       valid_lft forever preferred_lft forever
    inet6 fe80::e880:2501:cdab:b11d/64 scope link tentative dadfailed 
       valid_lft forever preferred_lft forever
    inet6 fe80::ada9:2128:e605:334a/64 scope link tentative dadfailed 
       valid_lft forever preferred_lft forever
    inet6 fe80::2f9b:31f4:73e6:e438/64 scope link tentative dadfailed 
       valid_lft forever preferred_lft forever
3: ens37: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
    link/ether 00:50:56:2c:1a:a8 brd ff:ff:ff:ff:ff:ff
    inet 192.168.124.166/24 brd 192.168.124.255 scope global dynamic ens37
       valid_lft 1452sec preferred_lft 1452sec
    inet6 fe80::5c28:fb1e:459:1b9/64 scope link 
       valid_lft forever preferred_lft forever

如果有vip则是

    "msg": {
        "centos-1": {
            "ansible_all_ipv4_addresses": [
                "192.168.124.136", 
                "172.16.120.10",
                "172.16.120.100"
            ],

之前我为了解决现实服务器网卡名称不统一的问题(现实有叫em2的有叫p6p1的还有team0, eth0等等, 而cmdb中又没有这些信息), 采用了ansible_all_ipv4_addresses的方法, 取所有ip, 然后根据规则自己过滤(比如过滤掉vip等等). 时间长了就成了这么一坨

{%- for ip_list in (groups[group] | map('extract', hostvars, ['ansible_all_ipv4_addresses'])) -%}
    {%- if loop.last -%}
        {%- for ip in ip_list -%}
            {%- if (ip.startswith('192.168') or ip.startswith('10.163') or ip.startswith('10.152') or ip.startswith('10.132') or ip.startswith('10.133')) and not ip.startswith('192.168.3') and not ip.startswith('192.168.8') and not ip.startswith('192.168.16') and not ip.startswith('10.62') and not ip.startswith('10.32') and not ip.startswith('10.52') and not ip.startswith('10.33') and not (ip.startswith('10.133.1.2') and ip.split('.')[3]|int>=200) -%}
                {{ ip }}:2{{ mysql_port }}
            {%- endif -%}
        {%- endfor %}
    {%- else -%}
        {%- for ip in ip_list -%}
            {%- if (ip.startswith('192.168') or ip.startswith('10.163') or ip.startswith('10.152') or ip.startswith('10.132') or ip.startswith('10.133')) and not ip.startswith('192.168.3') and not ip.startswith('192.168.8') and not ip.startswith('192.168.16') and not ip.startswith('10.62') and not ip.startswith('10.32') and not ip.startswith('10.52') and not ip.startswith('10.33') and not (ip.startswith('10.133.1.2') and ip.split('.')[3]|int>=200) -%}
                {{ ip }}:2{{ mysql_port }},
            {%- endif -%}
        {%- endfor -%}
    {%- endif -%}
{%- endfor -%}

写到vars/main.yaml里

group_replication_group_seeds: "{%- for ip_list in (groups[group] | map('extract', hostvars, ['ansible_all_ipv4_addresses'])) -%}{%- if loop.last -%}{%- for ip in ip_list -%}{%- if (ip.startswith('192.168') or ip.startswith('10.163') or ip.startswith('10.152') or ip.startswith('10.132') or ip.startswith('10.133')) and not ip.startswith('192.168.3') and not ip.startswith('192.168.8') and not ip.startswith('192.168.16') and not ip.startswith('10.62') and not ip.startswith('10.32') and not ip.startswith('10.52') and not ip.startswith('10.33') and not (ip.startswith('10.133.1.2') and ip.split('.')[3]|int>=200) -%}{{ ip }}:2{{ mysql_port }}{%- endif -%}{%- endfor %}{%- else -%}{%- for ip in ip_list -%}{%- if (ip.startswith('192.168') or ip.startswith('10.163') or ip.startswith('10.152') or ip.startswith('10.132') or ip.startswith('10.133')) and not ip.startswith('192.168.3') and not ip.startswith('192.168.8') and not ip.startswith('192.168.16') and not ip.startswith('10.62') and not ip.startswith('10.32') and not ip.startswith('10.52') and not ip.startswith('10.33') and not (ip.startswith('10.133.1.2') and ip.split('.')[3]|int>=200) -%}{{ ip }}:2{{ mysql_port }},{%- endif -%}{%- endfor -%}{%- endif -%}{%- endfor -%}"

网卡统一

如果网卡是统一的, 或者我们能知道要部署服务器的网卡叫什么.

一个部署任务的机器网卡名称要一致, 否则下面的方法也用不了

观察hostvars可以发现

ansible_ens33无vip

    "msg": {
        "centos-1": {
            "ansible_all_ipv4_addresses": [
                "192.168.124.136", 
                "172.16.120.10"
            ], 
            ...省略
            "ansible_ens33": {
                "active": true, 
                "device": "ens33", 
                ...省略
                "hw_timestamp_filters": [], 
                "ipv4": {
                    "address": "172.16.120.10", 
                    "broadcast": "172.16.120.255", 
                    "netmask": "255.255.255.0", 
                    "network": "172.16.120.0"
                }, 
                "ipv6": [
                    {
                        "address": "fe80::e880:2501:cdab:b11d", 
                        "prefix": "64", 
                        "scope": "link"
                    }
                ],

ansible_ens33有vip

    "msg": {
        "centos-1": {
            "ansible_all_ipv4_addresses": [
                "192.168.124.136", 
                "172.16.120.10",
                "172.16.120.100"
            ], 
            ...省略
            "ansible_ens33": {
                "active": true, 
                "device": "ens33", 
                ...省略
                "hw_timestamp_filters": [], 
                "ipv4": {
                    "address": "172.16.120.10", 
                    "broadcast": "172.16.120.255", 
                    "netmask": "255.255.255.0", 
                    "network": "172.16.120.0"
                }, 
                "ipv4_secondaries": [ --不知道为什么有俩
                    {
                        "address": "172.16.120.100", 
                        "broadcast": "global", 
                        "netmask": "255.255.255.0", 
                        "network": "172.16.120.0"
                    }, 
                    {
                        "address": "172.16.120.100", 
                        "broadcast": "global", 
                        "netmask": "255.255.255.0", 
                        "network": "172.16.120.0"
                    }
                ], 
                "ipv6": [
                    {
                        "address": "fe80::e880:2501:cdab:b11d", 
                        "prefix": "64", 
                        "scope": "link"
                    }
                ],

可以这样取map('extract', hostvars, ['ansible_ens33', 'ipv4', 'address'])

于是

[root@centos-4 ansible]# cat hosts
[mysql]
172.16.120.10 mysql_repl_role=master
172.16.120.11 mysql_repl_role=slave
172.16.120.12 mysql_repl_role=slave

[mha]
172.16.120.13

[proxysql]
172.16.120.10 weight=100 comment=PRIMARY
172.16.120.11 weight=99 comment=SECONDARY
172.16.120.12 weight=99 comment=SECONDARY


[all:vars]
ansible_user=root
#ansible_password=vagrant
ansible_port=22
ansible_become=true

playbook

---
- name: '测试'
  hosts: mysql
  tasks:
    - name: " groups['mysql']|map('extract', hostvars, ['ansible_ens33', 'ipv4', 'address'])|list"
      debug:
        msg: "{{ groups['mysql']|map('extract', hostvars, ['ansible_ens33', 'ipv4', 'address'])|list}}"

其中172.16.120.10还是有vip 172.16.120.100的

结果

TASK [groups['mysql']|map('extract', hostvars, ['ansible_ens33', 'ipv4', 'address'])|list] *********************************************************************************************************************************************************************
ok: [172.16.120.11] => {
    "msg": [
        "172.16.120.10", 
        "172.16.120.11", 
        "172.16.120.12"
    ]
}
ok: [172.16.120.10] => {
    "msg": [
        "172.16.120.10", 
        "172.16.120.11", 
        "172.16.120.12"
    ]
}
ok: [172.16.120.12] => {
    "msg": [
        "172.16.120.10", 
        "172.16.120.11", 
        "172.16.120.12"
    ]
}

到这一步这是取到了所有ip, 还没完成拼接出group_replication_group_seeds

接下来要用到zip_longest

拿官方文档的例子

- name: '测试'
  hosts: 172.16.120.10
  tasks:
    - name: give me list combo of two lists
      debug:
       msg: "{{ [1,2,3,4,5] | zip(['a','b','c','d','e','f']) | list }}"
    
    - name: give me shortest combo of two lists
      debug:
        msg: "{{ [1,2,3] | zip(['a','b','c','d','e','f'], ['!','@','#','$']) | list }}"
    
    - name: give me longest combo of three lists , fill with X
      debug:
        msg: "{{ [1,2,3] | zip_longest(['a','b','c','d','e','f'], [21, 22, 23], fillvalue='X') | list }}"

结果

TASK [give me list combo of two lists] *************************************************************************************************************************************************************************************************************************
ok: [172.16.120.10] => {
    "msg": [
        [
            1, 
            "a"
        ], 
        [
            2, 
            "b"
        ], 
        [
            3, 
            "c"
        ], 
        [
            4, 
            "d"
        ], 
        [
            5, 
            "e"
        ]
    ]
}

TASK [give me shortest combo of two lists] *********************************************************************************************************************************************************************************************************************
ok: [172.16.120.10] => {
    "msg": [
        [
            1, 
            "a", 
            "!"
        ], 
        [
            2, 
            "b", 
            "@"
        ], 
        [
            3, 
            "c", 
            "#"
        ]
    ]
}

TASK [give me longest combo of three lists , fill with X] ******************************************************************************************************************************************************************************************************
ok: [172.16.120.10] => {
    "msg": [
        [
            1, 
            "a", 
            21
        ], 
        [
            2, 
            "b", 
            22
        ], 
        [
            3, 
            "c", 
            23
        ], 
        [
            "X", 
            "d", 
            "X"
        ], 
        [
            "X", 
            "e", 
            "X"
        ], 
        [
            "X", 
            "f", 
            "X"
        ]
    ]
}

可以看到在这前两个task中, “多余"的会被舍弃掉, 而且可以zip多个list, 最后一个task使用fillvalue取"补齐”

于是我们就可以

    - name: " groups['mysql']|map('extract', hostvars, ['ansible_ens33', 'ipv4', 'address'])| list | zip_longest([], fillvalue=':2'+mysql_port|string) |list"
      debug:
        msg: "{{ groups['mysql']|map('extract', hostvars, ['ansible_ens33', 'ipv4', 'address']) | list | zip_longest([], fillvalue=':2'+mysql_port|string) |list}}"

这里为了看到结果所以list一下,否则是一个<itertools.izip_longest object at 0x24468e8>

TASK [groups['mysql']|map('extract', hostvars, ['ansible_ens33', 'ipv4', 'address'])| list | zip_longest([], fillvalue=':2'+mysql_port|string) |list] **********************************************************************************************************
ok: [172.16.120.10] => {
    "msg": [
        [
            "172.16.120.10", 
            ":23306"
        ], 
        [
            "172.16.120.11", 
            ":23306"
        ], 
        [
            "172.16.120.12", 
            ":23306"
        ]
    ]
}
ok: [172.16.120.11] => {
    "msg": [
        [
            "172.16.120.10", 
            ":23306"
        ], 
        [
            "172.16.120.11", 
            ":23306"
        ], 
        [
            "172.16.120.12", 
            ":23306"
        ]
    ]
}
ok: [172.16.120.12] => {
    "msg": [
        [
            "172.16.120.10", 
            ":23306"
        ], 
        [
            "172.16.120.11", 
            ":23306"
        ], 
        [
            "172.16.120.12", 
            ":23306"
        ]
    ]
}

然后使用map(‘join’),就是将列表里的每一个元素使用join拼接

    - name: " groups['mysql']|map('extract', hostvars, ['ansible_ens33', 'ipv4', 'address'])| list | zip_longest([], fillvalue=':2'+mysql_port|string) | map('join')|list "
      debug:
        msg: "{{ groups['mysql']|map('extract', hostvars, ['ansible_ens33', 'ipv4', 'address']) | list | zip_longest([], fillvalue=':2'+mysql_port|string) | map('join') |list}}"

TASK [groups['mysql']|map('extract', hostvars, ['ansible_ens33', 'ipv4', 'address'])| list | zip_longest([], fillvalue=':2'+mysql_port|string) | map('join')|list] *********************************************************************************************
ok: [172.16.120.11] => {
    "msg": [
        "172.16.120.10:23306", 
        "172.16.120.11:23306", 
        "172.16.120.12:23306"
    ]
}
ok: [172.16.120.10] => {
    "msg": [
        "172.16.120.10:23306", 
        "172.16.120.11:23306", 
        "172.16.120.12:23306"
    ]
}
ok: [172.16.120.12] => {
    "msg": [
        "172.16.120.10:23306", 
        "172.16.120.11:23306", 
        "172.16.120.12:23306"
    ]
}

最后

---
- name: '测试'
  hosts: mysql
  vars:
    mysql_port: 3306
  tasks:
    - name: " groups['mysql']|map('extract', hostvars, ['ansible_ens33', 'ipv4', 'address'])| list | zip_longest([], fillvalue=':2'+mysql_port|string) | map('join') | join(',')"
      debug:
        msg: "{{ groups['mysql']|map('extract', hostvars, ['ansible_ens33', 'ipv4', 'address']) | list | zip_longest([], fillvalue=':2'+mysql_port|string) | map('join') | join(',')}}"

TASK [groups['mysql']|map('extract', hostvars, ['ansible_ens33', 'ipv4', 'address'])| list | zip_longest([], fillvalue=:3306) | map('join') | join(',')] *******************************************************************************************************
ok: [172.16.120.10] => {
    "msg": "172.16.120.10:23306,172.16.120.11:23306,172.16.120.12:23306"
}
ok: [172.16.120.11] => {
    "msg": "172.16.120.10:23306,172.16.120.11:23306,172.16.120.12:23306"
}
ok: [172.16.120.12] => {
    "msg": "172.16.120.10:23306,172.16.120.11:23306,172.16.120.12:23306"
}

附1: 生产group_replication_local_address的方法

使用hostvars[inventory_hostname]

    - name: "hostvars[inventory_hostname]['ansible_ens33']['ipv4']['address']:23306"
      debug:
        msg: "{{ hostvars[inventory_hostname]['ansible_ens33']['ipv4']['address'] }}:2{{ mysql_port }}"

TASK [hostvars[inventory_hostname]['ansible_ens33']['ipv4']['address']:23306] **********************************************************************************************************************************************************************************
ok: [172.16.120.10] => {
    "msg": "172.16.120.10:23306"
}
ok: [172.16.120.11] => {
    "msg": "172.16.120.11:23306"
}
ok: [172.16.120.12] => {
    "msg": "172.16.120.12:23306"
}

同样, 如果网卡不统一, 只能…

       {% for ip in ansible_all_ipv4_addresses -%}
         {% if (ip.startswith('192.168') or ip.startswith('10.163') or ip.startswith('10.152') or ip.startswith('10.132') or ip.startswith('10.133')) and not ip.startswith('192.168.3') and not ip.startswith('192.168.8') and not ip.startswith('192.168.16') and not ip.startswith('10.62') and not ip.startswith('10.32') and not ip.startswith('10.52') and not ip.startswith('10.33') and not (ip.startswith('10.133.1.2') and ip.split('.')[3]|int>=200) -%}
           loose-group_replication_local_address = {{ ip }}:2{{ mysql_port }}
         {% endif %}
       {% endfor %}

附2: /etc/hosts

网卡不统一

 - name: 设置/etc/hosts
   blockinfile:
     path: /etc/hosts
     block: |
       {{ item }}
   with_items: "{{ etc_hosts }}"

 etc_hosts: |
   {% for ip_list in (groups[group] | map('extract', hostvars, ['ansible_all_ipv4_addresses'])) -%} {% set iploop = loop %}
   {% for ip in ip_list -%}
   {% for hostname in (groups[group] | map('extract', hostvars, ['ansible_hostname'])) -%}
   {% if loop.index == iploop.index -%}
   {% if (ip.startswith('192.168') or ip.startswith('10.163') or ip.startswith('10.152') or ip.startswith('10.132') or ip.startswith('10.133') ) and not ip.startswith('192.168.3') and not ip.startswith('192.168.8') and not ip.startswith('192.168.16') and not ip.startswith('10.62') and not ip.startswith('10.32') and not ip.startswith('10.52') and not ip.startswith('10.33') and not (ip.startswith('10.133.1.2') and ip.split('.')[3]|int>=200) -%}
   {{ ip }}  {{ hostname }}
   {% endif %}
   {% endif %}
   {% endfor %}
   {% endfor %}
   {% endfor %}

网卡统一

---
- name: '测试'
  hosts: mysql
  vars:
    etc_hosts: "{{ groups['mysql']|map('extract', hostvars, ['ansible_ens33', 'ipv4', 'address']) | list | zip(groups['mysql']|map('extract', hostvars, ['ansible_hostname'])) | map('join','  ') | join('\n') }}"
  tasks:
    - name: " groups['mysql']|map('extract', hostvars, ['ansible_ens33', 'ipv4', 'address'])| list | zip(groups['mysql']|map('extract', hostvars, ['ansible_hostname'])) | map('join','  ') | join('\n') "
      debug:
        msg: "{{ groups['mysql']|map('extract', hostvars, ['ansible_ens33', 'ipv4', 'address']) | list | zip(groups['mysql']|map('extract', hostvars, ['ansible_hostname'])) | map('join','  ') | join('\n') }}"
    - name: 设置/etc/hosts
      blockinfile:
        path: /tmp/hosts.test
        block: |
          {{ item }}
      with_items: "{{ etc_hosts }}"

TASK [groups['mysql']|map('extract', hostvars, ['ansible_ens33', 'ipv4', 'address'])| list | zip(groups['mysql']|map('extract', hostvars, ['ansible_hostname'])) | map('join','  ') | join('
')] ***************************************************************
ok: [172.16.120.10] => {
    "msg": "172.16.120.10  centos-1\n172.16.120.11  centos-2\n172.16.120.12  centos-3"
}
ok: [172.16.120.11] => {
    "msg": "172.16.120.10  centos-1\n172.16.120.11  centos-2\n172.16.120.12  centos-3"
}
ok: [172.16.120.12] => {
    "msg": "172.16.120.10  centos-1\n172.16.120.11  centos-2\n172.16.120.12  centos-3"
}


[root@centos-1 ~]# cat /tmp/hosts.test 
# BEGIN ANSIBLE MANAGED BLOCK
172.16.120.10  centos-1
172.16.120.11  centos-2
172.16.120.12  centos-3
# END ANSIBLE MANAGED BLOCK

注意hostname要用groups['mysql']|map('extract', hostvars, ['ansible_hostname'])取, 不能直接ansible_hostname

    - name: " groups['mysql']|map('extract', hostvars, ['ansible_ens33', 'ipv4', 'address'])| list | zip_longest([], fillvalue='  '+ansible_hostname) | map('join')| join('\n') "
      debug:
        msg: "{{ groups['mysql']|map('extract', hostvars, ['ansible_ens33', 'ipv4', 'address']) | list | zip_longest([], fillvalue='  '+ansible_hostname) | map('join') | join('\n')}}"

看输出的结果hostname部分, 每个主机都只取到自己的hostname


TASK [groups['mysql']|map('extract', hostvars, ['ansible_ens33', 'ipv4', 'address'])| list | zip_longest([], fillvalue='  '+ansible_hostname) | map('join')| join('
')] ****************************************************************************************
ok: [172.16.120.10] => {
    "msg": "172.16.120.10  centos-1\n172.16.120.11  centos-1\n172.16.120.12  centos-1"
}
ok: [172.16.120.11] => {
    "msg": "172.16.120.10  centos-2\n172.16.120.11  centos-2\n172.16.120.12  centos-2"
}
ok: [172.16.120.12] => {
    "msg": "172.16.120.10  centos-3\n172.16.120.11  centos-3\n172.16.120.12  centos-3"
}
發表評論
所有評論
還沒有人評論，想成為第一個評論的人麼? 請在上方評論欄輸入並且點擊發布.
相關文章

Ansible基础 day01 快速入门

Ansible 快速入門1.介紹2.工作原理3.如何安裝3.1 先決條件3.2 安裝Ansible4.管理節點與被管理節點建立SSH信任關係5.快速入門5.1 場景假設5.2 場景一5.3 場景二6.Ansible資產6.1 靜態

果子哥丶 2020-07-07 17:17:20

Ansible配置sudo提权免密登录

配置EPEL源： wget -O /etc/yum.repos.d/epel.repo http://mirrors.aliyun.com/repo/epel-7.repo yum clean all yum makecache

Dreamcatchering 2020-07-06 01:06:42

Docker实现ansible的练习

一. 使用dockerfile創建支持ssh服務的centos7鏡像 注意：本文基礎都是在docker和ansible都安裝好的情況下 創建dockerfile目錄 [root@localhost /]# mkdir mydo

托塔天王李 2020-07-06 00:37:23

Ansible剧本管理(实例演释!!!)

inventory主機清單 ansible默認的主機清單是/etc/ansible/hosts文件，主機清單可以手動設置，也可以通過Dynamic Inventory動態生成，一般主機名使用FQDN vim /etc/ansib

杨佳甘露 2020-07-04 07:28:36

Ansible Api 2.x 密钥登录方式实现

前提 （1）密碼方式可先參閱我另外一篇博文:  https://blog.csdn.net/knight_zhou/article/details/103683305 （2）也可以參閱我的 51cto訂閱專欄：  https://blog

knight-zhou 2020-07-03 04:55:12

Ansible详解

Usage: ansible <host-pattern> [options] Options: -m MODULE\_NAME, --module-name=MODULE\_NAME 要執行的模塊，默認爲 co

李庆海 2020-07-03 04:18:28

Ansible简单学习

最近做項目，機器比較多，自己還是沿用shell的for i in {1…20}這樣的蠢方法，旁邊的大佬用ansible已經爽的飛起。 故決定使用Ansible來提高自己的工作效率，達到摸魚的目的… 附上一個建議去學習的鏈接：Ans

齐泽文的Blog 2020-06-30 23:54:05

自动化运维工具——Ansible

文章目錄Ansible基本概述ansible軟件特點ansible軟件服務意義ansible基礎架構圖ansible常用模塊 Ansible基本概述 Ansible是新出現的自動化運維工具，它基於Python開發，集合了衆多運維工

玫瑰花的葬礼。 2020-06-29 03:38:35

一起学Python吧~Python3调用Ansible项目实战

別問我爲什麼Terminal的命令也要用PyCharm來寫,一切都是爲了方便麪~ #!/bin/env python3 #-*- coding:utf8 -*- #學python3的第十四天(運維開發者工具) #Ansible批量

CSDN阿坤 2020-06-28 18:12:01

一起学Python吧~Aansible批量部署与管理(自动化运维必备)

#!/bin/env python3 #-*- coding:utf8 -*- #學Python3的第十六天 #-----ansible----- """如果你鏈接遠程主機是個普通用戶,怎麼執行管理任務? #vim ansible

CSDN阿坤 2020-06-28 18:12:01

Ansible 通过playbook及shell结合部署jdk1.8

在工作中，初次部署服務器時需要初始化很多軟件，大平臺部署有時大幾十臺甚至上百臺，每臺都去做重複的工作將帶來非常大的工作量，下面我們介紹一下ansible自動化部署的相關操作，僅供交流學習。 環境準備： 操作系統 centos7     1

hu_wenjie 2020-06-27 11:15:40

Ansible常用Filter

文章目錄Ansible 常用Filter示例json文件`from_json``json query filter``list filters```random number filter```IP address filter`

十五十六 2020-06-25 10:51:48

（干货）Ansible安装（在线|离线）

Ansible安裝 在線安裝 root> yum -y install epel-release root> yum install ansible 離線安裝 Yum分析下載依賴 根據目標主機所用操作系統在實驗環境安裝一個新的操

imWhiteee 2020-06-24 14:54:01

MGR 原理

MySQL Group Replication（MGR）框架讓MySQL具備了自動主從切換和故障恢復能力，舉single primary（單主）模式爲例，primary作爲主節點對外提供讀寫服務，是唯一的可寫節點，其他節點均爲

Ty_FFTQ 2020-06-28 14:55:12

组复制（MySQL Group Replication）简介

1.簡介 本文提供mysql組複製的背景信息。 創建一個容錯系統的最常見的方法是求助於組件冗餘，換句話說，組件能被移除，但系統將如期可以繼續操作。這將整個系統的複雜度提升到了更具挑戰性的級別。尤其是，複製庫必須面對多個而非一個服務器維護和

lhdz_bj 2020-06-27 11:43:24