Hello, Our physical hosts are all connected to trunk/tagged ports, with the native vlan (ex. 123) being used for the installation, and the real vlan (ex. 500, or number of choice depending on function) being used for prod traffic.
The host boots, uses the native vlan to get an ip via dhcp and to boot the installer via pxe, and then the installation starts. At the end, the tagged networking config is configured by puppet in the OS. At reboot - which is done manually - the network config is applied and the host is on the prod VLAN. I would like to continue with this workflow by using Foreman, but I don't know how to make the installer fetch a "temporary" ip for the installation and use the "real" ip for creating the config. I am aware of the concept of "provisioning" vs "primary" interface, but this is one single interface so I'm afraid this can't be done. I am open to alternative approaches, even getting rid of the trunks, if necessary (which would make things ridiculously simpler). Thanks -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
