RFE: Host pre-registration feature instead of discovery

[lzap]

@bhawksfan

templates are difficult to get right, especially with languages that are highly sensitive to leading whitespace as python is

Noted, there was another concern raised that python might be available in other versions in older systems (python2 vs python3). So I am actually considering utilizing shell script to gather facts now rather than python. And instead of JSON facts transferred in HTML body, we would use HTTP headers (key-value strings) instead. We really do not need to find much info.

@bhawksfan

I’m not quite clear how this would work within %pre, since there’s not really enough information to base the rest of the kickstart template on. For example, the kickstart template wouldn’t know what the machine’s FQDN is supposed to be during the pre-registration phase.

The main idea behind Anaconda-Pre is here: Idea: Dracut/Anaconda-based discovery image

Now, FQDN is fact we will definitely not send in the new design - why would you need that? On discovery image it is always fdi, unless overwritten by DHCP which I think is turned off anyway. If someone needs some extra information (let’s say a vendor option from DHCP) a custom fact can be made.