Project

General

Profile

Feature #34

Support for use as FOG Project Server

Added by freenasfan - about 9 years ago. Updated almost 4 years ago.

Status:
Closed
Priority:
Important
Assignee:
-
Category:
Middleware
Target version:
Estimated time:
Severity:
New
Reason for Closing:
Reason for Blocked:
Needs QA:
Yes
Needs Doc:
Yes
Needs Merging:
Yes
Needs Automation:
No
Support Suite Ticket:
n/a
Hardware Configuration:

Description

FOG is a free, open source computer cloning solution (think "Symantec Ghost"), which allows computers to be cloned via the network, via either unicast or multicast.

It pulls together several technologies into one comprehensive package which covers DHCP, NFS and TFTP (which together provide PXE services), as well as FTP and http.

See www.fogproject.org. for more information.

History

#1 Updated by Anonymous about 9 years ago

Corrected version that this enhancement applies to

#2 Updated by jwhitt - about 9 years ago

Just to clarify... were you considering integrating the FOG project into Freenas, or using freenas as a storage location for your images?

I could see using freenas as a location for your images, there are two options i believe when you install fog you can set the image location usually /images this could be mounted via a nfs share on your freenas machine to your fog server.

Or FOG has the abbility to create what it calls storage nodes. My thought would be to create a plugin for freenas that creates a storage node of a share on freenas. This would require to see what is involved in creating a storage node on fog and implementing that as a plugin for freenas.

I haven't worked too much with storage nodes on FOG, however i believe there are some benefits to using fog with storage nodes over mounting a share. I will look into this and see what i can come up with.

#3 Updated by freenasfan - over 8 years ago

I would prefer integrating FOG into [[FreeNAS]] over using it as a storage node, since it would be an all-in-one solution. Having said that, I would settle for using it as a storage node, since it would at least provide me with image versioning via ZFS snapshots

Also, I believe storage nodes are better than a simple NFS mount, as storage nodes in the same group are kept in sync via FTP (I would prefer rsync for obvious reasons, but this is how FOG does it at the moment).

#4 Updated by Mahdi - over 8 years ago

++

#5 Updated by V4705 - over 8 years ago

Second that, its a great idea.

#6 Updated by Bryan T over 8 years ago

This is a great idea. I am doing the same thing! Anything to keep me further away from windows machines :). Total integration is always a goal. Although I think it would be very difficult since Fog is primarily PHP and [[FreeNas]] is Django Python. I think the main idea of storage nodes in Fog is to utilize more hosts with FTP or NFS to multicast mass clients. Overall I don't see a whole lot of changing the current infrastructure there. For a complete integration I assume to make this happen, unfortunately would be to scrap the Fog idea and write a new service view. This view could be created utilizing more Python friendly tools like Cobbler. Also could reuse much of the existing code. Stuff like this would be good to have a plugin feature for [[FreeNas]] which could be community driven. More specifically, Django apps that can be integrated with an API? I'm new if I missed some obvious docs. I woulden't want to take the devs away from crucial issues. One more thing, as good as it may sound for all this integration. Having the nas and imager seperate allows me to use the imaging server as a virtual machine host, making it easier to update the master image (virtual to metal). I'm sure that most of the popular hypervisors run on [[FreeBSD]], but wow what a system that would be! Yes, Multiple disconnected systems are a pain, but there is some truth to that age old Unix philosopy sometimes, do one thing and do it well.

Bryan

#7 Updated by Anonymous about 8 years ago

  • Status changed from Unscreened to Closed

FOG is a complete Linux software distribution with a pretty PHP GUI on top to integrate everything together. It would be better to rewrite the individual components from scratch in 8.1, or port over the PHP bits if you really desire. I don't recommend porting FOG though because a) it contains Linux specific code, and b) it uses Java (at least superficially.. I didn't look to see if it used.

You're better off creating plugins for dhcp, named, etc as most of this stuff is either already included in [[FreeBSD]] or can be installed with minimal headache.

#8 Avatar?id=14398&size=24x24 Updated by Kris Moore about 4 years ago

Commit: f017fd3d5d117541e8c8d8bf78b5c23509dcd07f
https://github.com/pcbsd/freebsd-ports/commit/f017fd3d5d117541e8c8d8bf78b5c23509dcd07f
Author: Bernard Spil <>
Date: 2015-09-23 (Wed, 23 Sep 2015)

Log Message:
-----------
Merge pull request #34 from Sp1l/master

Fix segfault in OpenVPN
Fix some more ports that have deps

#9 Avatar?id=14398&size=24x24 Updated by Kris Moore about 4 years ago

