Posts made by Wayne Workman

One of many examples of people getting mixed up by this: https://forums.fogproject.org/topic/12810/after-installing-fog-i-seem-to-get-locked-out-of-ubuntu

@maouu This tool will re-number your snapin IDs to start at 1 again. Normally, this is not used when you only have one snapin though… It’s normally used when you have created & deleted hundreds of snapins over years, and want a more sane numbering.
https://github.com/FOGProject/fog-community-scripts/tree/master/RenumberSnapinIDs

This tool will help you along: https://github.com/FOGProject/fog-community-scripts/tree/master/updateIP

I think the way to provide the last successful logs is links, and just keep all these dashboards, and to use html includes with JS.

This dashboard is being hosted from an s3 bucket and has no ability to do server side processing. Thus, it’s all gotta be in links or JS.

https://www.w3schools.com/howto/howto_html_include.asp
I’m thinking another column between Install Duration and Install Output that links to the dashboard where that particular test was last successful. And overall, index.html will just load up the latest dashboard using JS.

@Sebastian-Roth 2nd round going.

For CentOS taking a long time is probably two reasons.

• The installer does tons of stuff to get FOG working on CentOS 7.
• The CentOS 7 instance type is t2.micro. All others are t3.micro. The t3 series is newer hardware, more ram & cores, and is cheaper to run. I had to use a t2.micro with CentOS 7 because CentOS’s official AMIs do not support the advanced networking hardware that the t3s use.

@Sebastian-Roth Going, should be done in around 20 minutes.

This link is the original fog testing dashboard.
This dashboard was created to help identify problems with the FOG installation process early on, so they can be fixed before users experience them. This dashboard has been generally UP for about two years now. It’s served the FOG Project well.

However, the old dashboard was written mostly in BASH and is a mess. It requires custom setup, custom snapshots, hand-spun virtual machines, and a tremendous amount of compute resources and time. While the code that this dashboard uses is completely open source and available, due to the complex setup, nobody has bothered using it.

Thank you, old dashboard, You’re retirement party is coming up soon.

Hello new dashboard!

The new dashboard has several significant improvements over the old one. Notably:

• Mostly written in Python.
• 100% AWS based.
• 100% of the infrastructure is built via Terraform.
• Includes Red Hat Enterprise Linux 7 testing.
• Orders of magnitude faster to run.
• Makes logs available regardless of success status.
• New logs, and output - such as stdout from the fog installer, patching stdout, and php-fpm logs.

The new code base has been made available for all here and includes instructions for you to set this up for yourself, should you decide to run the FOG Installer tests yourself.

Features that existed in the old dashboard but were done away with (for now) are:

• Streak counts
• Log history.
• FogProject slack channel posts.
• Older OSs.

I plan to make testing history available in the future.

For a while, I plan to run the old tests and new tests in parallel until I’m sure the new tests are stable, bug free, and ready to be relied on. Then, the old tests will be shut down for good.

@The-Dealman Read through this, might help: https://forums.fogproject.org/topic/11868/how-to-change-colors-on-bandwidth-graph

You need to recapture. Preferably to a new image so that if something goes wrong, you still have the old one.

@The-Dealman I don’t think it’s currently possible through the web UI. Of course you could take a stab at modifying the code so that certain things are certain colors.

@AndrewG78 said in Multiple FOG servers in one network:

I have no access to DHCP server. Company’s policy.

Then request changes formally, in writing. If there’s an existing ticketing system, use that. State what you need, and why you need it. State the benefits. And be polite and respectful.

When you’re trying to automate bootstrapping a Ubuntu server with apt-get update;apt-get -y dist-upgrade and it still stops to ask you questions…
https://postimg.cc/Z9TFskWk

@Sebastian-Roth Will the installer’s -y switch ‘just do it’ ? The automated tests depend on this option.

EDIT: Nevermind, I see you have it taken care of.

@6rilT said in Permissions management server side:

could not find it on the wiki page

What wiki page?

I don’t know what you’re looking at, but the access control plugin is absolutely available.

@6rilT You would install the accesscontrol plugin, and then configure it. Here’s information on it: https://forums.fogproject.org/topic/9624/control-access-plugin/7
I don’t k now if @Fernando-Gietz completed the Site control plugin, but information on that is here: https://forums.fogproject.org/topic/9902/site-plugin

If you are not familiar with fog’s plugins, you have to enable the plugin system in FOG Configuration - it’s just a checkbox, click save. You’ll get a new item in the fog ribbon for plugins. From there, you can install any of the available plugins.

@Sebastian-Roth Debian 9’s log appears here: /var/log/php7.0-fpm.log
I’m going to have to match it like /var/log/php*-fpm.log and hope that does it.

@phil-dosi said in FOG Server Requirements:

the worry comes over the response times with the FOG master

Some of the statements in my response addresses that, and I can help you accomplish it if you like.

@Sebastian-Roth Not quite yet…

It wanted to install these:
bc curl gcc gcc-c++ genisoimage gzip httpd lftp m4 make mod_ssl mtools mysql mysql-server net-tools nfs-utils php php-bcmath php-cli php-common php-fpm php-gd php-ldap php-mbstring php-mysqlnd php-process syslinux tar tftp-server unzip vsftpd wget xinetd xz-devel

These weren’t available:

 * Skipping package: php-bcmath................................(Does not exist)
 * Skipping package: php-fpm...................................(Does not exist)
 * Skipping package: php-mbstring..............................(Does not exist)

Here’s the log:
0_1543782561152_fog_error_1.5.5.1.log
There wasn’t an apache or php-fpm log. I ran this and there was no output: find / -name *fpm*

@Sebastian-Roth said in Fog Installer - Distro check:

Can you possibly add another log file? Quite often those errors will only show up in /var/log/php-fpm/www-error.log… possibly also /var/log/php-fpm/error.log

I’ll add these logs to the new system. I don’t want to break the old system as it’s working right now and all the bash it uses is somewhat complicated.