主页 / 问题 / 764717
Accepted
Hellseher
Asked:2020-12-29 09:12:14 +0000 UTC2020-12-29 09:12:14 +0000 UTC

单个主机的剧本执行时间测量

  • 772

晚上好。

有这样的蚀刻问题，目前还没有达到足够的决定。

在 Telegram 中编译报告消息需要如何计算每个主机播放剧本所花费的时间。

到目前为止，如果 playbook 为多个主机并行执行，这样的存根并不总是显示正确的时间：

pl-signoff.yml

#!/usr/bin/ansible-playbook
- hosts: _signoff
  gather_facts: false

  vars:
    - playbook_name: "pl-signoff"
    - build_version: 1.41 

  pre_tasks:
    - local_action: shell date
      register: pl_begin
      become: false

  roles:
    - role-1
    - role-2
    # etc
    - inspector

角色/检查员/任务/main.yml

- name: "last probe of facts"
  setup:

- local_action: shell date
  register: pl_end
  become: false

- name: "shout it loud to signoff_test"
  telegram:
    msg_format: plain
    token: 'my_tocken'
    chat_id: my_id
    msg: |
         BEGIN: "{{ pl_begin }}"
         PL: "{{ playbook_name }}"
         MSG: task complete for the site "{{ site-id }}"
         END: "{{ pl_end }}"
ansible

1 个回答

  1. Best Answer

    一切都变得简单多了，我只是在本地机器上运行了初步任务并收集了有关时间的事实：

    - hosts: _signoff
  gather_facts: false


  pre_tasks:
    - name: "setup localhost"
      local_action: setup gather_subset=min
      become: false
    - name: "set meta facts"
      set_fact:
        pl_name: "pl-signoff"
        pl_version: 1.41
        pl_build: "{{ ansible_date_time.epoch }}"
        pl_begin: "{{ ansible_date_time.iso8601_micro }}"

    - debug:
        msg:
        - "{{ pl_name }}"
        - "{{ pl_version }}"
        - "{{ pl_build }}"
        - "{{ pl_begin }}"

    我们为每个主机获得了非常准确的剧本开始时间：

    Tuesday 02 January 2018  23:53:04 +0000 (0:00:00.053)       0:00:00.773 ******* 
ok: [TEST-SiteUbuntu-16-04] => {
    "msg": [
        "pl-signoff", 
        1.41, 
        "1514937183", 
        "2018-01-02T23:53:03.820574Z"
    ]
}
ok: [TEST-SiteUbuntu-12-04] => {
    "msg": [
        "pl-signoff", 
        1.41, 
        "1514937183", 
        "2018-01-02T23:53:03.817155Z"
    ]
}

    链接

    • 1

相关问题