Christopher Johnston wrote:
Some _possible_ ones that come to mind, although this seems to be
something that would be stored in a CMDB (which sounds like cobbler
could potentially be used for that). Console information is
important, but this may not be the right place to store it.
system_region (US, EU, FE)
system_location (NY, LON, CHI)
system_datacenter (DC1, DC2)
These three we don't have. Though they could perhaps be stored in
the comment field, that would not be highly structured though.
system_owner (chris)
--owners means something to authz_ownership, but can otherwise be abused
if one wants, even if not using that module.
system_description (HP DL360 G5)
Every cobbler object has a
--comment field that is free form right now,
and would be good for this.
console_host (con01)
console_speed (115200)
console_port (ttyS0)
These seem to be kernel arguments for setting up consoles to me, and can
be stored in --kopts
On Tue, Jan 27, 2009 at 8:38 AM, Dave Hatton <lists(a)davehatton.it
<mailto:lists@davehatton.it>> wrote:
> 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.
>
>
I'll happily collate the responses and try to get an agreed list
Dave
_______________________________________________
cobbler mailing list
cobbler(a)lists.fedorahosted.org <mailto:cobbler@lists.fedorahosted.org>
https://fedorahosted.org/mailman/listinfo/cobbler
------------------------------------------------------------------------
_______________________________________________
cobbler mailing list
cobbler(a)lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/cobbler