@CWDS Not sure why it would go through the interfaces twice.

Anyhow, if you want to change the behavior for iPXE you want to look into building your own iPXE binaries and play with the ipxe script: https://github.com/FOGProject/fogproject/blob/master/src/ipxe/src-efi/ipxescript

For iPXE building you wanna read here: https://wiki.fogproject.org/wiki/index.php?title=IPXE#Compile

It’s been a while since I wrote that code and I’ve been working hard on trying to get 1.6 to a more functional state (which I believe it’s mostly there now.)

Of note, while you can tie into the common ajax code sitting within for setupTimeoutElement and submithandlerfunc, the common thing to be noted is that you can have your JS code do whatever you need. Those methods are available, but there’s no 100% dedication to using it. Use it where you can, but it’s not a requirement.

The js code get’s loaded automagically in 1.5 via node and sub in the get request.

So let’s say you wanted js code to alter the list page for some reason. Your plugin node code would be say exampleplugin. You would simply need a file named: fog.exampleplugin.list.js (file names are always: fog.<node>.<sub>.js)

Hopefully this makes sense.

So in keeping with that file scheme, common files I can think of for a plugin named exampleplugin would be:

fog.exampleplugin.js //base js for all exampleplugin node items. fog.exampleplugin.list.js //exampleplugin's list page. fog.exampleplugin.add.js //exampleplugin's create/add item page. fog.exampleplugin.edit.js //exampleplugin's edit item page.

While I’m sure this doesn’t answer any of your questions, it should help with getting something functional.

You can use other plugin’s to help in the understanding of the js files too. A common one I like to use that interacts with both groups and hosts is the location plugin. This should give a pretty good understanding of what to do, and how to do it. If you still have questions please ask and try to be detailed in exactly what you’re looking for.

@Tom-Elliott ok thank you. We are starting with doing only some basic things, so I will just continue to get it up and running on 1.5.x.

Right now, I am using the doxygen generated focdoc/ folder and mostly some examples in other plugins. Sometimes a bit tricky, but IMHO no need to generate the files for 1.5

@klaus-jauk I understand for $osid and driver packs. In the case of drivers, using FOG’s built in $osid is not a problem, because for Win10 for example a win10 drive works across all win10 platforms. The same for Win8 and so on.

Here is an idea: What I see is at issue is the KMS key where you think you need custom $osid values. There is a key management plugin for FOG. Where you load the KMS/MAK keys into a key table and then associate that key with a host. I don’t know if that will solve your problem with kms keys or not, but the resultant link key should show up in hostproductkey so you don’t need to do anything special in the post install scripts.

The issue I see with creating custom $osid values is that FOG uses that $osid values internally when creating the disk partitions and how to deal with boot block. If you create your own $osid values then the internal programs that look for $osid (9) for example would not work because it would see your custom $osid value. Now of FOG internally would mask off (only look at) the lower 8 bits of $osid for FOG’s internal use then you could do what you want by creating custom IDs with the upper 8 bits of that $osid value.

@Fernando-Gietz said in Use an external database:

My FOG version is 1.5.5 for working branch, the last version.

So you don’t have the fixes I pushed to dev-branch. We might consider merging your code changes form working to dev-branch soon. This way you can make use of all those changes.

@Tom-Elliott What do you think?

@Fernando-Gietz said in Performance Monitoring tools:

We use Nagios to monitoring the server status but not use any plugin to see the activity of MySQL or Apache. Do you use any plugin to monitoring these services?

We use plugins for both mysql and apache monitoring. But I feel I must make a distinction between performance monitoring and service level monitoring. We do service level monitoring, in that we only check if the service is functional (what ever that means like mysql connections, or basic http queries) as well as critical service parameters. We dont monitor things like inbound network traffic for sql server, because its really not important to know how well the sql server is functioning (I know you can make an argument either way). As you know nagios is just a go/no-go monitoring system. If you couple that with mrtg or such then you can get trending over time. That is why we really like Centreon because it has nagios coupled with a few other opensource softwares in one package. You can get that trending over time of the actual recorded value as well as the go/no-go status.

Performance monitoring is collecting a large amount of metrics to understand how the system as a whole is functioning, not just the critical bits. You could use performance monitoring environment for forensic investigations over time to understand how metrics have changed. You may be not so interested in the individual services here.

So when looking for a monitoring tool, you need to decide what is important about that device/service. Why does it exist? What function does it perform? What would happen if that service disappeared? That is how you should decide what to monitor regardless of the tool.

