Use a Parameter you can set them on an Organisation, Location, operating system, subnet, host group and host. They have a priority so you can override them at points*. You could get access them from the template using @host.params['<param-name>'] so when the hosts PXE template is generated it would be set to what ever that param is set to for that host.
* sorry I can't remember he priory right now! On Mon, 14 Nov 2016 at 11:59, Alexander Rilik <alexander.ri...@gmail.com> wrote: On Monday, November 14, 2016 at 12:25:54 PM UTC+1, Lukas Zapletal wrote: Unfortunately, global PXE templates are "dumb", there is no magic in there and no host/hostgroup associations. They are simple templates as simple as file copy can be. At least at the moment, this may change in the future (send a patch :-) Ouch, I see! Thanks for confirming. Would you recommend any workaround via Foreman, in the meantime? I have two solutions, so far, that don't involve Foreman, but I'd like to rely on it instead: - Point to a WDS url which returns a different IP based on the site (as explained in previous message) - Use Puppet to generate the PXE config, changing the url by site based on local facts -- 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 foreman-users+unsubscr...@googlegroups.com. To post to this group, send email to foreman-users@googlegroups.com. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout. -- 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 foreman-users+unsubscr...@googlegroups.com. To post to this group, send email to foreman-users@googlegroups.com. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
