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?
DRAC is not using the ksmeta info, there are seperate variables assigned
to power management.
Given, I know this isn't just about power, in which case, it might make
sense to rename the variable to something more
generic, like "management_address" instead of "power_address", though
I
suppose it's possible something might have
seperate power and seperate remote consoles, as there are remote console
cards that do that.
Anyone else have comments? I'm generally amenable to change, but don't
particularly like the idea of calling it a network
interface -- the network interface snippets are too complicated as is, I
don't want to make them more so.