[SOLVED] How to test WADS in parallel with a PXE FOG server

[pierre.briec]

Hello everyone,

I'm currently using the latest WAPT Enterprise version. I wanted to test OS deployment.
At the moment, my infrastructure is configured to boot PXE with my FOG server.
Do you know of a way to test the WADS solution in parallel by adding an entry to the PXE menu to maintain normal operation while allowing testing of the solution?
For example:
`set pxeserver:ipv4 IP-SRVWAPT` `
set next-server ${pxeserver}`
`set filename ipxe.efi` `
chain tftp://${next-server}/${filename}`

Is this possible?
Thanks in advance
, Pierre Briec

[sfonteneau]

Good morning

If your IPXE has an IPXE script like this, it should work:

Code: Select all

#!ipxe

:menu
menu iPXE Boot Menu
item waptdeploy   WAPTDEPLOY
item fog          FOG
choose --default fog --timeout 5000 selected && goto ${selected}

:waptdeploy
chain http://srvwapt.mydomain.lan/api/v3/baseipxe?keymap=fr

:fog
chain http://fog.mydomain.lan/fog/service/ipxe/boot.php

[pierre.briec]

Thanks Simon,

I tested the PXE deployment using this method and it works well. The test was successful.

I have a few questions regarding WADS (FOG battle mode )
- does WADS also handle WOL for launching the deployment? I'm deploying laptops that are plugged into cabinets (30 PCs connected to a power/Ethernet dock), so I need everything to go smoothly, including the boot process.
Is it possible to limit the number of machines that can be deployed simultaneously?

I have machines that don't support WOL over PXE, so they are configured to boot from the network by default.
With FOG, the default behavior was to boot the OS.
What is the default behavior if it boots from WADS' PXE?
In my test, it didn't work, but since it's somewhat of a hybrid setup, is this the expected behavior?

Thanks

[sfonteneau]

- Does WADS also handle WOL for launching the deployment? I'm deploying laptops that are plugged into cabinets (30 PCs connected to a power/Ethernet dock), so I need everything to go smoothly without any prior knowledge, including the boot process.

If they are already registered in Wapt, you can go directly through the central inventory. (WakeOnLAN is already in the central inventory.)

In fact, instead of using PXE, you can use:

https://wapt.tranquil.it/store/fr/tis-d ... run-deploy

Which installs WinPE directly on the machine itself, thus bypassing PXE and IPXE.

- Can we impose a limit on the number of posts that can be done simultaneously?

Since it's a simple file distribution done by nginx, we didn't plan for it.
The more you add, the more it divides the speed between the number of workstations. (We're not doing unicast deployment either.)

I have machines that don't support Wake-on-LAN (WOL) over PXE, so they are configured to boot from the network by default.
With FOG, the default behavior was to boot the OS.
What is the default behavior if it boots from WADS' PXE?

In general, if the machine is not waiting for deployment, it "exits", see: https://ipxe.org/cmd/exit

So, "normally," depending on the BIOS, it should work on the next boot. (i.e., your hard drive)

I say "normally" because BIOSes behave differently depending on the manufacturer...

In your case, if you explore the tis-dangerous-package-wads-run-deploy package, it's possible that this could solve certain problems by bypassing the PXE boot (TFTP is insecure)

[pierre.briec]

Thanks Simon for the clarification.

Regarding WADS, how does it work on the secondary repository? I've enabled WADS replication on the secondary repository,
but I can't boot from it. Does it only work with a secondary repository running on Linux? Mine is on Windows.

Thanks,
Pierre

[sfonteneau]

You need to install https://wapt.tranquil.it/store/fr/tis-remote-repo-tftp

to have a TFTP server on the secondary repository.

Therefore, in DHCP, Nextserver will be the secondary repository.

(But if you use WAD's Dangerous Package, this isn't necessary.)