Problem: i need to customize the foreman discovery image
Expected outcome: while provitioining we need to update smart proxy url into formean-discovery iamge
Foreman and Proxy versions: 3.3
Foreman and Proxy plugin versions: 3.3
Distribution and version:
Other relevant data:
i need to modify fdi-bootable-3.3.1.iso so please suggest me any documnet
[root@boldforeman fdi-image]# pwd
/var/lib/tftpboot/boot/fdi-image
[root@boldforeman fdi-image]# ls -ltr
total 219904
-rw-r–r-- 1 foreman-proxy root 5393328 Jan 4 2017 vmlinuz0
-rw-r–r-- 1 foreman-proxy root 250 Jan 4 2017 README
-rw-r–r-- 1 foreman-proxy root 219778009 Jan 4 2017 initrd0.img
-rw-r–r-- 1 foreman-proxy root 153 Jan 4 2017 SHA256SUM
[root@boldforeman fdi-image]#
Hi
My foreman server and smart proxy servers are configured on Centos 7.
i can be able to provision the server successfully. but while boot with image i have to give smart proxy server Intractive mode to discovery the Mac address so i need to automate it discovery image
whatever you suggested document will work centos7 please suggest me
Helper script called discovery_remaster is being shipped with the foreman_discovery plugin. It can be used to make a copy of the ISO image with additional kernel command line options. Usage is simple:
i need to boot with network as i need to install with ISO image without any interaction inputs .
if i am booting with ISO image it needs to be SCAN mac address and send to foreman server via proxy region wise network .
After this you tell us if you have PXE or PXE-less environment. Means if you boot FDI ISO from (virtual) USB drive/CD-ROM or via network (=PXE) and if you have DHCP in your network or not.
Depending on this information we can tell you a) which cmdline parameters needs to be set and b) how you can set them.
I have Vsphere ( vmware network ) After selecting the DHCP network and providing the proxy server URL (https://hylforemanproxy.micron.com:9090), while booting with iso image ( fdi-bootable-3.3.1.iso) It will immediately send the MAC address to the Foreman server, where we will verify from the Hosts-> hots for discovery.
we are using CDROM in vmware network and booting with network and we have PXE boot environment for installation .
Upload resulting ISO to your vSphere, configure your VM to boot from it and have fun.
The package names might be different on other distributions. Do not take latest version (4a3c3d9) of discovery-remaster script from Github - does not work with older FDI ISO versions such as 3.3.1; b94bf01 as used in wget call is good enough.
For full automation you need to set:
proxy.url=https://<proxy-fqdn> – FQDN of your proxy, propably https://hylforemanproxy.micron.com
proxy.type=proxy – It’s a proxy, not Foreman directly
fdi.pxauto=1 – This does the automation magic, no need for manual confirmation
Once i installed required rpms then i am getting errors while creating iso image.
[root@hylformanproxy image]# ls -ltr
total 242692
-rw-r–r-- 1 root root 248512512 Jan 4 2017 fdi-bootable-3.3.1.iso
-rw-r–r-- 1 root root 3802 Mar 27 10:48 discovery-remaster
[root@hylformanproxy image]# bash ./discovery-remaster fdi-bootable-3.3.1.iso “proxy.url=https://hylformanproxy.micron.com proxy.type=proxy fdi.pxauto=1”
Copying contents to temporary directory…
Making hardlinks so inodes can be cached to save space…
/tmp/tmp.zqEaMo9loo /var/tmp/image
ln: failed to access ‘isolinux/initrd.img’: No such file or directory
ln: failed to access ‘isolinux/vmlinuz’: No such file or directory
/var/tmp/image
Configuring bootloaders…
Copy grub config to the ESP image…
Can’t open /tmp/tmp.zqEaMo9loo/images/efiboot.img: No such file or directory
Cannot initialize ‘::’
Bad target ::EFI/BOOT/grub.cfg
Building new ISO image…
Warning: creating filesystem that does not conform to ISO-9660.
Size of boot image is 4 sectors → No emulation
4.13% done, estimate finish Mon Mar 27 10:49:20 2023
8.26% done, estimate finish Mon Mar 27 10:49:20 2023
12.40% done, estimate finish Mon Mar 27 10:49:20 2023
16.53% done, estimate finish Mon Mar 27 10:49:20 2023
20.65% done, estimate finish Mon Mar 27 10:49:20 2023
24.78% done, estimate finish Mon Mar 27 10:49:20 2023
28.92% done, estimate finish Mon Mar 27 10:49:20 2023
33.04% done, estimate finish Mon Mar 27 10:49:20 2023
37.18% done, estimate finish Mon Mar 27 10:49:20 2023
41.30% done, estimate finish Mon Mar 27 10:49:20 2023
45.44% done, estimate finish Mon Mar 27 10:49:20 2023
49.56% done, estimate finish Mon Mar 27 10:49:20 2023
53.69% done, estimate finish Mon Mar 27 10:49:20 2023
57.82% done, estimate finish Mon Mar 27 10:49:20 2023
61.95% done, estimate finish Mon Mar 27 10:49:20 2023
66.08% done, estimate finish Mon Mar 27 10:49:20 2023
70.21% done, estimate finish Mon Mar 27 10:49:20 2023
74.33% done, estimate finish Mon Mar 27 10:49:20 2023
78.47% done, estimate finish Mon Mar 27 10:49:20 2023
82.59% done, estimate finish Mon Mar 27 10:49:20 2023
86.73% done, estimate finish Mon Mar 27 10:49:20 2023
90.85% done, estimate finish Mon Mar 27 10:49:20 2023
94.99% done, estimate finish Mon Mar 27 10:49:20 2023
99.11% done, estimate finish Mon Mar 27 10:49:20 2023
Total translation table size: 6249
Total rockridge attributes bytes: 2866
Total directory bytes: 10240
Path table size(bytes): 78
Max brk space used 22000
121085 extents written (236 MB)
isohybrid: fdi-bootable-3.3.1-230327_104859.iso: unable to find efi image
Inserting md5sum into iso image…
md5 = 5bfe2370c18c9c92fc557b2455b0f5f9
Inserting fragment md5sums into iso image…
fragmd5 = bc47ae7bb53dda959e8f55fb9650f8de8cbe27d52a4928bd281c8ae2f85b
frags = 20
Setting supported flag to 0
Created: fdi-bootable-3.3.1-230327_104859.iso (BIOS-only compatible)
Cleaning up temporary directory…
[root@hylformanproxy image]#
[root@hylformanproxy image]#
