Vreman, Peter - Acision wrote:
> -----Original Message-----
> From: cobbler-bounces(a)lists.fedorahosted.org [mailto:cobbler-
> bounces(a)lists.fedorahosted.org] On Behalf Of Vreman, Peter - Acision
> Sent: woensdag 3 december 2008 15:36
> To: cobbler mailing list
> Subject: RE: autodiscovery questions
>
>
>> 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?
>
For the auto-inventory I think we can use the output of the lshal command.
lshal contains all information for the network (MAC,ethX and driver) and also provides
information about the system including vendor and serial information
For the inventory it is also usefull to have additional system information fields
available for filtering. E.g. a systems with 64G memory are better suited for a DB profile
than the systems with 8G memory for webservers.
This sounds excellent.
I think it /seems/ to indicate that the following should exist:
koan --server=cobbler.example.com --register-me
Which would register the box if not already registered and add the
hardware info. If the box already existed in cobbler it would only
update the hardware info (like RAM) (to avoid overwriting other more
important data) and refuse to update the network data if already set up.
The live CD you mention could use this.
As I mentioned earlier, due to security reasons, we'd want this off by
default.
Ideally I think we want a setting like:
extended_registration_enabled: 1
And we could obsolete the existing "register new MACs" functionality as
this would be more feature-rich.
It's a slight weakness in that this would create an API that could allow
data in cobbler to be manipulated without access (like the RAM amounts
as we indicate above), though we do it right it should be reasonably
feature rich.
We could think about requring usernames and passwords but since this is
in a provisioning context those credentials would be exposed anyway, so
it's not that useful to do so.
I've also thought about doing something like this through Func, though
I'm not sure everyone would want to adopt Func for this so something
self contained might be better.
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.
_______________________________________________
cobbler mailing list
cobbler(a)lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/cobbler