Fog PXE boot multiple sites issue



  • Please know that first of all I am not very well versed in Linux. I have gotten my fog server ( Trunk version 4557 on Ubuntu 14.04 LTS ) up and working on the main site and I am able to upload and image systems fine. I then setup my Storage Nodes on a remote site and they are able to retrieive the images fine from the main fog server. However I am unable to boot a PC into PXE and get a menu. I am not sure what I am to do from here. Also if I was to decide to put FOG on its own VLAN would that be very complicated? right now we do not do a lot of imaging so dont know that it would be a big deal if we keep it on the default. Thanks in advance for your help.

    Main Site
    DHCP Server 10.5.1.11
    Fog Server 10.5.1.16
    Option 066 10.5.1.16
    Option 067 undionly.kpxe

    Remote Site
    DHCP Server 10.6.1.11
    Fog Storage Node 10.6.1.16

    Option 066 10.5.1.16 (Not sure what this should be I have tried both and cannot get it to boot either way).
    Option 067 undionly.kpxe
    I have setup options 66



  • Awesome Please let us know. Have a great vacation!!



  • @Wayne-Workman said:

    @Wayne-Workman said:

    I’m going to quote one of @Tom-Elliott 's old posts:

    Why not use the Location Plugin to do the transfers for you?
    Heck, if you update to the Development versions, you don’t even have to setup rsync tunnels.
    You can install the Nodes how you see fit. I’d recommend, for your case, to install all the servers as “Full Servers”, and then once the installation is complete edit the /opt/fog/.fogsettings file to use: snmysqluser=‘fogstorage’ snmysqlpass=‘fogstoragepasswordfromfogsettings’ snmysqlhost=‘IP.OF.Main.Server’
    This way, all the fog servers at all of the buildings communicate to a single server.
    Then you create your storage nodes based on the information of the other fog servers.
    Create the appropriate groups as necessary.
    Assign the images to the groups you want the images to “cross” between.
    That way you have a centrally managed server, with pxe boot setup locally at each building.
    The location plugin will attach to the hosts that belong at that particular building.

    Please give us details on your experience or thoughts, and please feel free to ask questions. We are here to help.

    Just reposting this - because this configuration would prevent the “missing images” problem you had. ONE DATABASE TO RULE THEM ALL!!! :-D

    Wayne,

    I will look into this part some more when I get back. I think that I did most of it but after rereading it I still need to create the groups. I will try that let you know how it goes.



  • @EAHarvey Hey thanks for pointing out the obvious. LOL dont know how I missed that. Yeah I need to look into the speed issue more. I will be on vacation all of next week so will try to get to in the next 2 weeks when I get back.



  • @Obsidian Any update on the Slow speed issue?


  • Moderator

    ALSO, Google is pretty awesome, if you guys haven’t noticed… :-D

    Screenshot from 2015-09-10 19-13-54.png


  • Moderator

    @Wayne-Workman said:

    I’m going to quote one of @Tom-Elliott 's old posts:

    Why not use the Location Plugin to do the transfers for you?
    Heck, if you update to the Development versions, you don’t even have to setup rsync tunnels.
    You can install the Nodes how you see fit. I’d recommend, for your case, to install all the servers as “Full Servers”, and then once the installation is complete edit the /opt/fog/.fogsettings file to use: snmysqluser=‘fogstorage’ snmysqlpass=‘fogstoragepasswordfromfogsettings’ snmysqlhost=‘IP.OF.Main.Server’
    This way, all the fog servers at all of the buildings communicate to a single server.
    Then you create your storage nodes based on the information of the other fog servers.
    Create the appropriate groups as necessary.
    Assign the images to the groups you want the images to “cross” between.
    That way you have a centrally managed server, with pxe boot setup locally at each building.
    The location plugin will attach to the hosts that belong at that particular building.

    Please give us details on your experience or thoughts, and please feel free to ask questions. We are here to help.

    Just reposting this - because this configuration would prevent the “missing images” problem you had. ONE DATABASE TO RULE THEM ALL!!! :-D



  • Change your rate to MB/Minute in the Drop down list and results to hours. I’m still thinking it’s throttling or either this is a RAW data image?

    Screenshot from 2015-09-10 15:02:50.png



  • Harvey,

    No worries, thanks for your feedback. I was looking at some calculators since doing math in my head is not my strong point. LOL and a couple of them showed me approx 30 minutes and normally have always had images take about 30 mins in the past. This all looks correct to me but maybe I missed something.

    image time.JPG



  • 29 gigs at 130 mb/s should take about 4 hours. I think you may be having a bandwidth issue. Should be running at gig/min not mb/m.

    Just my first observation. My math right? :-)

    28 gigs is 28,672 MBs

    at 130 MBs per minute that should be 220 minutes.

    220 / 60 is 3.6 hours.

    Not trying to be a jerk, just trying to type it out of my crazy head. lol



  • Not sure if I should post this with this topic or create a new one, if I need to create a new one just let me know. Hhowever I have been imaging the system (that I mentioned earlier in this post) and it has been imaging for over 3 hours now. The image is aprox 29GB and it has been transferring at aprox 130MB/Min it is plugged into the same switch as the imaging machine and by all calculations this should have been done in aprox 30 mins. Any thoughts or suggestions on why it is taking so long?

    slow image2.jpg



  • Thanks Tom, I was thinking that it would for some reason, I went and added my image and now am imaging a system.


  • Senior Developer

    Wait, what?

    The second system is built as a server? FOG Doesn’t autopopulate the images stuff. that’s done by you.



  • Wayne,

    Site 1 is Ubuntu 14.04 Server & Fog Trunk 4557 & Site 2 is Ubuntu 14.04 Desktop on fog trunk 4580.

    But now i have a new issue. The images have replicated and I can see them in the images folder on Site 2 however when I try to image a computer there are no images listed in fog. I have attatched screenshots of fog to show them not being listed and I was able to do an ftp to the system and list them in the directory.

    images ftp.JPG

    missing images fog.JPG


  • Moderator

    @Obsidian said:

    @Wayne-Workman That makes sense, I believe i have that written down since I redid this system and will update it with that. A couple of other questions.

    Do you know with this type of setup can I upload an image at any site and it be replicated at all sites? and why the log viewer on site 2 is not showing anything?

    The master node of a group should replicate to all other nodes in its group.
    For uploading -
    Say you create an image (or have an image already) that is set to Storage Group 1. Say that Storage Group 1 has a master node.

    When that image uploads - no matter where it uploads from - the upload will be captured on the master node - and after that is complete - the image then replicates to other nodes in the group.

    And for site 2’s log problems, it’s probably credentials related. is site 2 using the same version of FOG? what OS is site 2 running?



  • @Wayne-Workman That makes sense, I believe i have that written down since I redid this system and will update it with that. A couple of other questions.

    Do you know with this type of setup can I upload an image at any site and it be replicated at all sites? and why the log viewer on site 2 is not showing anything?


  • Moderator

    @Obsidian One slip-up on your part, and your entire system is compromised… because all passwords match, and they all provide root access.


  • Moderator

    @Obsidian said:

    @Wayne-Workman It has the user name and password of the Root user account for linux

    So you know, the username and password set for each of your storage nodes - these are the FTP credentials to be used with that storage node.

    the installfog.sh installer creates a “fog” user account locally on the system automatically for you, and this account is password protected. This is also the account that is used for FTP and MySQL access. The installer - if it completes the installation - generates /opt/fog/.fogsettings and fills in those two fields I mentioned before with the username and the randomly generated password for that account. This way - when you upgrade in the future, the installer will setup shop using the correct settings.

    For instance, my setup is using the local linux account called “fog” and a custom password I set on that account. I have this username and password set on my storage node and in my .fogsettings file.

    There are many sets of credentials used with the entire package that we call “FOG”, and this is to allow you to modularize easily, to protect passwords to separate systems better, to separate low level access and root access, to lock down your system better. To give YOU - the administrator of your fog set up - absolute power over all pieces of FOG.

    And, while using your root username and password will work obviously, I would not advise setting it up in this method.



  • @Wayne-Workman It has the user name and password of the Root user account for linux


  • Moderator

    @Obsidian What is set in all your storage node’s username and password fields? Anything?


Log in to reply
 

429
Online

39.3k
Users

11.0k
Topics

104.6k
Posts

Looks like your connection to FOG Project was lost, please wait while we try to reconnect.