On Fri, Oct 14, 2016 at 1:21 AM, Lukas Zapletal <[email protected]> wrote:
> > It looks like many of many customizations can be folded into one of these > > arrays, which would simplify our own templates and make it easier to keep > > them in sync with the upstream versions. > > > > How could I make use of the <%= options %> or <%= pxe_kernel_options %> > > arrays? I can't find any documentation about them. Would I want to set > > parameters on a Host Group basis? > > If you can help us defining which options to include, that would be > great. I only use Redhat systems and blacklist is the only parameter I > make use of, so can't think of others. > Our own examples are a bit localized, but are probably useful for other groups. Currently, I'm adding options using simple 'if/elsif/else' statements in the body of my templates, but I think this could be accomplished more elegantly. - The first option is to workaround a bug with VMware and Red Hat's consistent device naming, which creates network device names with crazy names like 'eno16777723' and 'eno33555201'. Our workaround is to append 'net.ifnames=0 biosdevname=0' to the kernel parameters, as you can see above. - The second is to activate a serial console for our Supermicro bare metal servers, using the device assigned for the IPMI/BMC's "Serial over LAN" feature. If these kernel parameters are added during provisioning, they persist after the provisioning is complete. Systemd will automatically activate the serial console, and there is no need to add a new Puppet class to make the changes. Maybe we could make a generic param kernel_cmdline that would work with > any OS. If you like the idea, file a feature ticket for me, easy change. Sounds good. I'll file a ticket soon. (Whoa, sorry for the delay. I thought I sent this message last week!) -= Stefan > > -- > Later, > Lukas #lzap Zapletal > > -- > You received this message because you are subscribed to a topic in the > Google Groups "Foreman users" group. > To unsubscribe from this topic, visit https://groups.google.com/d/to > pic/foreman-users/pFSAPKen7QA/unsubscribe. > To unsubscribe from this group and all its topics, 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. > -- Stefan Lasiewski Email: [email protected] Computer System Engineer III Email: [email protected] NERSC Data Infrastructure Group National Energy Research Scientific Computing Center (NERSC <http://nersc.gov>) Lawrence Berkeley National Laboratory -- 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.
