Build Hooks

[ColonelPanicks]

Not to be confused with #207.

The concept of build hooks would be able to run commands on both the controller and infrastructure systems as part of the build process.

An Example

The IPA service (which usually runs on infra01) is a host and user information service for the cluster. When a node is being built it needs to be added to the IPA service, this requires a command to be run on both infra01 and the node being built.

Currently, hosts are added to the IPA server on infra01 manually and the node is connected by using a firstrun script as part of the build process.

Further to this, if a node is being rebuilt then infra01 needs to disable and re-enable the entry for the host otherwise the IPA connection will fail.

What We're Looking For

Build hooks would need to:

• Run as part of metal build
• Allow custom user scripts to be added to the hook process
• Run commands both on the controller and other specified machines (most likely infrastructure nodes)
• Use the scope of the build command (whichever node/group is being built)

[ColonelPanicks]

A rethinking of the above, the initial outline is far more complicated than needs be. Quite simply what this would require from metalware is for it to template and run scripts in a directory as part of the metal build process. The requirements of which are:

• Scripts live in /var/lib/metalware/build_hooks/
• Each script is templated in the scope of each node in the build process (e.g. metal build node001 would do the equivalent of metal render /var/lib/metalware/build_hooks/myhook.sh node001 |/bin/bash, specifying a group with -g nodes would loop through the nodes and the build_hook scripts)
• Output from the build_hooks scripts to go to /var/log/metalware/build_hooks.log