Perhaps a custom iPXE menu entry to do what it is you’re asking?

@Wayne-Workman said:

I would suggest we pool our knowledge to just create some base-level scripts that will sync two DBs based on the exact same rules that the FOGImageReplicator follows. I’ve outlined these rules before in other threads.

I’m not thinking anything drastic. Its more like how pfsense sends http calls to a remote node to sync its configuration data. While its a bit deeper discussion that we should do here. The idea would be for the FOGReplicator to move the files as they do today. When all of the files in the current image directory have been moved, then make a http call to a php page the remote node (it should already know everything it needs to know to do this [i.e. no new database fields]) which adds the image information to the remote database.

I think that’s a good idea.

I think anything that includes a way of killing existing FTP instances is dangerous…

lftp is not only used for imaging, it’s used for transferring uploaded images from /images/dev to /images, it is what reports how much disk space is being used on the server, the size of images, deleting images (which takes a long time on Ext3), downloading the kernel and init…

I could just imagine some poor tech coming in to work early to update FOG and… right at the end of the installer when the new kernel and init is being downloaded, a cron event fires off and destroys the FTP transfer… and the poor technician has no idea it even happened…

You’d have to schedule this way way outside of operating hours; having it run AT the start time of the day is dangerous, having it run AT the exact end of the day is dangerous.

You might try time-based bandwidth shaping to slow down the fot-to-fog transfers over your WAN, you might get a much more stable and reliable method of controlling it that way.

For future readers, there is a post in this thread that details how to do this for the legacy client: https://forums.fogproject.org/topic/5996/svn-4972-to-svn-5046-server-load

I believe that for the new client, it is able to auto-adjust when the checkin time changes.

@Wayne-Workman

This would be nice!

Hi Wayne & Frank,

I have read extensively through all the information I could get at the time I investigated that (like 2 years ago), we have macminis, 2011 & 2012. And I never could get them to properly boot on the network, so what I did was to live boot a Ubuntu image on the mac, and “fog” myself (well, that is why I helped have partclone replace partimage in fog, because partimage couldn’t handle hfs).

Now I see you updated the wiki from what I remembered, as I was doing all that in the “pre ipxe” era. So I might give it a try next week… Thanks for the updates, I’ll let you know if that helps.

Cheers,
Gilles

@ch3i Yes, I meant having widgets on the dashboard.

@Jbob I see, thanks for the answer. 🙂

It already does this.

@sudburr Hi, not sure but I think it’s for FOG 2.0 : core installation and plugins to add dhcp, …

What you are requesting basically exists already but not in the way you’re requesting.

The proper way to handle this is to insert the host or fully/quick register with the USB Nic as the MAC address, whether primary or not. After These have been added you would then set the Mac to be ignored for the client. Only the client should be ignored because you most likely want these nics to be the Nic that the host images with. Ignore imaging is to ignore those macs as a potential imaging interface. What should happen is the host images. After that, assuming you’re using the new client, the host will check in via the client and should attempt to self register. Of course, it would make more sense to ensure the hosts are named the proper name you want them to be already in the database, otherwise you would end up with multiple hosts registered to the name of the client that uploaded the image.

@bharlow

In FOG Trunk, you can network boot a registered OR unregistered host - choose “Quick Image” from the boot menu - and then select the image you’d like to use.

If you’d look at the fog cloud on the FOG web console’s login page (or any page), in the cloud it says what version you’re using. This is what it looks like:
FOG_Revision_in_cloud.png

What do you see in the cloud on your login page?

One of my co-workers who likes fog alot also finds the snapin association process overly long @tdepczynski

I would also like to point out the potential issues of a single MACaddress getting registered on multiple systems. that alone is a big reason to not auto-approve of all pending MACs. duplicate MACs can happen when a virtual network device is installed on an image, like with virtualbox, or you have plugged a usb NIC into multiple machines.

@Tom-Elliott Maybe I had it backwards… now that I am thinking about it - I believe I had snapins waiting and couldn’t deploy an imaging task…

My bad.

This has been added. You can delete tasks from the db after searching. Active tasks will be cancelled. Nice part is the checkboxes remain in their checked state even on subsequent updates. If you cancel it will first prompt. Hopefully this helps.