Would it be crazy to need a foreman bootdisk based on UUID? For example,
instead of needing the MAC address for a specific host would it be useful
to autogenerate a UUID, embed it in the created ISO and recognize it when
the system boots to install it's self. In my mind, this might make it
easier to provision in VMWare without having to go first create the VM and
grab the MAC address.
Am I thinking about this wrong, or does this make sense?
Best Regards
Scott M
We have the concept of tokens in Foreman which could be added to a host
ISO image, but they have a limited lifetime (hours) so introduces an
expiry time to the image. The hope with MACs was they'd last longer
(plus MACs are mandatory for some orchestration events, so are often
available).
I think the full host image (bootdisk 3.2 onwards) has tokens embedded
though as it boots up differently, so you could perhaps try that too.
It could certainly be a better option if the host doesn't have a MAC,
please feel free to file it in Redmine.
···
On 18/03/15 22:15, smccarty@redhat.com wrote:
> Would it be crazy to need a foreman bootdisk based on UUID? For example,
> instead of needing the MAC address for a specific host would it be
> useful to autogenerate a UUID, embed it in the created ISO and recognize
> it when the system boots to install it's self. In my mind, this might
> make it easier to provision in VMWare without having to go first create
> the VM and grab the MAC address.
>
> Am I thinking about this wrong, or does this make sense?
–
Dominic Cleal
Red Hat Engineering