I think what you are describing is auto-inventory, seeding Cobbler
with
all of the MAC address info it can, and then provisioning later once you
assign them to certain profiles.
You don't need all the NIC info in Cobbler to provision, certaintly...
folks can also deploy using profile records if they don't want to create
the system records.
The MAC is of course required to pin a specific piece of hardware to a
specific profile without using the menus or the default profile, or
without using a "per-network" profile mapping (cobbler system record
with --ip input in CIDR notation to assign only certain systems to
certain profiles).
Agree, the auto-inventory is a better word. It is an addition to the existing
auto-registration and can (if enabled for the system) also be used for manual added
entries.
The new networking code for bonding requires a MAC address for each NIC.
The inventory probe sounds interesting to me, otherwise improving
and
adding to the registration mechanism could be very interesting.
(Especially if it described a bit more about the system maybe in the
comment field, and maybe had options on also registering inventory with
a Smolt server?) We haven't persued any kind of trivial cobbler+smolt
integration in the past though it may be something we can do in the
future.
You mean running a smolt-server on the node where the cobbler-server is running?
Regards,
Peter
This e-mail and any attachment is for authorised use by the intended recipient(s) only. It
may contain proprietary material, confidential information and/or be subject to legal
privilege. It should not be copied, disclosed to, retained or used by, any other party. If
you are not an intended recipient then please promptly delete this e-mail and any
attachment and all copies and inform the sender. Thank you.