General

• J

  [HELP WANTED] Client Internationalization
  • Joe Schmitt

  56
  2
  Votes
  56
  Posts
  10188
  Views

  S

  @Kirill Great, I will add this to the fog-client in the next days!

  For the FOG translations you wanna take a look at the files here: https://github.com/FOGProject/fogproject/tree/dev-branch/packages/web/management/languages

  The master branch points to the current version (1.5.8 as of now) and for new things we work on dev-branch (as in the link above) or created feature branches. As we don’t have much changes in the language files currently I would suggest you work on what we have in dev-branch.

  Best if you grab a copy of the english version and start translating on that. I know there are many lines marked as fuzzy because of changes in strings. I was hoping to clean this up at some point but never got to it so far. If you are keen you are more than welcome to clean this up first. Would be really great!

• J

  Firewall Configuration
  • Joe Schmitt

  24
  2
  Votes
  24
  Posts
  13800
  Views

  

  the firewalld configuration no longer works on Fedora 21.

  The commands succeed, but at least http is blocked still.

• J

  SELinux Policy
  • Joe Schmitt

  19
  2
  Votes
  19
  Posts
  15422
  Views

  

  Bumping this - it would be so nice to have SELinux enabled as a standard configuration.

• C

  FOG Status
  • Chuck Syperski

  59
  0
  Votes
  59
  Posts
  34016
  Views

  

  Nope it’s still heavily in the beta phase, I bet when we do have an idea we will post it on the forums or on the main site letting everyone know we are close. There is a thread you are more than welcome to monitor it can be located here ->[url]http://fogproject.org/forum/threads/latest-fog-0-33b.6476/[/url]

• 

  New release?
  • Wayne Workman

  6
  1
  Votes
  6
  Posts
  63
  Views

  

  @quazz I already got it working on the working-1.6 repository. I started working to limit the amount of error messages too, though that’s going to be a project in and of itself.

  For dev-branch:

  https://github.com/FOGProject/fogproject/blob/dev-branch/packages/web/lib/db/databasemanager.class.php#L47

  Change the implode($noDBpattern, "|") to implode("|", $noDBpattern)

  That should fix the issue as it seems PHP 8 standardized their usage of implode/explode for ease.

• 

  FOG External Reporting
  • Wayne Workman

  13
  0
  Votes
  13
  Posts
  191
  Views

  

  After a bit over one full year now, we are at 527 dev installations of fog.

• F

  NVRAM EFI bootorder
  • Fernando Gietz

  8
  0
  Votes
  8
  Posts
  63
  Views

  F

  @sebastian-roth Yes, I saw it. I am following it XD
  it can be the way to do it.

• L

  Install/update your database schema" URL just goes to blank FOG UI .
  • llightfoot

  7
  0
  Votes
  7
  Posts
  32
  Views

  L

  @llightfoot

  When I inspect the page and go tot he network tab hit refresh @
  https://10.33.250.5/fog/management/

  It gets a server 500 response from /fog/management/
  and the second thing it attempts to load is favicon.ico which is a 404 error.

  L
  llightfoot
  about 5 hours ago

  I should give some more specifics.

  This is a first server build on physical hardware.
  Rhel 7
  I utilized the rhel 7 install instructions
  I did not use any specialized command line options when kicking off the bash script to install fog.
  I did disable selinux
  I did disable firewall
  I can access the login page after passing through the ssl error but there is nothing to log into.

• M

  deduplication of images files possible yet?
  • mfinn999

  5
  0
  Votes
  5
  Posts
  187
  Views

  

  @george1421 i meant to reply to this a long time ago, but here goes.

  testing on deduping of those images has been done. they dedup quite well. the dedup changes affect zstd and pigz compressed images. pigz compressed images actually dedup better, but the the compression and performance are worse. it’s a tradeoff to be evaluated by the individual.

  dedup is only possible with the newer version of partclone due to a rolling checksum integraed into the image format on earlier versions. the newer version lets us choose no checksum.

  the compressed binary file is dedupable thanks to the --rsyncable flag on compression that is supported by both pigz and zstd.

  like george said, any deduping would be the responsibility of the underlying filesystem or storage, not built into fog itself.

• 

  RHEL 8, CentOS 8, master branch, July 22, 2021
  • Wayne Workman

  9
  0
  Votes
  9
  Posts
  257
  Views

  S

  @sebastian-roth said in RHEL 8, CentOS 8, master branch, July 22, 2021:

  sed -i -e 's/dnf check-update/dnf -y check-update/g' /path/to/fogproject/lib/redhat/config.

  Not sure if you saw that I edited my initial post. That sed command should take care of the issue that is causing master to fail. Find the related commit that fixed the issue in dev-branch here: https://github.com/FOGProject/fogproject/commit/90caf2367d21d0594b7f16b2813a2fa94684ad78

