Mark Goddard d28635d2cf Changes to support standalone ironic
For standalone ironic deployments, such as those deployed using bifrost, there
is typically no keystone or placement service running. Use of the ironic API is
without authentication. We use clouds.yaml in this case.

Change-Id: I61ed791d019e43f6dfc632fa185f079b385c290c
Story: 2004425
Task: 28077
2018-12-20 09:48:21 +00:00
..
2018-08-31 16:57:34 +00:00

Ironic Enrolment

This role enrols nodes with OpenStack Ironic, creates Ironic ports for each of the nodes' NICs, and sets relevant attributes on created resources.

Requirements

  • OS_* environment variables for the OpenStack cloud in question present in the shell environment. These can be sourced from an OpenStack RC file, for example.

  • The virsh command-line tool present at /usr/bin/virsh.

Role Variables

  • ironic_nodes: A list of dicts of details for nodes that are to be enroled in Ironic.
  • ironic_hypervisor: The hostname of the hypervisor on which ironic_nodes exist.
  • ironic_deploy_kernel_uuid: The Glance UUID of the image to use for the deployment kernel.
  • ironic_deploy_ramdisk_uuid: The Glance UUID of the image to use for the deployment ramdisk.
  • ironic_virtualenv_path: The path to the virtualenv in which to install the OpenStack clients.
  • ironic_python_upper_constraints_url: The URL of the upper constraints file to pass to pip when installing Python packages.