• Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login
    1. Home
    2. george1421
    3. Topics
    • Profile
    • Following 1
    • Followers 64
    • Topics 113
    • Posts 15,310
    • Best 2,772
    • Controversial 0
    • Groups 2

    Topics created by george1421

    • george1421G

      Can php-fpm make fog web-gui fast

      General Problems
      • • • george1421
      8
      2
      Votes
      8
      Posts
      3.8k
      Views

      george1421G

      @andrewg78 At this time don’t enable memcached, The developers have decided to not add this feature at the moment.

      Actually you should not need to follow any of this post since most of it has already been included in FOG 1.5.2 base configuration and later.

    • george1421G

      Can you make FOG imaging go fast?

      General Problems
      • • • george1421
      7
      0
      Votes
      7
      Posts
      4.9k
      Views

      Wayne WorkmanW

      @george1421 said in Can you make FOG imaging go fast?:

      I can say from my production FOG server running 2 vCPUs on a 24 core vSphere server, I can achieve about 6.2GB/min transfer rates (yes I know this number is a bit misleading since it also include decompression times, but its a relative number that we all can see) for a single unicast image.

      That figure is not network transfer speed or compression/decompression speed nor is it an aggrigate, it is simply write speed to the host’s disk.

      It doesn’t represent or reflect network transfer speed or decompression speeds. These things are very loosely related to the write speed just as the disk you’re using is related to the write speed - but this figure does not tell where any bottleneck is.

      Trying to use this figure to gauge network transfer speed would be like trying to gauge the mail man’s speed based on how long it takes me to go check my mailbox (if the post office used that as their metric, the mailman would be fired because I check my mail every few days).

      Further, your bottleneck is probably not the next person’s bottleneck. My experience with multiple FOG servers on multiple types of hardware has shown that tuning FOG is a matter of balancing network throughput with a host’s ability to decompress. We cannot speed up how fast a host’s disk can write, it’s maximum write speed is still it’s maximum write speed no matter what we do with CPU or Network or Compression or RAM - the idea is simply to always have data waiting to be written to disk without delay, and how to balance the CPU’s ability to decompress with the network’s ability to transmit to many clients at once, and the FOG server’s ability to serve many clients at once. This all comes back to two simple things I think: Max Clients and compression rate.

      It’s a balancing act of these two things. Of course, ZSTD is the most superior compression algorithm, which is why it’s not one of the two simple things. But it’s compression rate is.

      The FOG Server’s disk does play a role - but at my last job, I was clearly hitting the network’s maximum throughput bottleneck - so a solid state disk would not have helped.

      At any rate, the script below is an example of how to automate the monitoring & collecting of things from FOS: https://github.com/FOGProject/fog-community-scripts/blob/master/fogAutomatedTesting/postinit.sh
      That’s what I’d use to collect any custom metrics you want to monitor more quickly, instead of doing a debug every time and manually monitoring.

    • george1421G

      Adding additional image storage space to FOG server

      Tutorials
      • • • george1421
      3
      2
      Votes
      3
      Posts
      11.6k
      Views

      george1421G

      Part 2 FOG WebGui Configuration

      We need to create a new Storage Group. Go to Storage->Add Storage Group Enter a new Storage Group Name and Description Press Save/Update to create this new Storage Group.
      0_1500031509623_istore_group.png Note that now we have 2 storage groups (default and ImageStoreGroup2)
      0_1499989908064_new_storage_group.png Now we need to add a new Storage Node. Go to Storage->Add Storage Node.
      Enter the values in the storage node configuration appropriate for your setup. The key values to watch are the IP Address (fog server IP address), Is Master Node, Storage Group, Image and FTP Path. The rest can remain the defaults. Its worth noting that the Management Username and Management Password are related to the FOG server where we just mounted to the new hard drive. If you don’t know what these values should be you can always inspect the default storage node settings. Just copy and paste them from the default storage node configuration to this new storage node configuration.
      0_1500032048809_istore_node_p1.png
      0_1500032067873_istore_node_p2.png In the All Storage Nodes list note that the storage node ImageStore2 is attached to the ImageStoreGroup2 and that it is a Master Node in that storage group. This is important since only master nodes in a storage group can capture files.
      0_1500032405739_istore_nodes.png Now we will setup an image definition to store images to this new storage group. Goto Image Management->Create New Image. Enter the Image Name and select ImageStoreGroup2 for the Storage Group. Fill in the remaining fields as you would normally for the image.
      0_1500032769977_new_image1.png Update your host to use this new image definition.
      0_1500033275647_host_def1.png At this point we can schedule an image capture for this host. Go ahead an schedule a capture task for this host. Below is a screen shot of the capture task as its running. The key thing to note here is that the Working with node points to our node definition that is pointing to /images2 directory. (Wh00t!!)
      0_1500032982805_active_task1.png You can also confirm that the image is being saved to the /images2 directory by monitoring the partclone display.
      0_1499990078263_partclone1.png We are done.

      As you can see from this tutorial, its possible to add a second hard drive to your FOG server to add additional storage space by simply creating a loop back storage node definition. There are a number of steps involved with setting this up, so take it slow and follow each step exactly.

    • george1421G

      Solved Storage Node: No open slots, there are 0 before me

      Bug Reports
      • • • george1421
      6
      0
      Votes
      6
      Posts
      3.1k
      Views

      george1421G

      @Tom-Elliott The error continues to persist even after the update

      The conditions are the master node is set to disabled in a storage group. When you attempt to deploy an image the deploy task get created and the above error is thrown and the page never refreshes only times out. If you pick another menu item them that page is painted.

      Should the master know ever be disabled in a storage group? (probably not)
      Would this ever happen in the wild?? (probably not)
      Does it needs to be fixed ?? (only the developers will know that)

    • george1421G

      Error capturing to a subfolder

      General
      • • • george1421
      4
      0
      Votes
      4
      Posts
      1.3k
      Views

      george1421G

      @Tom-Elliott Yeah I got that on the mounting.

      /images/vol1 (which points to a directory on /dev/sda1) images correctly.
      /images/vol1 --> /dev/sdb1 errors out

      From FOS with the mount point in place if I stop the script where it errors out. I can move to /images/vol1 no problem. I can’t touch a file in /images/vol1 because /images on the fog server is shared out read only. There must be some conditional check that is failing above where it works when /images/vol1 is a directory and failing when /images/vol1 is a mountpoint. I’m just not seeing it.

    • george1421G

      Unable to locate image store

      General
      • • • george1421
      6
      0
      Votes
      6
      Posts
      2.1k
      Views

      george1421G

      @Wayne-Workman It was capture. I was testing the bits about having a mounted (local) file system under /images This was the first issue I ran into.

    • george1421G

      FOG-casting across VLANs (subnets)

      Tutorials
      • • • george1421
      5
      1
      Votes
      5
      Posts
      3.9k
      Views

      george1421G

      Part 2 Pfsense Router setup

      In this design, the pfSense router will perform 4 different functions.

      Provide the dhcp addresses to the clients on the deployment network [192.168.23.0/24] Provide the necessary dhcp boot options to pxe boot the clients on the deployment network Act as a normal router to route traffic between the subnets Act as a IGMP route (via its built in IGMP Proxy server). The IGMP server will listen on its defined upstream interface [LAN] for any defined multicast streams and rebroadcast the stream on any of the defined downstream interfaces [WAN]. Please note I’m only using the concepts of LAN and WAN as interface names. I could have just as easily used em0 and em1, but inside pfSense they reference the logical names of LAN and WAN exclusively. To avoid confusion I’ll continue to use those labels through this document, just understand the are label and not based on functional intent.

      I’m not going to go through the setup of the pfSense router since there are many fine examples of setting up pfSense as a basic router. I will go through the settings I changed to configure the igmp proxy setting.

      In the graphic above I configured the pfSense router’s

      Set the LAN interface address to 192.168.50.250/24
      0_1495554662259_Interfaces_ LAN.png

      Set the WAN interface address to 192.168.23.1/24
      0_1495554685442_Interfaces_ WAN.png

      Configured the dhcp server on the WAN interface to issue IP addresses from 192.168.23.10 to 192.168.23.250.
      0_1495555318851_Services_ DHCP Server_WAN1.png

      For the imaging network, the default route points to the pfSense WAN interface of 192.168.23.1
      0_1495555352459_Services_ DHCP Server_WAN2.png

      Configured the netboot section of the WAN’s dhcp server to send out the {next-server} of 192.168.50.100 with a bios {boot-file} of undionly,kpxe, ia32 uefi boot file of i386/ipxe.efi, and ipxe.efi for the x64 uefi boot file.
      0_1495555364450_Services_ DHCP Server_WAN3.png

      In pfSense Advanced Configuration I disabled all firewall rules. In this setup I want pfSense to act as a normal unrestricted router and not as a screening or firewall appliance.
      0_1495556193981_System_ Advanced_ Firewall_NAT.png

      You will need to go into the firewall rules and add one rule to each interface (LAN and WAN) that is an allow all to any
      WAN rule
      0_1495558034751_Firewall_ Rules_WAN1.png
      LAN rule
      0_1495558047051_Firewall_ Rules_ LAN1.png

      With the static route configured on your FOG server and the pfSense router now setup on the network, you should be able to ping the deployment network’s router interface [WAN] from the fog server. If you can’t then something is setup incorrectly on the iP router side. Don’t proceed until you have basic IP routing working correctly.

    • george1421G

      Setting up a Windows 2012 server as a FOG Storage Node

      Tutorials
      • • • george1421
      6
      0
      Votes
      6
      Posts
      2.1k
      Views

      J

      @george1421 said in Setting up a Windows 2012 server as a FOG Storage Node:

      @Jamaal The tutorial was more of a proof of concept than something that should be used in production. Did it work, yeah. Would I probably use it… maybe not but some of the dedup capabilities in 2016 and 2019 make it sound intreaging.

      For your case if you have additional space on your VM host server you might consider adding an additional virtual disk to your fog server then adding it to the LVM group for your fog server. There are a number of ways to go about this, but that discussion should be moved to a new thread.

      Ok, I’ll create a new post, thanks for your assistance.

    • george1421G

      When DHCP-PXE booting process goes bad and you have no clue

      Tutorials
      • • • george1421
      1
      4
      Votes
      1
      Posts
      17.4k
      Views

      No one has replied

    • george1421G

      Add enhanced iPXE boot menu capabilities - based on host associations

      Feature Request
      • • • george1421
      2
      1
      Votes
      2
      Posts
      1.1k
      Views

      JunkhackerJ

      @george1421 i actually don’t think this is as massive of a rewrite/change as you imagine. Tom put a lot of flexibility in the code. I honestly think this could probably all be done with a plugin.

      i mean, it’s beyond MY skill level. but someone could do it.

    • george1421G

      Solved FOG broke my hard drive, why?

      Bug Reports
      • • • george1421
      2
      0
      Votes
      2
      Posts
      967
      Views

      george1421G

      The developers found this issue to why the log file grew so big (after almost a year of log file collection). The log file will now be capped at the log file maximum set by the fog configuration settings. This was just a fluke case that caused this file to grow to an abnormal size.

      The fix / log file limiting code will be in 1.3.5RC11 when its released.

    • george1421G

      FOG Postinit scripts, before the magic begins...

      Tutorials
      • • • george1421
      4
      2
      Votes
      4
      Posts
      3.3k
      Views

      Wayne WorkmanW

      #wiki worthy

    • george1421G

      Dynamic FOG Replicator transfer rates

      Tutorials
      • • • george1421
      4
      2
      Votes
      4
      Posts
      1.4k
      Views

      Wayne WorkmanW

      @george1421 as long as people understand that, then yeah this is great.

    • george1421G

      Synology NAS as FOG Storage node

      Tutorials
      • • • george1421
      31
      5
      Votes
      31
      Posts
      19.6k
      Views

      M

      @george1421
      for those struggling with permissions with dev folder.
      nfs creates a root:root with 775 permissions and fog ftpuser isn’t part of that group

      Just use setgid feature on filesystem . it will enable inheritance
      first change the owner of the folders and make “users” the group , lets say fog is your ftp user

      chown -R fog:users /volume1/images/

      #set inheritance to the dev folder

      chmod g+s /volume1/images/dev/

      now every new file under dev will have the directory group owner

      Regards

    • george1421G

      Help with Win10 Driver injection

      General Problems
      • • • george1421
      88
      0
      Votes
      88
      Posts
      32.9k
      Views

      J

      @george1421 what version of MDT are you running btw? I’m on 8450.

    • george1421G

      PXE Booting Surface Pro 3 to FOG Menu

      Tutorials
      • • • george1421
      4
      0
      Votes
      4
      Posts
      2.3k
      Views

      Wayne WorkmanW

      https://wiki.fogproject.org/wiki/index.php?title=Surface_Pro

    • george1421G

      FOG Post install script for Win Driver injection

      Tutorials
      • • • george1421
      69
      8
      Votes
      69
      Posts
      46.6k
      Views

      JJ FullmerJ

      @Coolguy3289 Sorry for the crazy delayed reply, I just saw this, I must have missed the notification

      This is what my general structure looks like. You would not need to recreate that with the + pseudo wildcards, that is part of my windows side matching that I have now actually replaced with this modellist method. The grep line will search each model folder in the given make folder regardless of its name. I will probably end up changing those folders to be something like HP ElitePro G# or something like that.

      e880c851-3f3c-418d-adb9-8ff886199667-image.png

      Then say I have a HP Elite Mini 600 G9 Desktop PC

      This bit

      makePth="/images/drivers/${make}" cd $makePth;

      Should get me into the /images/drivers/hp folder

      Then this listFile=`grep -il "$model" ./*/*-ModelList.txt` should search each HP ModelList.txt for that model string using grep and return the matching modelList file with a match. In this case it would match /images/drivers/hp/HP + +00 G9+/HP + +00 G9+-ModelList.txt as that file looks like this where I have various possible matching model names these drivers apply to including the one being searched for

      HP Elite Mini 600 G9 Desktop PC HP Elitedesk 600 G9 DM HP Elite Mini 800 G9 Desktop PC HP Pro Mini 400 G9 Desktop PC HP EliteOne 840 23.8 inch G9 All-in-One Desktop PC

      And then this remotedriverpath="$makePth/${listFile%/*}" should point to the parent path of where the found ModelList.txt file was found and it will then proceed to inject that folder to `C:\Out-Of-Box Drivers\HP + +00 G9+

      And as to creating those modelList.txt files, it’s easier than it sounds, especially if you use the fog api powershell module FogApi (see my signature).

      For example, to get all my current HP (and any other make that stores the friendly name of their model in system-product-name) model names as they are detected by fog you would setup the FogApi module in powershell

      Install-Module FogApi; Set-FogServerSettings -interactive

      Then this one liner would get all your fog host inventories, select just the sysman and sysproduct fields, and then sort it to unique model names giving you a list of model names you have in your inventory

      (get-foghosts).inventory | select-object sysman,sysproduct | sort-object sysproduct -Unique

      You’d also what to run these other 2 commands to get lists of other model names stored in system-version or baseboard-product-name

      (get-foghosts).inventory | select-object sysman,sysversion | sort-object sysversion -Unique (get-foghosts).inventory | select-object sysman,mbproductname | sort-object mbproductname -Unique

      You could probably expound from there to programatically create to folder structure and the modelList files of your current hosts, but I don’t have time at the moment to get that deep into it. I don’t have that many different models and already had the folder structure so just getting those lists was all I needed to construct the model list files

    • george1421G

      Basic Persistent groups and 1.3.0RC16

      Tutorials
      • • • george1421
      24
      2
      Votes
      24
      Posts
      11.1k
      Views

      Tom ElliottT

      @yannickF You really should state your issues.

      If a feature isn’t available for whatever reason, we will tell you, but leaving us in “uh oh” isn’t really a good approach.

      What issue are you having?

    • george1421G

      Advanced dnsmasq techniques

      Tutorials
      • • • george1421
      9
      2
      Votes
      9
      Posts
      9.2k
      Views

      Wayne WorkmanW

      This has been added to the wiki here:
      Link

    • george1421G

      Compiling dnsmasq 2.76 if you need uefi support

      Tutorials
      • • • george1421
      15
      2
      Votes
      15
      Posts
      11.7k
      Views

      F

      My two cents.

      In RHEL7 I have compiled the dnsmasq 0.78 version using these instructions and doing some changes.

      Install the necesary packages:

      sudo yum install nettle-devel sudo yum install libidn2-devel sudo yum install libnetfilter_conntrack-devel sudo yum install dbus-devel

      config.h options:

      /* #define HAVE_LUASCRIPT */ #define HAVE_DBUS /* #define HAVE_IDN*/ #define HAVE_LIBIDN2 #define HAVE_CONNTRACK #define HAVE_DNSSEC

      Compiling and starting the service:

      sudo make install sudo systemctl start dnsmasq sudo systemctl status dnsmasq

      Output:

      dnsmasq -v Dnsmasq version 2.78 Copyright (c) 2000-2017 Simon Kelley Compile time options: IPv6 GNU-getopt DBus no-i18n IDN2 DHCP DHCPv6 no-Lua TFTP conntrack ipset auth DNSSEC loop-detect inotify This software comes with ABSOLUTELY NO WARRANTY. Dnsmasq is free software, and you are welcome to redistribute it under the terms of the GNU General Public License, version 2 or 3.
    • 1 / 1