Topics created by Wayne Workman

@Wayne-Workman Really awesome work. Thank you so much for all this as well as new ideas!

I definitely vote for more testing as it’s still mostly manual work. Though I have to admit that I can’t see me working on this.

One option for limiting support to reduce workload would be to limit to LTS branches only. So only 18.04 and 20.04 for Ubuntu and skipping the intermediary releases and dropping those that go out of support by their vendor (eg ubuntu 14.04, 16.04).

Another thing I just now thought of - versioning the partition file we keep with the images. We can start out with v1.0.0. And if we change how we store that file, we simply increment the version. This would give us some more flexibility in regard to changes.

Thinking further, the scripts that collect the physical partitions are fine, we can just add JSON output for those.

And really, the LVM describing tools are what needs JSON output, so the effort there is targeted to just those.

I think I’m going to take a swing at adding JSON to an LVM describing tool (there are several).

@sebastian-roth said in New release?:

For those I’d suggest they stick with 1.5.x for now and probably some months down the road until 1.6.x is fully ready for production. Just my opinion.

Same here I think sticking with 1.5.x line a bit longer is in order. No new features in 1.5.x just bug fixes for now. We need to get the 1.5.x last version as stable as 1.4.4 was to the 1.4.x line.

In 1.6 I’d like to see nfsv4, and some other stuff around security posture of FOG nothing dramatic though.

@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

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

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

@wayne-workman said in Fedora 33 and Ubuntu 16:

wants to get everything OS agnostic by replacing PHP components with NodeJS ones, getting the UI and API away from making native OS calls, so on.

I agree with this too. Node.js opens the door to running the FOG server on a lot more platforms than just linux. It WILL be a long road to get there (if ever). We do need 3-4 node.js new developers to step up and restart the FOG-too project to get things moving.

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

The figures seem much more stable now, much less fluctuations. Thank you @Quazz !

Tried emailing chuck, he has not replied. For now, I’ve removed all of the fogproject.org references, and HTTPS is working directly (redirect does not work). This is fine until Chuck can help with the DNS records.

I am totally geeking out hearing this! The film technology they used is also quite fascinating.

@EduardoTSeoane It will be interesting to see how optimization works for you. With the size of your campus we may need to split the database from the FOG server to give the sql database more CPU time. We need feedback from large campuses like you have to help with performance tuning of FOG.

@Quazz Not sure from the top of my head. Thanks for finding this!! I will take a look later on.

@Wayne-Workman Sorry this has been without attention for a long time! Not only this topic but all the others:

https://forums.fogproject.org/topic/11868/how-to-change-colors-on-bandwidth-graph
https://forums.fogproject.org/topic/11999/bandwidth-line-colours
https://forums.fogproject.org/topic/6912/can-i-change-the-colors-of-the-tx-rx-graph

I played with the things mentioned in the other topics and figured that it seems to pick colors just by itself if we don’t force it to use our colors. When I remove the color scheme as described I get the following picture:

Please vote if you find this appropriate. Sure the more nodes you have the less obvious distinct colors there are. But from it’s still better than using a successive shade of whatever color you start from.

I’ve tested this in three different browsers on a Linux machine. I would imagine this working nicely on Windows and Mac OS browsers as well. What do you think @Tom-Elliott?