| Summary: | Organized PXE menu in beaker | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Nilesh Patil <npatil> | ||||||||||
| Component: | cobbler | Assignee: | Bill Peck <bpeck> | ||||||||||
| Status: | CLOSED DEFERRED | QA Contact: | |||||||||||
| Severity: | medium | Docs Contact: | |||||||||||
| Priority: | unspecified | ||||||||||||
| Version: | 15 | CC: | awood, bpeck, dcallagh, jimi, mcsontos, parimbra, rmancy, scott, stl, vanmeeuwen+fedora | ||||||||||
| Target Milestone: | --- | Keywords: | Reopened | ||||||||||
| Target Release: | --- | ||||||||||||
| Hardware: | Unspecified | ||||||||||||
| OS: | Linux | ||||||||||||
| Whiteboard: | |||||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||||
| Doc Text: | Story Points: | --- | |||||||||||
| Clone Of: | Environment: | ||||||||||||
| Last Closed: | 2012-08-22 23:12:17 UTC | Type: | --- | ||||||||||
| Regression: | --- | Mount Type: | --- | ||||||||||
| Documentation: | --- | CRM: | |||||||||||
| Verified Versions: | Category: | --- | |||||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||||
| Attachments: |
|
||||||||||||
Created attachment 479039 [details]
rhel 5 submenu
Created attachment 479040 [details]
main menu
Created attachment 479041 [details]
pxemenu default file
Created attachment 479042 [details]
rhel5 conf file
Some great ideas here. But beaker doesn't generate the pxe menu, you really want to open these against cobbler. Changed component and reopening ticket. It would be really nice to have it as associates always get confused on versions,releases and on top of that so many options. I could help you to build menu. - Nilesh Can you please file this upstream with cobbler? https://fedorahosted.org/cobbler/newticket As of version 0.9 Beaker is generating its own PXE menu, and it is organised by distro family and version. |
What we see currently is in pxe menu of lab.rhts.eng.pnq.redhat.com, a list of all available trees especially so many nightly, rel-eng etc updates, releases with nfs, http and ftp options for each tree. So it becomes difficult for end user to choose correct option. Whereas most of the users would be using only small subset of available options. Can we have proper segregation of available list, it will be easy to locate a particular tree/release to install, like we have done in GSS Lab Pune. Please find attached screenshot of pxemenu and configuration files. snippet of configuration files are here, "/tftpboot/pxelinux.cfg/default" file contains, ---------------------------------------------- default menu.c32 prompt 0 ONTIMEOUT local MENU TITLE GSSLAB PXE LABEL local MENU LABEL Boot locally LOCALBOOT 0 label RHEV menu label ^RHEV kernel menu.c32 append pxelinux.cfg/rhev.cfg label RHEL 6 menu label ^RHEL 6 kernel menu.c32 append pxelinux.cfg/rhel6.cfg And "pxelinux.cfg/rhel6.cfg" file contains, ---------------------------------------------- MENU TITLE RHEL 6 LABEL Main Menu MENU LABEL Main Menu KERNEL menu.c32 APPEND pxelinux.cfg/default label RHEL6.1 x86_64 - nightly kernel global-sync/rhel/nightly/latest-RHEL-6/6.1/Server/x86_64/os/vmlinuz append initrd=global-sync/rhel/nightly/latest-RHEL-6/6.1/Server/x86_64/os/initrd.img lowres ramdisk_size=9216 raid=noautodetect lang= ks=nfs:10.65.208.3:/share/ks/rhel6u1-nightly-x86_64.cfg ksdevice=eth0 label RHEL6.1 i386 - nightly kernel global-sync/rhel/nightly/latest-RHEL-6/6.1/Server/i386/os/vmlinuz append initrd=global-sync/rhel/nightly/latest-RHEL-6/6.1/Server/i386/os/initrd.img lowres ramdisk_size=9216 raid=noautodetect lang= ks=nfs:10.65.208.3:/share/ks/rhel6u1-nightly-i386.cfg ksdevice=eth0 Thanks Nilesh