Red Hat Bugzilla – Bug 832000
Reduce number of kargs to enable a better automated installation with PXE
Last modified: 2014-04-30 07:44:42 EDT
Description of problem:
Currently we've got quite many kernel args and even more kernel args are required if an automatic installation is performed (like in automated testing).
The number of required/default kernel arguments should be reduce (e.g. removing the iso name) to allow the addition of additional arguments (like for creating specififc sawp partitions etc)
What I missed: This isn't a problem for an ISO but when bootign via PXE.
What are you proposing here?
Some functionality to pass the informations we need to auto-install/configure the node on a way different from kargs.
<mburns> fabiand: number of kargs -- yes, it's a problem, but it's really bigger than that
<mburns> we need something different than kargs
<fabiand> mburns, something like ks :)
<mburns> either kickstart functionality or something similar
<fabiand> a file defining stuff that can be defined
<mburns> fabiand: exactly
<mburns> something like passing /etc/default/ovirt
I see two obvious ways of implementing this:
1. Pass an URL where to fetch the contents of /etc/default/ovirt
2. Pass an URL where to fetch the variables formatted as kernel arguments
I'm currently favoring the second solution because it can be implemented without changing much code and established code paths would be reused to transform the arguments into the appropriate /etc/default/ovirt file.
Sometimes, like in the case of BOOTIF, there is not just a 1:1 mapping between the KARG and a oVirt Node variable, but there also additional logic happening when the kargs are parsed. We would have to introduce some mechanism to run this logic when we are not using the kargs for all arguments.
Or am I wrong in my last point?
We should investigate which arguments can be dropped from the default cmdline.
This is an automated message.
Re-targeting all non-blocker bugs still open on 3.4.0 to 3.4.1.
This needs to be addressed differently.
The basic problem i sthat the management on the kargs on the server side is not solved.
This is up to confmgmt systems like Foreman, to keep track of the right args.
Node should not provide it's own mechanism to organize kargs on the server side.