Subject: [ansible-project] High CPU when running playbook to disable virtual servers


Its hard to tell without knowing the resources of the ansible controller, number of changes/hosts and forks but, networking tasks are more CPU related due to running on localhost and sending api calls.

Jonathan Lozada De La Matta on mobile

________________________________
From: [EMAIL PROTECTED] on behalf of Sharon Day <[EMAIL PROTECTED]>
Sent: Sunday, June 16, 2019 8:38 AM
To: Ansible Project
Subject: [ansible-project] High CPU when running playbook to disable virtual servers

I recently run an Ansible playbook to disable several virtual servers on the LTM F5.  I noticed that when I was running the playbook CPU on the F5 was up to about 97% while the playbook was running and it made the GUI interface almost unusable.  Any suggestions on how to make this run more efficiently?  Also, if I have a list of 25 VIPs is the Ansible host logging into the F5 25 times to make the change or is it logging in once and then running through all the virtual servers.

---
- name: Disable VIPs
  hosts:
    - xx.xx.xx.xx
  connection: local
  gather_facts: False

  vars_files:
   - /automation/ansible/playbooks/f5/virtuals.yml

  tasks:

    - name: Obtain Creds
      include_vars: /etc/ansible/group_vars/password.yml
      no_log: true
    - name: Disable VIP
      bigip_command:
       commands:
        - tmsh modify ltm virtual "{{ item.vip_name }}" disabled
       provider: "{{ cli }}"
      delegate_to: localhost
      with_items:
        - "{{ virtual1 }}"
      notify: Show VIP
  handlers:
    - name: Show VIP
      bigip_command:
       commands:
        - tmsh show ltm virtual | grep -E -A 4 "Server"
       provider: "{{ cli }}"
      delegate_to: localhost
      register: result

    - debug: msg="{{ result.stdout_lines }}"

    - name: Sync configuration from device to group
      bigip_configsync_action:
        device_group: "{{ device_group }}"
        sync_device_to_group: "{{ save_config }}"
        provider: "{{ cli }}"
--
To post to this group, send email to [EMAIL PROTECTED]<mailto:[EMAIL PROTECTED]>.

--
To post to this group, send email to [EMAIL PROTECTED].