I’m trying to understand how the snapins work code wise. I’m wanting to try to implement a location based pull for the fog client much like the multi location patch. But I’m not sure which files are doing what. Can anybody point me in the right direction? I would like to know which php file creates the task to pull the snapin from the fog server so I can maybe add a location if statement so it will pull from a storage node instead of the main fog server.
Posts made by djm79
How do snapins work?
Snap-in deployment from storage node
I have been working on setting up FOG for the company I work for as a replacement for Ghost. I have setup a version 0.31 that is using the [URL=‘http://fogproject.org/forum/threads/requested-multi-site-location-patch-requested.410/’]Mutli-site location patch[/URL]. It seems to be working great as we have 20+ remote locations and a three building main campus. I found that snap-in still pull from the main campus site to the remote locations would it be possible to add the functionality to have the FOG agent pull the snap-in from the local storage like image?
I want to say that all those who have put in their hard earned time and energy into this project Thank You!! This is one of the best IT solutions have ever used and the support and development is top notch.
Multi site Fog deployment
I have some questions on the proper way to configure Fog to work in a multi site setup. We have one main campus that includes three buildings all on the same subnet 10.0.0.0. Then we have 20 branches that are on 192.168.x.x third octet is the branch ID then the fourth being the range of IP’s given out to machnes.
I setup Fog to replace a botched Ghost install that has been running for five years or so and only images machines at the helpdesk. We are mainly a windows shop and DHCP scopes are controlled here at the main campus for all branches. My thoughts after reading the forums on how I can set this up so we can image from a local storage node at each location would be to set them up as TFTP/PXE and point the scope for each location to the local storage node and leave the client on each machine configured to the main Fog server at the main campus. Will this allow us to control the imaging process from the main Fog server while only pushing images and Snap-ins from the local storage node? If there are steps to control the local machines so that they will accept commands from the main server while only pull images from the local node I'm not seeing any but if you guys could point me in the right direction I would be very grateful. Fog is the best free solution I have ran across and you guys kick ass.
Sorry for the wall of text. I try to remember to format it for easy reading next time.
RE: Multi site Fog deployment
Well since your using a flat network you could try this [URL=‘http://fogproject.org/forum/threads/requested-multi-site-location-patch-requested.410/’]multi site patch[/URL]. Lee is the man on this but the downside is you have to .031 for it to work as there are changes to the coding on .032 that keep this from working. So long story short you create locations and tie them to FOG servers with each computer then add the secondary FOG servers to the main FOG server as part of the default storage group and use DHCP to control which FOG server the computers boot from and the location make the computer pull from that machine.
Then you can setup the replication to happen in off hours or throttle it so that the link between the two sites isn’t overloaded. Look this over and hit me up or ask Lee since he made the patch and hes really nice and walked me through getting it hammered out.
RE: Virtualize FOG Server in OpenVZ Container using Proxmox VE 2.1
I have mine running in VMware and it runs great. As for VZ/Proxmox i have not tried this virtual software.
RE: Boot loop on some Dell Optiplex 790 when first boot device is NIC
If you chain load them it should clear up the boot loop. I have a batch of dells that would boot loop on me till I just chain loaded all my FOG computers and now no problems.
RE: Cannot add to Domain.
Yea thats why you need to look in the folder that you used to install fog and there will be a fogcrypt run this on a windows machine from the command prompt and it will output the password encrypted and then input that in your fog settings and test joining.
RE: Network Boot Problems/Computer won't communicate with Ubuntu/FOG
Well if you already have a device doing DHCP you could cause a “race” situation were they are both trying to hand out address. The proxy DHCP setup would allow FOG to hand out the PXE boot options to computers without messing with the DHCP device that is doing it now. Does someone else manage the device handing out addresses? If so ask they to add the boot options to the DHCP scope. IF not then proxy is the way to go.