Ideal FOG Setup
-
I used 14.04 for about 6 months on two FOG servers, then fresh installed 14.10 on both of them.
I’ve been running 14.10 for over 8 months on both now with no issues. Don’t sweat it, IMO…
-
@Wayne-Workman Sorry to hop on this thread, but the discussion is very relevant to what I’m working on. Currently we run FOG 1.1.2 on Ubuntu 12.04 LTS. I’ve been messing around with the latest SVN builds on Ubuntu 14.04 LTS.
What’s the upgrade path for the “old” client to the new one? The speed improvements I’m seeing in the latest SVN builds, along with the hopefully improved management UI performance with our 8k+ hosts, makes me want to migrate before summer imaging gets underway on a large scale. With that said, I’m having a hard time finding info on what the upgrade is like to go from the current “old” client to the new one.
Anyone have some input on this?
-
The new “client” is still in beta, and I am not using it yet… FOG Trunk comes with the “new” client and the Legacy client too. To be clear, the “FOG Client Service” is what gets installed on your image, and then that client communicates with the FOG Server to do various things.
I’m using FOG Trunk with the Legacy client currently. But by all means, go ahead and try out the new client.
To upgrade to FOG Trunk, I recommend using the ‘svn’ method. Here’s an article on that:
https://wiki.fogproject.org/wiki/index.php/SVNFOG Trunk is currently tested working on Debian 8, CentOS 7, Fedora 21 and 22, and Ubuntu 15.04 and a little older, and current RHEL. I’d recommend going with RHEL, CentOS, or Fedora… But that choice is up to you.
-
@MRCUR If you’re rebuilding every image that you have (like I do each summer) for specific labs/buildings, I would suggest rebuilding it fresh. Do you have to? No. But it’s easy enough to do that.
If not, I would suggest setting BitSync up to your ‘old’ 1.1.2 machine and have it update that way.
-
@RLane We are rebuilding images (thankfully that’s not one of my responsibilities), but we won’t reimage every machine (tough to do with this many of them).
My actual plan is to upgrade the existing FOG servers (I have one storage node besides the main server) once I’m confident in the SVN rather than do a fresh install on new servers.
-
@Wayne-Workman Thanks Wayne. I guess my real question is about the upgrade path between clients, but it sounds like there isn’t info on that yet. Obviously out of the box, there is no “auto update” to the new client since the legacy client is still being supported - I’m just looking for guidance on what, if any, upgrade path there will be once 1.3.0 launches.
Upgrade path?
Currently, in FOG Trunk, you’d go to FOG Configuration -> FOG Settings -> Client Service -> and tick the new client checkbox.
There might not be a path of “upgrading” for the old clients… There is talk of discontinuing support of the legacy client, and just disabling it completely in 1.3.0.
As far as the old clients out in the field… they will just be out there… lonely… with nobody to talk to… and some day… they will go to a better place when a new image is applied.
Currently, though, FOG Trunk does support both the old client AND the new one, although you can’t set settings for the old client when the “new client” check box is ticked. Whatever AD credentials/ encrypted strings are set on clients will stay, but new changes will use the new client methods.
Did that answer your question?
-
I am so excited for 1.3.0! Having said that, all of my real work has to be done on 1.2.0. Like the issue Tom recently mentioned that broke several images for a few revisions, when using the latest, you are subject to the latest bugs (even undiscovered ones).
I can’t afford to have production problems on my production fog server, but I happily have a node setup with the latest SVN for my own pleasure and enjoyment (I’m looking at you web-based boot menu!). Good luck!
-
@DevinR For what it’s worth, I’ve had r3540 running since it’s been out. I’ve taken images, imaged devices, etc. with no trouble. A hair quicker too than 1.2.0 over my 10/100 clients.
The biggest thing I’m worried about and I know @Wayne-Workman said it should be no problem, is installing client 0.8.4 on my images (using r3540) and relying on the automatic update to patch them when 1.3.0 is finalized.
-
@MRCUR @Wayne-Workman Thanks for the edit Wayne. That answers everything for me.
I do hope when 1.3.0 launches, the old client is still supported as it is in the current SVN’s. That way I can work on removing the legacy client from existing machines and installing the new client. Otherwise it’s going to be a long time until many machines get the new client as we do not reimage all that quickly with 8,000+ hosts.
-
ah dang it… I’m getting bad about that (that’s the 2nd time)… I thought I was just “replying” but I end up editing other people’s posts… not sure if I should be a mod! lol
-
@MRCUR said:
I do hope when 1.3.0 launches, the old client is still supported as it is in the current SVN’s. That way I can work on removing the legacy client from existing machines and installing the new client. Otherwise it’s going to be a long time until many machines get the new client as we do not reimage all that quickly with 8,000+ hosts.
@Developers Probably something to consider there…
I, too, am partial to the legacy client… it’s a fall-back, at the least.