For example: Lets say you wanted to monitor your FOG server for both availability and performance metrics. What do we know about your FOG service? Well it runs on linux, it uses a tftp server, apache server, a ftp server, and nfs.

So for linux what is important?

Is it reachable on the network? How utilized is the CPU? How much free memory is there? How much free disk space is there on the /images disk? Are the tftp, http, ftp services running in memory? (notice I didn’t mention if they were working only if they are running in memory)

For the tftp server what is important

Is it listening on port 69? Does it respond to a file size request?

For the http server what is important?

Is it listening on port 80 Does it respond to http requests? If your site uses php does it respond properly to a php page call? What is the percentage of CPU does the apache service use?

And so on for monitoring. The point is to understand what you want to inspect before you pick the tool. Then find the tool that fits your budget and time you are willing to invest in setting it up.

At my brothers company they use a product called WhatsUp Gold and they loved it before they moved to PRTG which they now love more. But they had the budget but not much time to build it themselves. In my case I’ve been running nagios monitoring servers on and off since 2000. I don’t have a problem spending time to build new installs.

@ragnurenson so, I’ve just tested after applying the commited changes and everything works fine! Thank you for pointing out the github commit and thanks @Fernando-Gietz for the awesome work!

If I can make a suggestion, I’d say it would be nice to have that search filter implemented in “List All Hosts” screen on Active Tasks!

I made the changes and did a test run, dev-branch completely passed.

Unless, of course, you’re trying to make it core usable? But the only time this would be viable would be if LDAP plugin is in use. Of course other plugins may want to make adjustments here as well. I need to think on this a little bit.

Thanks to Wayne I had access to the RHEL 7 machine for a quick test and seems like we hit it with the latest fix. Installer went through like a charm. So RHEL is back in the race I suppose.

@Sebastian-Roth Thanks for you answer, i’ll try next time.

Sincerely.

Jérôme

@Doctrg You should be able to go straight from 1.3.5 to 1.5.4 I think. Make a full DB dump on the old server, install mysql on the new one by hand (yum install mysql mysql-server), import DB dump and then start the FOG 1.5.4 installer. When it asks you to open the web interface go ahead and it should upgrade your database structure - usually does without an issue.

Not saying there can’t be anything going wrong but mostly this is going fine. As you still have the old server (or at least a full backup of machine and DB), you can always give it a try. Shouldn’t hurt.

@tom-elliott we do all the installing manually… Could you please elaborate the steps…

Like @Tom-Elliott said, the initial postdownload script always runs. However, you can use CASE or IF statements to either call a function or open another script. Here is my current postdownload script that I got from one of @george1421 and his wonderful driver injection scripts found here

#!/bin/bash . /usr/share/fog/lib/funcs.sh [[ -z $postdownpath ]] && postdownpath="/images/postdownloadscripts/" if [ $img == "Win7BaseVM" ] || [ $img == "Win10BaseVM" ] ; then case $osid in 5|6|7|9) clear [[ ! -d /ntfs ]] && mkdir -p /ntfs getHardDisk if [[ -z $hd ]]; then handleError "Could not find hdd to use" fi getPartitions $hd for part in $parts; do umount /ntfs >/dev/null 2>&1 fsTypeSetting "$part" case $fstype in ntfs) dots "Testing partition $part" ntfs-3g -o force,rw $part /ntfs ntfsstatus="$?" if [[ ! $ntfsstatus -eq 0 ]]; then echo "Skipped" continue fi if [[ ! -d /ntfs/windows && ! -d /ntfs/Windows && ! -d /ntfs/WINDOWS ]]; then echo "Not found" umount /ntf >/dev/null 2>&1 continue fi echo "Success" break ;; *) echo " * Partition $part not NTFS filesystem" ;; esac done if [[ ! $ntfsstatus -eq 0 ]]; then echo "Failed" debugPause handleError "Failed to mount $part ($0)\n Args: $*" fi echo "Done" debugPause . ${postdownpath}fog.deletelog . ${postdownpath}fog.drivers #. ${postdownpath}fog.ad umount /ntfs ;; *) echo "Non-Windows Deployment" debugPause return ;; esac fi

You can see that I have an if statement at the beginning to only run his driver injection script if the image name is one of my golden image VM’s.

Removed. Well, kept the surface-pro-4 matching element, but just removed the 7156 portion.

@maikbat by default the api access is disabled. Check fog configuration ->fog settings->API Settings and enable

@tom-elliott thank you so much! You are a rockstar. I look forward to 1.6!

Thank you 🙂 That worked great!