James Harris wrote:
On Mon, 2009-01-26 at 14:38 +0000, Dave Hatton wrote:
> Hi all,
>
> I've been thinking of developing a patch to add some form of system tags
> to cobbler.
>
> Initially I was thinking of a number of free format fields.
>
> System_Serial_Number
> System_Description
> System_Owner
> System_Location
>
> Maybe there are some more?
>
This would certainly be useful for the way we use Cobbler and Puppet.
At the moment we use Cobbler kickstart metadata to provide location
information that Puppet uses to set things like DNS server order and
backup server addresses based on the data centre where the host is
located.
It works, though it's not idea as you can easily forget to provide all
the information required.
The fields we use are data centre name, rack number and RU range (e.g.
RU17-19).
James
*********************************************************************************
Important Note
This email (including any attachments) contains information which is
confidential and may be subject to legal privilege. If you are not
the intended recipient you must not use, distribute or copy this
email. If you have received this email in error please notify the
sender immediately and delete this email. Any views expressed in this
email are not necessarily the views of AXA-Tech Australia. Thank you.
**********************************************************************************
_______________________________________________
cobbler mailing list
cobbler(a)lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/cobbler
Yeah, I think so, not having the fields overwriteable also makes sense.
Can folks come up with a common list of fields that would be useful for
this?
It concerns me slightly that we are building sort of /another/ inventory
system, though someone need not use it if they have another. Plus the
advantages (especially when we can do things like "cobbler find" to see
what's in what rack (cobbler find already exists as a command), would
definitely be worth it.
--Michael