Hi There,

We have an interesting case where we almost entirely use ipmitool and sol activate to boot servers and pxe boot them, we currently use a pxe server contained in a docker container, but I’ve used fog previously and would like to try using it again, I think it might best fit our needs. But would need to make sure this fog menu would display on serial over lan (SOL) connections.

Hi There,
Trying to create an automated deployment of fog, and want to be able to do an api call to create our ipxe menu items, as we generally don’t use static images anymore, but most is from an ipxe menu, loading the iso, and autoinstalling. Which all of this we do from the ipxe menu. So I’m looking for how I could push these menu options out with an api call, if there is one.

Thanks

@george1421 Oddly enough, ALT-F1 - ALT-F4 is doing nothing, so I can’t switch to tty.

@george1421 Yes, same screen as above.

@george1421 I just updated and it looks like it’s a little better (it shows the kernel loading page, whereas before it went straight to starting syslogd"
But after the kernel loads it moves to the black screen, starting syslogd, etc… Then starting eno1, eno2, etc until it finds the active interface.

@george1421 Probably a stupid question, but will this need done on all of the servers(storage nodes) I’m assuming yes, just S instead of N.

@george1421 Oh really, interesting…

Yeah, I’m on the latest known release. What does the upgrade path look like for that? This is a brand new fog build, migrating from an existing host into a new location, but this behavior is the same on both old/new.

This from what I can tell is only affecting one of our models of systems we are pxe booting.

Supermicro
PXE Boots via UEFI, Boot to the fog menu, click deploy image, enter user/password and then I get the following screen after some time instead of being presented with the image selector screen

Has anyone seen this happen before? If I switch to legacy, it does get to the menu fine.

Thanks.

@george1421

1. No not every machine - Only the machines we have registered in FOG that we associate this “image”(ipxe menu item) to. Just like you can do currently with Associating an image to a host
2. Yes, all will be registered in FOG. Would like to do this with an API call.
3. There will be many, yesterday there were 20 done.
4. Yes, although I haven’t personally used php in years myself and other people on my team can do this. I started looking at the source code last night, but not too deep yet.
5. Motivated enough to make it work so we don’t have to adopt something else, since this primarily works for our other needs.

Is it possible to associate an iPXE menu item to a host like you can associate an image to a host?

Scenario:

I have multiple machines that all need the same image but I am not using static captured images I am using ipxe menus to boot an iso and run an automated installer from ubuntu, so there is zero interaction. Currently the only interaction is plugging in the machine and booting it to fog, selecting the menu item and letting it go.

I’d love to be able to associate mac addresses to a certain option so once it hits the fog menu it selects it and then runs in the installer. Does anyone have any idea how to make this a possibility?

Thanks!