Stephen John Smoogen wrote: > On Wed, Mar 4, 2009 at 5:08 PM, Michael DeHaan <[email protected]> wrote: > >> Corey Osman wrote: >> >>> I could probably add the following when I get a chance since I know >>> IPMI. >>> >>> cobbler-register --use-ipmi=<IP of server> >>> >>> then have in the settings a default username/password for connecting >>> to IPMI >>> >>> It would then return all the variables and such. >>> >>> >>> >>> >> I had considered --extra-opts that would take all the other opts that >> XMLRPC can take. We could do that (at least for the scalar options). >> >> I also forgot to tell it to save the kickstart arguments from >> /proc/cmdline (if that flag, say --include-kopts is used). >> >> --Michael >> > > What is the list of things that cobbler would need to know.. would it > be like what 'facter' gives off? > > My network, > My CPU, > My motherboard > My mom's maiden name > >
More like anything someone would want to force feed down through templating. The IPMI case is something that can't be auto-discovered, for instance. But yeah, we should look at facter and see what it can mine. Func could use some of the same data, so eventually having a Python version of something like that could be helpful. Right now we are grabbing network info from rhpl.eththool, and rhpl is available for Debian (for instance), but is probably /not/ intended to be highly portable. Possible future subproject :) I think I'd want keep it simple for starters though and just have a way to push extra variables in from the command line. --Michael _______________________________________________ cobbler mailing list [email protected] https://fedorahosted.org/mailman/listinfo/cobbler
