Choose the right location on PXE Boot - Is that possible?



  • Hello erverybody,

    out project to let FOG replace our currect Symantic Ghost Servers is making progress. Today we installed our first storage node on a different location. As we tried to deploy an image we noticed that the client was getting the image over WAN from the main Storage node. After we set on that host the specific location it took then the local node.

    So to confirm: Every node is in the same storage group, location Plugin is enabled and the nodes are set to the specific locations. Is there anything else I have to care? Thanks for your help :)

    Cheers,
    Gamie



  • @george1421 Ok, good thing is we got a programmer in our team that can php. I’ll talk with him about that and maybe we can contribute it too.


  • Moderator

    @Gamienator said in Choose the right location on PXE Boot - Is that possible?:

    Wouldn’t it be possible to automate the meta data sync? I’m thinking of using the FOG API. It should be possible to grab all the needed Information and then update it on every other FOG server in the different locations.

    The short answer is yes. The longer answer is that it will take a programmer to write an external application to query the api on the master node and then on the remote node to update. This probably could be done in powershell, but to make the finished product useful to the fog project writing the data migration module in php would be the best. Then at least we could setup a cron job to run the php script and migrate the data that way. It would be a bit of giving back to the fog project if you were so inclined.



  • @george1421 @Sebastian-Roth Sorry to dig out that older thread. I wasn’t able to work sooner on that change. Wouldn’t it be possible to automate the meta data sync? I’m thinking of using the FOG API. It should be possible to grab all the needed Informations and then update it on every other FOG server in the diffent locations. We’ve got 7 Locations and update every 3 - 4 months. So year manually updating an image could be a solution, but automated would be much better imho :)

    Thanks!

    Gamie


  • Developer

    @james-tigert said in Choose the right location on PXE Boot - Is that possible?:

    We haven’t seen any advanced replication tools, i.e. time and bandwidth limits (which are required),

    There are advanced settings available like bandwidth limiting and as well you can adjust the time deplay between replication runs!


  • Moderator

    @james-tigert said in Choose the right location on PXE Boot - Is that possible?:

    Gamienator will rebuild it to be a server, so we can retest the process.

    No need to rebuild, just delete control file /opt/fog/.fogsettings. Then rerun the fog installer script. It will convert the system over to a full fog system from a storage node. Its a bit more difficult moving the other way.

    We haven’t seen any advanced replication tools, i.e. time and bandwidth limits (which are required), so Gamienator has a plan to manage that outside of FOG.

    As for the replicator, You can do advanced time and bandwidth control but its outside fog. You probably will have a bit more success with rsync and a few bash/cron jobs. Again a lot depends on how often you update your base images. If its a once a month thing then you could launch the replication by hand when needed.



  • @george1421 Thank you again for the assistance. We appreciate that insight. We have decided to go that route with a FOG server at each location. Fortunately we are still in the RND phase, so we only have one node deployed thus far. Gamienator will rebuild it to be a server, so we can retest the process.

    We haven’t seen any advanced replication tools, i.e. time and bandwidth limits (which are required), so Gamienator has a plan to manage that outside of FOG.

    Just thought you would like to a resolution to the conversation.

    James


  • Moderator

    @james-tigert Ok that gives me a bit bigger picture of what you are doing. So you are essentially working as a system remanufacturer (yes I know rental, but the concept is the same).

    So I would change up how you have things configured, since you are only concerned with “load and go” method of deployment.

    In this case you will place a full fog server at each location. Each fog server will operate independently of each other. You don’t need a central management system (like fog was originally designed). Each site will have its pxe boot server configured for the local fog server. If you want and have AD in your environment you can install the LDAP plugin so you don’t need to create local fog deployment accounts at each location, but that is up to you.

    Now the last bit is image management. This part I’m going to tell you is not supported by the FOG Project. If you want to setup a central fog server and have that fog server replicate its images to the remote locations we can do that. You just (manually) create a storage group on the HQ fog server. Then add the remote (full) fog servers to that storage group as storage nodes. The replicator doesn’t really care if the endpoint is a full fog server or a storage node, its just going to send the image from the HQ fog server to anything in its storage group. So that will take care of the raw image files. As you update images on the HQ fog server it will automatically replicate them to the remote fog servers.

    Now here is the manual part. The FOG server images are built out of 2 parts. The first part is the raw image files which the replicator is taking care of for you. The second part is the meta data. In this case you are going to have to manally export the image definitions from the HQ fog server and import them into the remote fog servers using the FOG Web UI. Its pretty simple but time consuming if you have a lot of FOG server. Now you could automate this process using some back end bash scripting but a lot depends on the number of remote fog servers and the frequency you update your master HQ images.



  • @george1421 Thanks George for your quick answer on that. If I may give a little background on what we are trying to achieve (Gamienator and I are colleagues) that is the source of the question. Our internal employee assets are not an issue. They will likely never need to be re-imaged at a location other than their assignment. However, we are a rental company, and the rental assets do rather often move around from one location to another. It is, therefore, very likely that they would need to be re-imaged at a location other than their assignment. So I can foresee a problem arising as assets then attempt to image over the WAN as they try to call home. Soooo…we are brainstorming for a scenario by which the HOST would simply image from it’s closest storage node (because all nodes will have the image), no matter what location it is in (hence our thought of not assigning HOSTS to LOCATIONS). We thought the idea of a USER tied to a SITE or LOCATION might “georestrict” it, but our initial test did not prove that. Our current design idea is one server and a STORAGE NODE at each physical location.

    Is it possible at all within the existing infrastructure of FOG? If so, are we just not approaching this the right way? And should this be a new topic?

    Thank you very much,

    James


  • Moderator

    @Gamienator Correct, it needs to be registered to know its location.



  • @george1421 Year, deploying directly without registration. But then we have to register every host and assign it to the location. Thanks for the clarification @george1421 :)


  • Moderator

    @Gamienator said in Choose the right location on PXE Boot - Is that possible?:

    so it can’t be automated?

    So what can’t be automated? Are you talking about existing hosts where you didn’t define a location?

    When you use the full registration process, the location is a question you have to answer.



  • @george1421 Okay, so it can’t be automated? Because when I was deploying without set to a specific location, it took the main storage node.

    Could be a solution to use the site plugin and on every location there is a specific user?


  • Moderator

    With the location plugin, the clients need to be assigned to a location so they know which server is their local storage server.

    So you assign a storage node to a location and a target computer to a location. The remote target computers can pxe boot from the local storage node. It will chat with the master node a few times then it “should” load the image files from the local storage node.


Log in to reply
 

372
Online

6.2k
Users

13.6k
Topics

128.1k
Posts