+1
This would be huge for me. I know some (most) would prefer to KISS, but IMHO adding a small amount of code would save a whole lot of kludgey workarounds.

Owen Mann
Interactive Data Real Time Services
Email: owen.mann@interactivedata.com

James Cammarata <jimi@sngx.net>
Sent by: cobbler-devel-bounces@lists.fedorahosted.org

03/17/2009 02:19 PM

Please respond to
jimi@sngx.net; Please respond to
cobbler development list <cobbler-devel@lists.fedorahosted.org>

To	cobbler development list <cobbler-devel@lists.fedorahosted.org>
cc
Subject	Creating non-standard interfaces

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? -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. _______________________________________________ cobbler-devel mailing list cobbler-devel@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/cobbler-devel