ce7982192f
We need to differentiate local_working_dir from working_dir as well as decouple the stack user from `ansible_user` var. Both of these are causing issues as we begin to automate deployments in more environments. - Cleanup duplicate variables that are consumed via extras-common - Note: extras-common depends on the common role in OOOQ - Cleanup redundant var and superfluous quotes from overcloud-scale role - Cleanup redundant comments in <role>/defaults/main.yml Closes-bug: 1654574 Change-Id: I9c7a3166ed1fc5042c11e420223134ea912b45c5 |
||
---|---|---|
.. | ||
defaults | ||
meta | ||
tasks | ||
templates | ||
tests | ||
README.md |
Role Name
An Ansible role to setup the undercloud for a deployment on baremetal overcloud nodes.
Requirements
This playbook expects that the undercloud has been installed and setup using one of the roles relevant to baremetal overcloud deployments.
Role Variables
Note: Make sure to include all environment file and options from your initial Overcloud creation.
- step_root_device_size: -- boolean value that will apply disk size hints and rerun introspection if true
- working_dir: <'/home/stack'> -- working directory for the role. Assumes stackrc file is present at this location
- step_adjust_mtu: -- boolean value that will change MTUS on specified nics
- mtu: <1350> -- numerical value to set MTUs
- mtu_interface: <'eth1'> -- list of NICs
- undercloud_type: -- can be overwritten with values like 'baremetal' or 'ovb'
- network_isolation: -- bolean value to test if network isolation wil be used in the deployment
- network_isolation_ipv4_cidr: <"172.16.23.0/24">
Dependencies
This playbook does not deploy the overcloud. After this playbook runs, call https://github.com/redhat-openstack/ansible-role-tripleo-overcloud.
Example Playbook
- Sample playbook to call the role
- name: Prepare for deployment on baremetal overcloud
hosts: virthost
gather_facts: no
roles:
- ansible-role-tripleo-overcloud-prep-baremetal
License
Apache
Author Information
RDO-CI Team