Commit: eac0d507dbc63514e8124244009d68a5a0786687
https://github.com/pcbsd/freebsd-ports/commit/eac0d507dbc63514e8124244009d68a5a0786687
Author: pawel <>
Date: 2015-11-24 (Tue, 24 Nov 2015)

Log Message:
-----------
Update to version 0.2.0

Changelog:
- quiet batch mode (not available on OSX) - #13
- bugfixes in Napisy24 engine - #23
- icons placed at directories according to their sizes - #24
- HiDPI display awareness (OSX) - #27
- support for paths containing special characters (Windows) - #28
- bugfixed SRT conversion adding empty lines to resulting file (Windows) - #29
- application self-closing in batch mode (OSX) - #31
- added version information to .exe file (Windows) - #32
- bugfixes in file encoding detection (UTF-8 with BOM amongst others) - #34
- preserving original file encoding during subtitle format conversion
- bugfixed backup language support - #36

#10 Avatar?id=14398&size=24x24 Updated by Kris Moore almost 4 years ago

Commit: 3bd19b1310a12a6bae51db5d7ca2d6a6ed1aed17
https://github.com/pcbsd/freebsd-ports/commit/3bd19b1310a12a6bae51db5d7ca2d6a6ed1aed17
Author: truckman <>
Date: 2016-02-03 (Wed, 03 Feb 2016)

Log Message:
-----------
Upgrade net/nmsg to 0.11.0:

nmsg (0.11.0)

[ Henry Stern ]
  • Add an interval randomization option that randomizes the initial offset
    within the selected time interval. This functionality is exposed via the
    libnmsg nmsg_io_set_interval_randomized() function and the nmsgtool -R /
    --randomize command-line option (#27, #33).
  • Add documention for nmsgtool -j / --readjson and -J / --write-json
    command-line options (#26, #28).
  • Add PKG_CHECK_MODULES dependency on yajl >= 2.1.0 (#29, #31).
  • Make nmsgtool -k / --kicker work when combined with -c or -t, when
    producing output in JSON format (#25, #38).
  • Fix compiler warning [-Wtautological-compare] in
    _nmsg_msgmod_json_to_payload_load() (#36, #39).
  • Add nmsg_message_get_num_field_values(),
    nmsg_message_get_num_field_values_by_idx() functions (#5, #40).
[ Robert Edmonds ]
  • Remove the unused enum nmsg_modtype from the internal libnmsg API (#30).
  • Header file cleanups (#14, #34).
  • Rewrite nmsg_res_lookup() to use a switch, which eliminates a Clang
    warning (#14, #35).
  • Add a message filtering capability to the libnmsg I/O loop, including
    external filter module plugin and nmsgtool support (#41, #43, #44).
[ Mike Schiffman ]
  • Add yajl/ prefix to #include's of yajl headers (#37)

Pet portlint

Sponsored by: Farsight Security, Inc.

#11 Avatar?id=14398&size=24x24 Updated by Kris Moore almost 4 years ago

Commit: 3bd19b1310a12a6bae51db5d7ca2d6a6ed1aed17
https://github.com/pcbsd/freebsd-ports/commit/3bd19b1310a12a6bae51db5d7ca2d6a6ed1aed17
Author: truckman <>
Date: 2016-02-03 (Wed, 03 Feb 2016)

Log Message:
-----------
Upgrade net/nmsg to 0.11.0:

nmsg (0.11.0)

[ Henry Stern ]
  • Add an interval randomization option that randomizes the initial offset
    within the selected time interval. This functionality is exposed via the
    libnmsg nmsg_io_set_interval_randomized() function and the nmsgtool -R /
    --randomize command-line option (#27, #33).
  • Add documention for nmsgtool -j / --readjson and -J / --write-json
    command-line options (#26, #28).
  • Add PKG_CHECK_MODULES dependency on yajl >= 2.1.0 (#29, #31).
  • Make nmsgtool -k / --kicker work when combined with -c or -t, when
    producing output in JSON format (#25, #38).
  • Fix compiler warning [-Wtautological-compare] in
    _nmsg_msgmod_json_to_payload_load() (#36, #39).
  • Add nmsg_message_get_num_field_values(),
    nmsg_message_get_num_field_values_by_idx() functions (#5, #40).
[ Robert Edmonds ]
  • Remove the unused enum nmsg_modtype from the internal libnmsg API (#30).
  • Header file cleanups (#14, #34).
  • Rewrite nmsg_res_lookup() to use a switch, which eliminates a Clang
    warning (#14, #35).
  • Add a message filtering capability to the libnmsg I/O loop, including
    external filter module plugin and nmsgtool support (#41, #43, #44).
[ Mike Schiffman ]
  • Add yajl/ prefix to #include's of yajl headers (#37)

Pet portlint

Sponsored by: Farsight Security, Inc.

Also available in: Atom PDF