> The biggest challenge is that pieces of the oVirt project require there > to be persistent storage locally. For example, when you register a node > with the engine, a manual step is required to approve the node. After > this manual step, some certificates are copied locally into the node and > stored. That way, the node can immediately identify itself with the > engine and start working with no need to identify itself. > > To solve this problem, we need to either > 1. remove the need to store stuff locally > 2. provide some way to package up this config and store it somewhere, > then retrieve on boot > 3. embed some sort of key or certificate in the pxe image that allows > the engine to know that this valid machine and automatically approve it. Is there a method to pre-generate a set of certificates/configuration files for a node? It is not that hard to let the boot server serve the node-specific configuration files as a cpio (initramfs) archive, based on the MAC-address of the node. The kernel supports having more than one initramfs file, and simply combines the files from both archives.