-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Forgot to mention, WRT multiple interfaces, it's probably fair to
just
report multiple lines for the system in that case, rather than making it
bleed over if using any of the Wiki/CSV type outputs. This basically
makes the system report be a report of it's interfaces. The text can
probably remain as it is today, though some improvement is welcome there
too.
Yes, we'll want to support multiple interfaces as they are in
wide-enough use that it would cause some confusion if we didn't.
Here is my question about multiple interfaces:
Let say I did:
cobbler system report --fields=name,mac_address
What mac_address would that be? Should one have to specify which
interface they want? Or should we just assume that ==fields,mac_address
will show as many mac_addresses as they are defined for a given system?
Pending the question above, here is my plan:
Alright, I will work on adapting the code to support multiple
interfaces, and also instead of using the config file, I'll add the
- --fields parameter.
Once I get that working, I will 'come back' and discuss more about
integrating with cobbler.
Thanks,
AS
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Fedora -
http://enigmail.mozdev.org
iD8DBQFImc5nECmX3C4JWKgRAugQAKC9BbZqcBkiq2F/zMA6FWy6a4BTfQCeIcPh
HhTdHMCd8OK6KzyMYPLO/TI=
=PAx3
-----END PGP SIGNATURE-----