On Wed, 2 Mar 2011 08:15:32 -0500, Jonathan Sabo <[email protected]> wrote: > On Wed, Mar 2, 2011 at 7:58 AM, Jonathan Sabo <[email protected]> wrote: > > It's clearly not intended to be restricted to just Cobbler developers > > and maintainers. It's not hidden from the user at all and there are > > some things in Cobbler that are indeed kept from the users. The > > comments field is not one of them. In fact it's made available for > > user's to enter information (notes, descriptions, comments) through > > out the entire hierarchy of the objects in the Web UI, cli, and api. > > > > When you say users you mean people looking at a pxe menu don't you and > not people using the Cobbler Web UI or cli? Those would be your > "maintainers"? I can understand wanting the comments field all for > yourself and a separate one in that case but I also don't think we > should have lots of fields with an overlapping purpose.
Yeah, duplication would be my problem as well. The thing is, that once the comment is exposed in the pxe template, you can process it in whatever way you see fit. So if you want to have some complex string data type in there that python/cheetah can parse and then extract the description, that would work. Having said the above, we have talked in the past about a misc field. Something that could contain a python/json dictionary and allow the user to stuff whatever they want in there. I'd be fine adding something like this in to make the above easier to do. -- Scott Henson Red Hat CIS Operator WVU Alum BSAE/BSME
pgptXdukk23o2.pgp
Description: PGP signature
_______________________________________________ cobbler mailing list [email protected] https://fedorahosted.org/mailman/listinfo/cobbler
