FOG 1.6 Testing Needed - Help would be greatly appreciated as needed

[jms]

@Sebastian-Roth I set SElinux to permissive and rebooted and now have full access to the web application. Are there any tips/tricks to get this to work in a more secure environment? My customer will require it.

[Sebastian Roth]

@jms Are you sure you wanna use the current 1.6 testing branch of FOG? From what you write it doesn’t sound like it. Please let us know what exactly are you aiming for.

We have a wiki article on CentOS that you might find interesting: https://wiki.fogproject.org/wiki/index.php?title=CentOS_7

About SELinux… first search result in the forums is: https://forums.fogproject.org/topic/6154/selinux-policy

[Tom Elliott]

I know it’s been a while since I posted this announcement, but I’ve been kind of keeping up with @Sebastian-Roth with his code changes with 1.5.5 and how they apply to 1.6 as well.

Remember, for the most part, the backend side of FOG is staying the same with as minimal of changes as I can. What this means, is many of things in terms of overall performance and functionality that has been going into 1.5.5 can be relatively simple to apply to 1.6.

There are some caveats to this though. But I think things are looking much better than they had from the initial posting of this.

I know it’s the holiday season and I hope everybody enjoys it. I think this is all the more reason to apply the post so it can be viewed a little more readily.

Thank you all.

[astrugatch]

With what sounds to be the impending release of the 1.5.x (6?). The 1.6 branch seems to be several commits back from 1.5.5 (almost 200, not sure how many are just different based on the UI). Is 1.6 going to keep up with the new release or should I pump the breaks until it is more official. I prefer the UI greatly to the 1.5.5 release and am the impatient type. I just don’t want to move my system over only to have to back out.

[Tom Elliott]

@astrugatch The dev-branch and working-1.6 branches have more or less diverged. So while it may “seem” behind the curve, I assure you it is not. There may be some minor differences but they’re 2 totally separate things.

[astrugatch]

@Tom-Elliott

Will they be living in parallel for the foreseeable future or is there a merge on the horizon?

[Tom Elliott]

@astrugatch most likely parallel as a merge would create a TON of conflicts.

[lebrun78]

Hello,
I’m installing a new server with Centos 8.0.
Could I use 1.6 version for production ?

Arnaud

[george1421]

@lebrun78 Centos 8 is not currently supported by FOG 1.5.7, you can switched to the dev-branch and updated version of 1.5.7 that will bring you to ~1.5.7.49. You can switch to the 1.6 deb branch which is a stepping stone towards FOG 1.6.0 which hasn’t been released as of now. Plus upgrading to 1.6.x is a one way street. Only make the move if you plan on staying on 1.6.x for better or worse.

To install the dev branch change to the root of the fogproject directory (also understand this only works if you created the git install and not the tarball install). This directory is typically in either /opt or /root. Once in the fogproject directory issue this command git checkout dev-branch. Next change to the bin directory and reinstall FOG. If you already tried to install FOG 1.5.7 onto Centos 8 you may have to drop the fog database (understand you will loose the entire contents of the fog database and all configurations if you do this).

[Tom Elliott]

@george1421 To test what will become 1.6 the git checkout needs to be: git checkout working-1.6

dev-branch will put you on 1.5.7.40 (ish) 1.5.7.700 (ish) is in working-1.6

[Sebastian Roth]

@lebrun78 Just be aware there is no way back to the 1.5.x version of FOG if you switched to working-1.6 now other than very messy manual manipulations in the database. We are working towards 1.6 and hope to have most users upgrade at some point. So I am not saying you shouldn’t. Just want to make sure you understand the consequences.