On Fri, Mar 10, 2017 at 11:49 AM, Alexander Rilik <[email protected]> wrote: > Now, question: how does foreman react to the installation being done with > one IP (in subnet/vlan 123) and the host ending up in another subnet/vlan > (500)? I suppose Foreman will create the DNS records for the first IP (in > vlan 123), not for the real (500), causing a mismatch.
Foreman itself cant manage one NIC (MAC address) for multiple subnets, a NIC is one entity which is assigned exactly to one subnet. Foreman is capable of re-configuring NICs on fact upload (this can be turned off or on in settings), so you can let facter to do the job for you during initial fact upload. So I think your initial idea (workflow 1) is doable. One more thing. Our PXELinux templates don't ship with VLAN configuration flags as most of our users use non-VLANs for provisioning. Feel free to make adjustments there (and file pull request in our https://github.com/theforeman/community-templates repo) for that. Usually it's just a flag on kernel command line to set vlan. Oh I see now you are using untagged VLAN for provisioning, then you should be fine. -- Later, Lukas @lzap Zapletal -- 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.
