Related questions

Ansible: YAML inventory for staging / production hosts

2020-11-24 18:21 prosto.vint imported from Stackoverflow

I cant setup inventory which will be easy and useful in yml` format for Ansible Playbook :(

For example:

all:
  children:
    db:
      children:
        production:
          hosts:
            1.1.1.1:

        staging:
          hosts:
            11.11.11.11:

    web:
      children:
        production:
          hosts:
            2.2.2.2:

        staging:
          hosts:
            22.22.22.22:

So, I have two playbooks with:

playbook-db.yml

...
hosts:
  - db

and playbook-web.yml

...
hosts:
  - db

And I want to use this inventory like:

andible-playbook -D playbook-db.yml --limit=staging

I am expecting that my playbook will be used only db and staging hosts, but playbook is applying for all staging hosts: 11.11.11.11 and 22.22.22.22 (but I am expecting 11.11.11.11 only) :(

How I can realize it correctly?

1 answer

  • answered 2020-11-24 19:23 mdaniel

    It seems you have a misunderstanding about the inventory file, since ansible is doing as you described

    ansible-inventory -i your-posted-file.yml --list

    emits

    {   ...
    "all": {
        "children": [
            "db",
            "ungrouped",
            "web"
        ]
    },
    "db": {
        "children": [
            "production",
            "staging"
        ]
    },
    "production": {
        "hosts": [
            "1.1.1.1",
            "2.2.2.2"
        ]
    },
    "staging": {
        "hosts": [
            "11.11.11.11",
            "22.22.22.22"
        ]
    }

    showing that the db group has all members of production and staging, but staging has hosts "11.11.11.11", "22.22.22.22" just as you described

    I think perhaps you were conflating the yaml indentation with membership, but that's not how ansible inventories work.

    What is far more likely is that you'd want a db-staging and db-production group, for the case you described where you want only db hosts that are staging, leaving the db group to mean every db member

See also questions close to this topic

  • How to use proper loop in Ansible uri module

    I'm using the Ansible uri module to trigger the pfSense API. Now I want to create firewall rules in a task (code is truncated).

    ---
# tasks file for creating firewall rules

- name: "Create firewall rules"
  uri:
    url: "https://{{ pf_hostname }}/api/v1/firewall/rule"
    method: "POST"
    body: "{ \
          \"client-id\": \"{{ pf_user }}\", 
            \"client-token\": \"{{ pf_password }}\",
            \"type\": \"{{ pf_fw_type_01 }}\",
            \"interface\": \"{{ pf_fw_interface_01 }}\",
          }"

    The vars file looks like this.

    ---
# vars file for creating firewall rules

# Authentication
pf_hostname: "pfsense.local"
pf_user: "admin"
pf_password: "pfsense"

# Rule 01
pf_fw_type_01: "pass"
pf_fw_interface_01: "wan"

    How can I now repeat the task without unnecessary redundancy (e.g. with loop) for other rules? I only come up with the following idea, but it doesn't seem ideal to me.

      loop: 
    - "{{ item.client-id: {{ pf_user }}, item.type: {{ pf_fw_type_01 }} }}"
    - "{{ item.client-id: {{ pf_user }}, item.type: {{ pf_fw_type_02 }} }}"
  • Running Ansible playbook from Gitlab-CI pipe line

    I am trying to run Ansible playbook from my gitlab-pipeline. But I am getting an error "Invalid/incorrect password: Permission denied, please try again."

    Here is my GitLab-ci pipeline

    before_script:
  - ssh-keyscan <serverip>
  - echo "$SSH_KNOWN_HOSTS" >> ~/.ssh/known_hosts
  - chmod 644 ~/.ssh/known_hosts

job1:
    tags:
        - xyz
    script:
        - echo $CI_PROJECT_DIR
        - cd $CI_PROJECT_DIR/scripts
        - ./bashscript.sh
        - echo "Completed"

    bashscript.sh contains ansible command "ansible-playbook test.yml" and test.yml

    - hosts: all
  gather_facts: yes
  name: checking host
  tasks:
  - name: "Check if the machine is connecting to host"
    shell: echo "Hi"
  • AWS application load balancer DNS name as a variable in Ansible AWX tower playbook

    I need to fetch AWS application load balancer dns name and pass it as a variable in AWX tower Ansible playbook. Is this doable? I couldn't find any useful example online.

    Any help would be much appreciated!