[Requested] Multi-Site Location Patch [Requested]

  • Developer

    Option 3 is how i have our infastructure setup. we have 55 sites, alot of those are branch sites and only have VPN links, We have the FOG Server on a VM on our server scope, a Master Node in the “Build Area”, which has it’s own 1GB switch/scope so uploading and downloading images,snapins etc is quick, and another Master Node at our failover site and rsync and crontab syncs down the changes to the relevant sites, dependant how they’re routed (Main Office - Branch Site). Works extremely quick, Build Area Gets 4-5GB/Min Deployment and the others are 1.4-1.5GB/Min… All data is transferring on site, Images, snap-ins, tftpboot etc… the only traffic going across the VPN is reporting to and from to the FOG Server to kick off the image etc…


  • [I]Who has the most sites here? anyone managed more than 5 FOG Sites? how do you do it?[/I]

    How could we make FOG a real Multi Site solution

    Would there be a way to implement a sweet Multi Site setup with DNS with site specific A Records

    As what happens when a particular Laptop roams between sites, would it not try and connect to an incorrect storage node?

    Could something like this work

    OPTION (1)

    [QUOTE]
    SITE 1 (MAIN SITE)

    [INDENT=1]FOG-SERVER-1-1[/INDENT]
    [INDENT=1]FOG-NODE-1-1[/INDENT]
    [INDENT=1]FOG-NODE-1-2[/INDENT]

    SITE 2

    [INDENT=1]FOG-SERVER-2-1 (PXE Only? or MySQL Replication?)[/INDENT]
    [INDENT=1]FOG-NODE-2-1[/INDENT]
    [INDENT=1] [/INDENT]
    SITE 99

    [INDENT=1]FOG-SERVER-99-1 (PXE Only? or MySQL Replication?)[/INDENT]
    [INDENT=1]FOG-NODE-99-1[/INDENT]

    Then using DNS for each site needs some common A/CNAME records

    [INDENT=1]FOGSERVER - Unique for each site[/INDENT]
    [INDENT=1]FOGSTORAGENODE-1 - Unique for each site[/INDENT]
    [INDENT=1]FOGSTORAGENODE-2 - Unique for each site[/INDENT]
    [/QUOTE]

    OPTION (2)

    [QUOTE]
    SITE 1 (MAIN SITE)

    [INDENT=1]FOG-SERVER-1-1[/INDENT]
    [INDENT=1]FOG-NODE-1-1[/INDENT]
    [INDENT=1]FOG-NODE-1-2[/INDENT]

    SITE 2

    [INDENT=1]FOG-NODE-2-1 (Also has PXE and using RSYNC for tftpboot)[/INDENT]
    [INDENT=1] [/INDENT]
    SITE 99

    [INDENT=1]FOG-NODE-99-1 (Also has PXE and using RSYNC for tftpboot)[/INDENT]

    Then using DNS for each site needs some common A/CNAME records

    [INDENT=1]FOGSERVER - Main Site[/INDENT]
    [INDENT=1]FOGSTORAGENODE-1 - Unique for each site[/INDENT]
    [INDENT=1]FOGSTORAGENODE-2 - Unique for each site[/INDENT]
    [/QUOTE]

    Then no matter which site you are at, you always know it would use the correct Storage Node and Server

    ISSUES

    Option (1)

    [LIST]
    []Has Multiple Databases, how could you keep the databases in sync?
    [LIST]
    [
    ]having local database would surely improve performance vs slow WAN link
    []Would still operate If link between sites is down (just no sync)
    [
    ]Assuming the sites are connected via some form or WAN/LAN/MPLS/VPN etc then some replication is necessary for the Databse
    []MySQL Database Replication? keeping all sites in sync so the agent can contact the server and the relevant jobs are there ready meaning you only need to manage ONE single FOG Web Interface for all sites
    [/LIST]
    [
    ][INDENT=1]RSYNC (or DFS) can be used for the Storage Images and SNAP-INs, and tftpboot folder[/INDENT]
    [/LIST]
    Option (2)

    [LIST]
    []One single database, administration is easier, less to go wrong with database?
    [
    ]slower performance as agents are talking across WAN links to central site?
    [LIST]
    []how much data would (1 or 10 or 500) agents use across a WAN link per day chattering?
    [
    ]SCCM here bogs down an entire network, what about FOG?
    [*]can snap-ins be downloaded from Storage Nodes instead of server
    [/LIST]
    [/LIST]
    Option (3)

    [LIST]
    []Re-think the entire approach
    [LIST]
    [
    ]Use the FOG Server as an SQL Database and Web Interface only no storage
    []Use storage nodes for Images, Snap-Ins, PXE Boot and sync them
    [/LIST]
    [
    ]This way would mean each brach site has a storage node which performs storage of images, snap-ins, tftpboot folder which all syncs using rsync with other storage nodes (controlled by server?)
    [*]the FOG administrator administers one database uploads snapins and images to one and its replicated
    [/LIST]

    Thoughts?


  • Brilliant. Thanks for this. Just out of interest I have been having issues installing a storage node. [I have posted a support question but it has largely been ignored. I can can’t install FOG storage nodes on Ubuntu 10.04 [32 or 64 bit]. Can anybody confirm that it works/doesn’t work and suggest a work around?


  • Please note that Line 34 of service/Pre_stage1.php should read:
    [INDENT=1][PHP]if ( $location != null || $location != -1 )[/PHP][/INDENT]
    It currently reads
    [INDENT=1][PHP]if ( $location == null || $location == -1 )[/PHP][/INDENT]
    This is causing the execution to stop during the location check and say that there is no location set for the PC.
    [edit] only while a location is actually set. I didn’t try it without a location set.

    Stephen.

254
Online

8.4k
Users

15.2k
Topics

142.5k
Posts