• S

  Streamlining kernel and init releases
  • Sebastian Roth

  1
  0
  Votes
  1
  Posts
  35
  Views

  No one has replied

• A

  New to Fog - Suggestions/help
  • alboon

  5
  0
  Votes
  5
  Posts
  64
  Views

  A

  @tom-elliott
  Thanks for the details

• L

  Dry-run mode for monitoring
  • Luc Novales

  3
  0
  Votes
  3
  Posts
  35
  Views

  L

  @sebastian-roth Thanks for this reply.
  I will try un inventory task to check bi-directional data exchange.
  Luc.

• A

  Configuring IPtables and running into no file or directory error
  • alomarh

  2
  0
  Votes
  2
  Posts
  20
  Views

  

  @alomarh Well it depends on what version of linux you are using. This appears to be RHEL compatible OS.

  You can restrict the NFS server in FOG to limit access to a specific subnet range. You can do this without the need of a firewall. Look at the /etc/exports file. In the share line it starts with a star ( * ) replace that with the subnet range you want to share to. Look up nfs and exports for the exact syntax. Its hard to limit NFS to a single port range. You can do it, but you will need to make some configuration changes. NFSv4 is the way to go, but FOG is not there yet. I did experiment with it and it works with a few changes to the FOG server and FOS Linux.

• 

  Ubuntu 16.04 installer observation
  • Wayne Workman

  7
  0
  Votes
  7
  Posts
  87
  Views

  S

  @Wayne-Workman Ok, right. Then toss it I would say.

• V

  Export captured images into Bootable USB
  • vtl.victor

  4
  0
  Votes
  4
  Posts
  66
  Views

  S

  @vtl.victor I am not saying it’s impossible to do. It just needs work and we don’t seem to find the time to work on this. Your quickest way to achieve what you want is capture/deploy an image at your FOG network site. Don’t let the deployed host boot into the OS (add kernel parameter shutdown=1 to that host). Then boot that same host up with Clonezilla (for example) and for taking a backup that can be deployed at an offline site on USB - no FOG server needed there - just the Clonezilla boot media and image on portable drive. (cross references: 1, 2, 3)

  If that’s not what you want you need to dive into the details. Just quoting Junkhacker’s postfrom another topic here:

  FOG image capture and deploy are multi-step processes. each are several commands that rely on scripts and programs in the FOG OS (FOS) and change based on what options you have selected. FOG images are not designed to be used stand alone. Using FOG images without a FOG server will require steps that were expected to be automated and there really isn’t a quick way around it.

  So if you or anyone else is keen, you want to start looking at the commands to do this here:

  Clear old partition table: https://github.com/FOGProject/fos/blob/master/Buildroot/board/FOG/FOS/rootfs_overlay/usr/share/fog/lib/funcs.sh#L2012 Apply new partition table: https://github.com/FOGProject/fos/blob/master/Buildroot/board/FOG/FOS/rootfs_overlay/usr/share/fog/lib/funcs.sh#L2041 Loop to do the restore: https://github.com/FOGProject/fos/blob/master/Buildroot/board/FOG/FOS/rootfs_overlay/usr/share/fog/lib/funcs.sh#L2376 Finally call partclone deploy the image files one by one: https://github.com/FOGProject/fos/blob/master/Buildroot/board/FOG/FOS/rootfs_overlay/usr/share/fog/lib/funcs.sh#L760 Restore UUID information: https://github.com/FOGProject/fos/blob/master/Buildroot/board/FOG/FOS/rootfs_overlay/usr/share/fog/lib/partition-funcs.sh#L25 Possibly more things I have missed…

  And that’s just the simple case without resizing partitions!

  It’s all open source, it’s all yours!

• 

  Ansible scripts for installation?
  • Wayne Workman

  1
  0
  Votes
  1
  Posts
  58
  Views

  No one has replied

• K

  Access Control Plugin
  • kevinnew22

  3
  0
  Votes
  3
  Posts
  38
  Views

  K

  @fernando-gietz thanks

• L

  Automate iPXE Menu Selection
  • londonfog

  4
  0
  Votes
  4
  Posts
  87
  Views

  

  @londonfog Just wondering out loud but if that python script can hit the FOG API, and register that new host and then select image deploy when the target computer boots up for the first time and it pxe boots, it will boot right into imaging. So if you already have the image defined, then you would create one curl api call to register the new server’s name and mac address with fog, then a second curl api call to deploy your image.

  ref: https://forums.fogproject.org/topic/11184/api-powershell-create-host-and-deploy-task-script

• 

  Ubuntu 16, 18, 20, and Debian 10
  • Wayne Workman

  6
  1
  Votes
  6
  Posts
  99
  Views

  

  @sebastian-roth Great job, the installation tests are looking beautiful today.