Testing the YAML file and running playbooks

The aposHouseConfig.py command checks for the most recent YAML file in the directory and validates it, then it asks for confirmation to run the configuration with this file.

Procedure

  1. From /opt/ibm/appliance/platform/apos-comms/customer_network_config/ansible directory, run:
    ANSIBLE_HASH_BEHAVIOUR=merge ansible-playbook -i ./System_Name.yml  playbooks/house_config.yml --check -v
    to test the YAML and playbooks.
    Note: If any changes are listed in --check --v, ensure that they are expected. If they are unexpected, you must edit the YAML file so that it contains only the expected changes. When you run the playbook in the next step, these changes will take effect.
  2. Run the following command:
    /opt/ibm/appliance/platform/apos-comms/tools/aposHouseConfig.py
    The command asks for confirmation:
    [root@gt34-node1 ~]# /opt/ibm/appliance/platform/apos-comms/tools/aposHouseConfig.py
    Validated /opt/ibm/appliance/platform/apos-comms/customer_network_config/ansible/gt34-house.yml
    Confirm you wish to proceed with this yaml: [yes]:
    Note: It is recommended that there is only one YAML file in the directory apart from the template. The playbook always uses the one with the latest timestamp.
    Draft comment: anna.bogusz@pl.ibm.com
    There is also a --limit_play option for this command to be used with network_operator_setup.html
    /opt/ibm/appliance/platform/apos-comms/tools/aposHouseConfig.py --limit_play set_openshift_addrs