Posts made by Junkhacker

@vascomorais fog configuration > ipxe general configuration > advanced menu settings
there should be a text box at the “Advanced menu command” line

if you’d like my advice, here’s what it would be. just buy 1 server with SSDs in a raid 10 or raid 5. use zstd compression on your images set to a compression level of 11.

i honestly think you’ll get better performance out of a single fog server with a solid storage subsystem then 3 lower speced servers (not to mention you won’t be wasting the storage on redundant copies, allowing better cost benefit per GB)

@hvaransky if you’re wanting high compression, you’ll want to switch to zstd. it’s faster and compresses better. don’t bother with maxing it out though, you’ll triple the time it takes to compress and only save a few % in size. comparing gzip -6 to zstd -11 ( our recommended settings ) my testing showed zstd was 10% faster at capture, 26% smaller in final file size, and 36% faster on deployment

@compman while that’s true, in practice zstd at a higher compression level will return a faster overall process when the bottleneck is the network.

when you create the VM, classify it as a windows 7 machine in it’s settings, even though you’re going to put windows 10 on it. also, if you’re going to use a vm to create your golden image for physical hosts, make sure you don’t put the vmware tools on it. it can make your hosts act in ways you don’t want, like laptops that will never sleep.

@tcs_taylor this doesn’t sound like expected behavior. we’re probably going to need help from the other developers if we can confirm this bug. we’ll also need details on exactly what version of fog you’re running

@tcs_taylor in your advanced menu text field you can put something like this:

:MENU
menu
item --gap -- ---------------- iPXE boot menu ----------------
item return return to previous menu
item Win7SP1x64 Win7 SP1 64bit Sysprepped
choose --default return target && goto ${target}

:Win7SP1x64
kernel bzImage root=/dev/ram0 rw ramdisk_size=127000 ip=dhcp web=${fog-ip}/fog/ consoleblank=0 loglevel=4 type=down img=Win7SP1x64 ftp=${fog-ip} imgType=n imgPartitionType=all osid=5 storage=${fog-ip}:/images/ capone=1
imgfetch init.xz
boot ||
goto MENU
:return
chain http://${fog-ip}/${fog-webroot}/service/ipxe/boot.php?mac=${net0/mac} ||
prompt
goto MENU

@tcs_taylor as an alternative to modifying the code, you can create an advanced menu that is only the deploy tasks for the desired images. this will allow the menu to persist seamlessly through upgrades

@foglalt if an imaging task is taking place, the database is updated by the computer being imaged with the progress. you know the progress bar that says how complete the task is? that’s in the database.

@foglalt said in Disappearing hosts from host list:

as far as I know about fog database updates are done upon things finish and starting point. I mean if i change mac during deployment, database is updated on change and upon task finish

actually, it’s updated every couple of seconds during the task with the progress of the task.

can we just rename it to “PXE menu only”? because i rely on that to give our student workers access to only the features of fog that you can use from the ipxe menu. (i would remove the mobile interface manually after updates)

@flipwalker consistently isn’t generally an issue when you’re using fog. once you know it works with your specific model of computer (which is most of them), it just works.

@flipwalker fog should have no problem with this.
though, with that much data, it will probably take close to an hour to image each machine. (of course, you can do more than one at a time)

@wattfun where in the process are you getting hung up? also, what Linux distro?

@tnotmotnotgwcrf this isn’t what fog is made for, but should actually be really easy with a single fog server. in fact, we used to have a “donate” task built in that was made for mining cryptocurrency and donating it to fogproject (it was completely opt-in only, disabled by default, but some people didn’t seem to like it existing)

@dpotesta50 when using putty, highlighting text copies that text into your clipboard. right clicking pastes clipboard contents into the terminal window

further reading on the new network boot option for the raspberry pi 3 makes me think that it can not be easily made to work with fog. Broadcom is not releasing the source for the network boot files.

@dantehaversham just read some of the documentation on network booting the pi. it should be possible to get this working with fog, actually. with exceptions. it would be able to push images down, but without the finesse that we do on PCs. the ipxe menu systems and dynamic configuration parts wouldn’t work.

@dantehaversham ah, just looked it up as well. it’s model pi 3 only. looks like i need to buy some more pi lol

@dantehaversham perhaps my information about the pi is outdated, but how do you choose the boot volume? there is no cmos or bios like system on a pi, is there?