I would like to be able to append some explanatory text to [some of] the PXE menu entries.
I can see that the Cobbler-generated pxelinux.cfg/default file has a MENU LABEL line for each entry. I can see in the pxeprofile.template file that this is from variable $menu_label. But I don't see any way to modify or append to it from anything in profile dumpvars. Is there a way? If not, is this a planned enhancement?
That is, instead of seeing: Fedora14-i386-Web1 Fedora14-i386-Web2 one might see: Fedora14-i386-Web1 -- For internal intranet web servers Fedora14-i386-Web2 -- For web servers on the DMZ
On Fri, 25 Feb 2011 23:13:30 -0800, petermity 6t12-n6js@dea.spamcon.org wrote:
I would like to be able to append some explanatory text to [some of] the PXE menu entries.
I can see that the Cobbler-generated pxelinux.cfg/default file has a MENU LABEL line for each entry. I can see in the pxeprofile.template file that this is from variable $menu_label. But I don't see any way to modify or append to it from anything in profile dumpvars. Is there a way? If not, is this a planned enhancement?
No and not currently but we would love something like that. Every profile has a 'comment' section. I don't think it would be hard to get that exposed in the template and include it.
On Feb 28, 2011, at 1:12 PM, Scott Henson wrote:
On Fri, 25 Feb 2011 23:13:30 -0800, petermity 6t12-n6js@dea.spamcon.org wrote:
I would like to be able to append some explanatory text to [some of] the PXE menu entries.
I can see that the Cobbler-generated pxelinux.cfg/default file has a MENU LABEL line for each entry. I can see in the pxeprofile.template file that this is from variable $menu_label. But I don't see any way to modify or append to it from anything in profile dumpvars. Is there a way? If not, is this a planned enhancement?
No and not currently but we would love something like that. Every profile has a 'comment' section. I don't think it would be hard to get that exposed in the template and include it.
Rather than expose comment, it should probably be a new field. Otherwise someone might be caught by surprise... :p
Allen Wittenauer awittenauer@linkedin.com wrote:
On Feb 28, 2011, at 1:12 PM, Scott Henson wrote:
On Fri, 25 Feb 2011 23:13:30 -0800, petermity 6t12-n6js@dea.spamcon.org wrote:
I would like to be able to append some explanatory text to [some of] the PXE menu entries.
I can see that the Cobbler-generated pxelinux.cfg/default file has a MENU LABEL line for each entry. I can see in the pxeprofile.template file that this is from variable $menu_label. But I don't see any way to modify or append to it from anything in profile dumpvars. Is there a way? If not, is this a planned enhancement?
No and not currently but we would love something like that. Every profile has a 'comment' section. I don't think it would be hard to get that exposed in the template and include it.
Rather than expose comment, it should probably be a new field. Otherwise someone might be caught by surprise... :p
I agree, it should be something new and separate like $menu_description, for profiles, systems, and images.
On Tue, Mar 1, 2011 at 1:17 AM, petermity 6t12-n6js@dea.spamcon.org wrote:
Allen Wittenauer awittenauer@linkedin.com wrote:
On Feb 28, 2011, at 1:12 PM, Scott Henson wrote:
On Fri, 25 Feb 2011 23:13:30 -0800, petermity 6t12-n6js@dea.spamcon.org wrote:
I would like to be able to append some explanatory text to [some of] the PXE menu entries.
I can see that the Cobbler-generated pxelinux.cfg/default file has a MENU LABEL line for each entry. I can see in the pxeprofile.template file that this is from variable $menu_label. But I don't see any way to modify or append to it from anything in profile dumpvars. Is there a way? If not, is this a planned enhancement?
No and not currently but we would love something like that. Every profile has a 'comment' section. I don't think it would be hard to get that exposed in the template and include it.
Rather than expose comment, it should probably be a new field. Otherwise someone might be caught by surprise... :p
I agree, it should be something new and separate like $menu_description, for profiles, systems, and images.
cobbler mailing list cobbler@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/cobbler
I think you should use the comments field instead of creating another field with the same purpose as the one that already exists. You could make it configurable in settings if you want to have them be in your menu so there are no surprises.
On Tue, 1 Mar 2011 07:48:43 -0500, Jonathan Sabo jsabo@criminal.org wrote:
I think you should use the comments field instead of creating another field with the same purpose as the one that already exists. You could make it configurable in settings if you want to have them be in your menu so there are no surprises.
+1, patches?
Scott Henson shenson@redhat.com wrote:
On Tue, 1 Mar 2011 07:48:43 -0500, Jonathan Sabo jsabo@criminal.org wrote:
I think you should use the comments field instead of creating another field with the same purpose as the one that already exists. You could make it configurable in settings if you want to have them be in your menu so there are no surprises.
+1, patches?
To me, it seems better to have a separate setting. The comment is for the Cobbler developer/maintainer. The new menu description item is for the users of the Cobbler system.
On Wed, Mar 2, 2011 at 3:05 AM, petermity 6t12-n6js@dea.spamcon.org wrote:
Scott Henson shenson@redhat.com wrote:
On Tue, 1 Mar 2011 07:48:43 -0500, Jonathan Sabo jsabo@criminal.org wrote:
I think you should use the comments field instead of creating another field with the same purpose as the one that already exists. You could make it configurable in settings if you want to have them be in your menu so there are no surprises.
+1, patches?
To me, it seems better to have a separate setting. The comment is for the Cobbler developer/maintainer. The new menu description item is for the users of the Cobbler system.
cobbler mailing list cobbler@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/cobbler
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.
-----Original Message----- From: cobbler-bounces@lists.fedorahosted.org [mailto:cobbler-bounces@lists.fedorahosted.org] On Behalf Of Jonathan Sabo Sent: Wednesday, March 02, 2011 12:58 To: cobbler mailing list Cc: petermity Subject: Re: Add descriptions to PXE menu entries?
On Wed, Mar 2, 2011 at 3:05 AM, petermity 6t12-n6js@dea.spamcon.org wrote:
Scott Henson shenson@redhat.com wrote:
On Tue, 1 Mar 2011 07:48:43 -0500, Jonathan Sabo jsabo@criminal.org wrote:
I think you should use the comments field instead of creating another field with the same purpose as the one that already exists. You could make it configurable in settings if you want to have them be in your menu so there are no surprises.
+1, patches?
To me, it seems better to have a separate setting. The comment is for the Cobbler developer/maintainer. The new menu description item is for the users of the Cobbler system.
cobbler mailing list cobbler@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/cobbler
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. _______________________________________________ cobbler mailing list cobbler@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/cobbler
But given that the field is potentially used for quite a lot of information, would that not generally be too much info for inclusion in a boot menu, would it not be better to have the comments field as a large field that can contain plenty of info, and a separate field that is used for a concise boot menu item description?
Paul This communication is for informational purposes only. It is not intended as an offer or solicitation for the purchase or sale of any financial instrument or as an official confirmation of any transaction. All market prices, data and other information are not warranted as to completeness or accuracy and are subject to change without notice. Any comments or statements made herein do not necessarily reflect those of JPMorgan Chase & Co., its subsidiaries and affiliates.
This transmission may contain information that is privileged, confidential, legally privileged, and/or exempt from disclosure under applicable law. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or use of the information contained herein (including any reliance thereon) is STRICTLY PROHIBITED. Although this transmission and any attachments are believed to be free of any virus or other defect that might affect any computer system into which it is received and opened, it is the responsibility of the recipient to ensure that it is virus free and no responsibility is accepted by JPMorgan Chase & Co., its subsidiaries and affiliates, as applicable, for any loss or damage arising in any way from its use. If you received this transmission in error, please immediately contact the sender and destroy the material in its entirety, whether in electronic or hard copy format. Thank you.
Please refer to http://www.jpmorgan.com/pages/disclosures for disclosures relating to European legal entities.
On Wed, Mar 2, 2011 at 7:58 AM, Jonathan Sabo jsabo@criminal.org wrote:
On Wed, Mar 2, 2011 at 3:05 AM, petermity 6t12-n6js@dea.spamcon.org wrote:
Scott Henson shenson@redhat.com wrote:
On Tue, 1 Mar 2011 07:48:43 -0500, Jonathan Sabo jsabo@criminal.org wrote:
I think you should use the comments field instead of creating another field with the same purpose as the one that already exists. You could make it configurable in settings if you want to have them be in your menu so there are no surprises.
+1, patches?
To me, it seems better to have a separate setting. The comment is for the Cobbler developer/maintainer. The new menu description item is for the users of the Cobbler system.
cobbler mailing list cobbler@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/cobbler
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.
On Wed, 2 Mar 2011 08:15:32 -0500, Jonathan Sabo jsabo@criminal.org wrote:
On Wed, Mar 2, 2011 at 7:58 AM, Jonathan Sabo jsabo@criminal.org 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 shenson@redhat.com wrote:
On Wed, 2 Mar 2011 08:15:32 -0500, Jonathan Sabo jsabo@criminal.org wrote:
On Wed, Mar 2, 2011 at 7:58 AM, Jonathan Sabo jsabo@criminal.org 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.
I don't think that a "misc" field would work for this particular case, because Cobbler handles the creation of the PXE boot menu, so it has to do the processing.
I learned today of another PXE menu feature (menu.c32) that Cobbler could take advantage of, along these same lines. You can define a multi-line description via TEXT HELP ... ENDTEXT in a LABEL section, showing the description at the bottom of the screen when you select that entry. Ideally there would be a Cobbler variable that could be set for each profile etc. that would do this.
petermity 6t12-n6js@dea.spamcon.org wrote:
Scott Henson shenson@redhat.com wrote:
On Wed, 2 Mar 2011 08:15:32 -0500, Jonathan Sabo jsabo@criminal.org wrote:
On Wed, Mar 2, 2011 at 7:58 AM, Jonathan Sabo jsabo@criminal.org 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.
I don't think that a "misc" field would work for this particular case, because Cobbler handles the creation of the PXE boot menu, so it has to do the processing.
I submitted an enhancement issue for menu descriptions: https://fedorahosted.org/cobbler/ticket/654
I learned today of another PXE menu feature (menu.c32) that Cobbler could take advantage of, along these same lines. You can define a multi-line description via TEXT HELP ... ENDTEXT in a LABEL section, showing the description at the bottom of the screen when you select that entry. Ideally there would be a Cobbler variable that could be set for each profile etc. that would do this.
Although the above paragraph didn't trigger any discussion yet, I submitted an enhancement issue for it as well: https://fedorahosted.org/cobbler/ticket/655#preview
cobbler@lists.fedorahosted.org