1 The structure is being reworked. This page describes the DHA.yaml file.
3 Below is an example DHA for a libvirt deployment. An actual hardware deployment
4 could for instance add additional data fields to the node list, such as:
8 pxeMac: 52:54:00:9c:c2:c9
11 impiPassword: ericsson
14 The important thing is to keep the mandatory fields and add additional
15 ones to map to the DHA adapter implementation for the hardware in
18 The following example for libvirt is based on what's created by
21 Example DHA.yaml file for a libvirt adapter
23 # DHA API version supported
25 created: Wed Apr 22 11:34:14 UTC 2015
26 comment: Small libvirt deployment
28 # Adapter to use for this definition
32 # Mandatory fields are id, role and the "isFuel: true" property
33 # for the Fuel node if not fuelCustomInstall is set, when it is
35 # The MAC address of the PXE boot interface is not mandatory
36 # to be set, but the field must be present.
37 # All other fields are adapter specific.
41 pxeMac: 52:54:00:38:c7:8e
43 pxeMac: 52:54:00:9c:c2:c9
45 pxeMac: 11:11:11:11:11:11
48 # Deployment power on strategy
49 # all: Turn on all nodes at once. If MAC addresses are set these
50 # will be used for connecting roles to physical nodes, if the
51 # installation order will be arbitrary.
52 # sequence: Turn on the nodes in sequence starting with the lowest order
53 # node and wait for the node to be detected by Fuel. Not until
54 # the node has been detected and assigned a role will the next
58 # If fuelCustomInstall is set to true, Fuel is assumed to be installed by
59 # calling the DHA adapter function "dha_fuelCustomInstall()" with two
60 # arguments: node ID and the ISO file name to deploy. The custom install
61 # function is then to handle all necessary logic to boot the Fuel master
62 # from the ISO and then return.
63 # Allowed values: true, false
65 fuelCustomInstall: false