625a628887
Bifrost was built around utilizing noauth authenticaiton mode. However the roles can easilly be re-utilized by users consuming only part of bifrost, or that are wishing to utilize the roles as examples to create their own playbooks. To allow re-consumption of roles interacting with ironic, addition of logic to allow for os-client-config to be utilized for module authentication Change-Id: I072791613cdf99723c567d24dbd3aee935e2e068 Implements: blueprint bifrost-role-auth-support
20 lines
899 B
YAML
20 lines
899 B
YAML
---
|
|
ironic_url: "http://localhost:6385/"
|
|
nginx_port: 8080
|
|
|
|
# Default network interface that bifrost will be attached to.
|
|
network_interface: "virbr0"
|
|
ans_network_interface: "{{ network_interface | replace('-', '_') }}"
|
|
|
|
# Normally this would setting would be http in a bifrost installation
|
|
# without TLS. This setting allows a user to override the setting in case
|
|
# the local webserver has been updated to support HTTPS.
|
|
# Note: Users wishing to leverage HTTPS should reference the iPXE
|
|
# documentation at http://ipxe.org/crypto
|
|
ipa_file_protocol: "http"
|
|
|
|
ipa_kernel_url: "{{ ipa_file_protocol }}://{{ hostvars[inventory_hostname]['ansible_' + ans_network_interface]['ipv4']['address'] }}:{{nginx_port}}/ipa.vmlinuz"
|
|
ipa_ramdisk_url: "{{ ipa_file_protocol }}://{{ hostvars[inventory_hostname]['ansible_' + ans_network_interface]['ipv4']['address'] }}:{{nginx_port}}/ipa.initramfs"
|
|
|
|
noauth_mode: true
|