tripleo-quickstart-extras/roles/validate-ipmi
Wes Hayutin 19933e5f03 Ensure that each role in extras has a dependency on extras-common
As more ansible variables are shared or reused across roles it is
important to define these variables in a role that is always
executed.  In this case that role is extras-common.

Note: This review is a blocker for https://review.openstack.org/#/c/418998/

Change-Id: I31fd13d7bcb98d73e7f16048c57c027d95faeec5
2017-01-18 09:32:16 -05:00
..
defaults Cleanup and move files for validate-ipmi 2016-11-21 11:50:27 +01:00
meta Ensure that each role in extras has a dependency on extras-common 2017-01-18 09:32:16 -05:00
tasks Cleanup and move files for validate-ipmi 2016-11-21 11:50:27 +01:00
templates Cleanup and move files for validate-ipmi 2016-11-21 11:50:27 +01:00
tests Cleanup and move files for validate-ipmi 2016-11-21 11:50:27 +01:00
README.md Cleanup and move files for validate-ipmi 2016-11-21 11:50:27 +01:00

Role Name

An Ansible role to validate the instackenv.json and IPMI overcloud connections.

Requirements

This role should be executed before deploying an overcloud on baremetal nodes to ensure that introspection and PXE boot will be able to access the nodes required for deployment.

Role Variables

Note: Make sure to include all environment file and options from your initial Overcloud creation.

  • validate_ipmi_step: -- boolean value that will validate IPMI if true
  • working_dir: <'/home/stack'> -- working directory for the role.

Dependencies

Example Playbook

  1. Sample playbook to call the role
- name: Validate IPMI connection to overcloud nodes
  hosts: undercloud
  roles:
    - ansible-role-triple-validate-ipmi

License

Apache

Author Information

RDO-CI Team