Posts made by Wayne Workman

First thought, figure out how to make the FOG Server return the storage node you want.

Take a look at this function:

https://github.com/FOGProject/fogproject/blob/24bb5a62698b9ba5bd4d80296be8615105c9a810/packages/web/lib/fog/storagegroup.class.php#L237

I think if you can figure out how to pass in an IP address (and maybe subnet mask) to this, you can add logic to select the storage node you want.

The hard part will be figuring out how to pass in the IP address / subnet mask all the way from the unregistered host to the FOG Server and into this function. The easy part is adding a bunch of logic in here to return the node you want.

This link below is for USB devices, but it shows how the request is made and parameters are passed back. You could modify this to pass your IP, subnet, and whatever else to the fog server:

https://github.com/FOGProject/fos/blob/c0238723ce381b5cd0340932086b10d47e79e26b/Buildroot/board/FOG/FOS/rootfs_overlay/bin/fog#L10C40-L10C88

Notice that it writes to this file: /tmp/hinfo.txt

You would add lines somewhere in here to get the IP / subnets from the request that the host makes:

https://github.com/FOGProject/fogproject/blob/24bb5a62698b9ba5bd4d80296be8615105c9a810/packages/web/service/hostinfo.php#L164

And you would pass that IP / subnet information into that optimal storage node function here somewhere:

https://github.com/FOGProject/fogproject/blob/24bb5a62698b9ba5bd4d80296be8615105c9a810/packages/web/service/hostinfo.php#L88

Second thought, hack the storage node selection into a custom FOS build

Checkout this spot, it may have potential:

https://github.com/FOGProject/fos/blob/c0238723ce381b5cd0340932086b10d47e79e26b/Buildroot/board/FOG/FOS/rootfs_overlay/bin/fog.checkin#L81

Another thought here is to look at how the Capone plugin sets this stuff. The script is called here:

https://github.com/FOGProject/fos/blob/c0238723ce381b5cd0340932086b10d47e79e26b/Buildroot/board/FOG/FOS/rootfs_overlay/bin/fog#L60

And this is the file that gets executed, you see it sets a storage node IP, among other things:
https://github.com/FOGProject/fos/blob/c0238723ce381b5cd0340932086b10d47e79e26b/Buildroot/board/FOG/FOS/rootfs_overlay/bin/fog.capone#L108

Third thought, postinit scripts
The method @george1421 suggested seems promising, but I am unsure how the postinit script would make changes to environment variables that will persist after the postinit script ends. If you could solve that somehow, this seems like the easy path.

How would you update FOG without ssh? Are you using the terminal via a hypervisor? Are you plugging a monitor, keyboard, and mouse into a physical server?

Also if you needed to fix something, very likely all the help you would find in the forums will involve some kind of shell commands.

Hi, this is an old problem people continue to walk into. The problem is people upgrade their OS, and then the fog installer fails.

While some people have had success with this, I need more fingers and toes than I currently have to count those who’ve had issues with this approach.

The most safe and sure way to move to a newer operating system is to build a new fog server using that new operating system, and then migrate to it.

I’ve put a lot of time and effort creating an article on how to do this, I believe all the steps should still be valid. It is here:
https://wiki.fogproject.org/wiki/index.php?title=Migrate_FOG

It’s possible you can resolve your issue - but this isn’t guaranteed. It’s also possible that you resolve this one issue, only to immediately face yet another issue. I would advise migrating to a completely new server because this is the safe and sure pathway. I can also tell you that 22.04 daily clean installation tests are passing, meaning that you’d have good results with a clean install on 22.04 (results in my signature).

I would recommend dnsmasq. Here’s a good simple tutorial. https://stevessmarthomeguide.com/home-network-dns-dnsmasq/

@icemannz I’m guessing the disk uses LVM. Fog doesn’t support LVM. If you create the partitions without LVM, it should work.

I know this is an old thread, but we now have metrics on what kernels are being used out in the wild. It’s the external reporting page. Link in my signature. This should let us know if it’s worth it (or not) to find all those old commits and tag them.

There’s a wiki article that walks you through migration:
https://wiki.fogproject.org/wiki/index.php?title=Migrate_FOG

@tag said in Setting up FOG in multi-location environment:

Is it even possible to do it this way?

What you’ve tried is what I was going to suggest. Having a storage group per site, each setup as a master storage node. Do you have any error messages?

Fedora 37 has been added to the daily installation tests. Link to the results dashboard is in my signature.

Fedora 35 has been removed.

Rocky 9 is delayed, as their AMI is not available in us-east-1 Virginia. I’ve emailed them about the issue, they are looking into it.

@flareimp There’s other options as well. You could do either of the below.

The below script is a one-use script that someone could run manually. After updating the IP via the OS configuration, you can run this script that will update all the FOG IP bits for you.
https://github.com/FOGProject/fog-community-scripts/tree/master/updateIP

This next script below will continuously update FOG’s IP settings to match the local interface IP address. You could package this with the fog server image you have so everything just works out-of-box.
https://github.com/FOGProject/fog-community-scripts/tree/master/MakeFogMobile

fwiw, there is a script that updates FOG’s IP.
https://github.com/FOGProject/fog-community-scripts/tree/master/updateIP

this will re-write your DHCP config on your fog server too. Should be perfect for this use case.

I opened a GitHub issue for the DHCP thing: https://github.com/FOGProject/fogproject/issues/510

Are you using the location plugin? If not, that could explain a lot, as FOG will image from whatever storage node with open slots rather than a specific one in the same location as the host.

@danboid For the renaming problem, we need to see a fog client log file. Should be on the root of the C drive. Please include enough of the file, a single line usually is not helpful.

@fog_newb dev-branch does work with Ubuntu 22.04, but you’re doing OS upgrades, not a fresh installation. So that’s hit and miss (usually a miss). Luckily you are using snapshots and can revert.

I advise you migrate, rather than upgrade existing OS. Here’s a guide to do it: https://wiki.fogproject.org/wiki/index.php?title=Migrate_FOG

In this migration process, it’s OK to go to a different OS type altogether. Like Debian or Alma, for example.

Fixed. Ubuntu 22 is now really Ubuntu 22.
https://github.com/FOGProject/fogproject-aws-devops/commit/685df98250938f94b3e099df5d72f609102811fc

ah geeze, I will look into it.

After you get all the steps documented @Sebastian-Roth I can try to create a Jenkins pipeline file that does all this stuff, and add it to the right repo via pull request. Try to automate some of this stuff. We can probably have a Jenkins server in our aws account where we can do builds.