On Tue, 17 Mar 2009 20:14:43 +0100, Jasper Capel capel@stone-it.com wrote:
On 03/17/2009 07:19 PM, James Cammarata wrote:
Ok, so I was working on some snippets the other day for configuring our Dell DRAC interfaces (similar to HP iLO, etc.) using ksmeta variables, when it occurred to me that it would be a better idea to use the interfaces capability of the system object to store this information. For example:
cobbler system edit --name=foo --interface=DRAC --ip=1.2.3.4...
In this way, we could use the built-in error checking, and not have to worry about ks-meta accidently being blown away by an admin who doesn't know about --in-place. Obviously, this presents an issue with the existing snippets and koan's functionality, which would have to be taught to ignore interfaces named after certain key words, or to add a configuration command option to mark certain interfaces as "virtual", along the lines of
bonded
interfaces.
We could then write an OOB network snippet to configure the hardware for HP, IBM, Dell, or whatever other manufacturers that may have similar setups.
Thoughts?
Can't we just add two extra fields (subnet/gateway) to the power stuff for this? Or maybe I'm missing the whole point. :)
Perhaps, I'm not that familiar with the power stuff, though that would mean people would also need to install CMAN in order to do OOB management interfaces, wouldn't it? I know fencing uses these same objects, but fencing also supports a lot of other stuff that would not qualify for this, nor would many people use it.
There is definitely some cross over here though, question is simply which would we prefer handle this?