Posts made by Tom Elliott

What’s the image information in the GUI set for?

What’s the contents of the folder for this image? ls -lhat /images/Salledeformation

@jsch

This may be able to help:
https://wiki.fogproject.org/wiki/index.php?title=USB_Bootable_Media

https://forums.fogproject.org/topic/6350/usb-boot-uefi-client-into-fog-menu-easy-way
https://forums.fogproject.org/topic/6400/usb-boot-uefi-client-into-fog-menu-harder-way

The size does not mean the image is bricked as this get’s updated during deploy/capture (though there’s also a service running to try to keep the data updated as well.)

This is a Nice to have display, but is not an indication as to the status of your image.

Can you provide us with the error you’re seeing when it fails to deploy? That will give us a lot more information to work with. Also what’s the exact FOG Version you’re running? 1.5 does not tell us anything as we’re currently at 1.5.5 and dev branch is at 1.5.5.6 I believe. 1.5 just tells us you’re sort of updated, but we don’t know where too.

@fhrivers Do you guys have a web filter? Potentially a web filter blocking https://fogproject.org ?

I can download the files just fine so I’m not quite sure what’s going on and this is the best guess I can give.

Sorry if me message there sounded short, that was not my intention. I simply wanted to inform you of the plugin that would do exactly what you were asking.

There is some documentation on how to use the location plugin too, for the future.

Mind you, you can do this is “Central GUI Server->Storage Nodes about” layout, or really however you feel appropriate for your environment.

Location plugin will likely get an overhaul in the next few years (yes years) with more automating of how to select which storage node’s based on subnets/ip ranges, but for now it’s completely manual (and thus extremely granular too).

https://wiki.fogproject.org/wiki/index.php?title=Location_Plugin

From a purely technical standpoint, it’s actually fully possible to use FOG while maintaining machine’s with Secure boot, but it requires a lot of “customization” that our generic code base most likely would not easily be able to support (as it’s respective of each organization.)

@Lee-Rowlett Has done something like this, and while I’ve been kind of distant with minor chip-in’s here and there (Sorry Lee) I do still try to keep up with things so as to provide good and accurate information.

That said, if Lee’s willing to share his process, I’m sure you could have a setup where you wouldn’t require disabling Secure boot. Of course, I do think to get the setup initially done, you would need to set the machines up without secure boot, run the process, then go ahead and re-enable secure boot and frolic in the joy that is secure boot and FOG.

Does the manually registered client literally have has usb nic as it should really be has_usb_nic=1?

This wouldn’t necessarily fix the problem, but if you’re going to use the argument, it’d be best to use it as it was intended. Of course, once you make the correction, please try and see if that helps out.

You should not require downgrading CentOS in order to download the binaries for FOG.

The No such file or directory, itself, seems fine, as the first time it checks for it (and the binaries don’t exist) you will get the error, however the fact that it tried the 10 times and failed leaves me to think maybe you’re behind a proxy server?

In that case you’ll likely need to create a .curlrc file that provides the system with proxy information.

I’m only guessing based on the (very) limited information I’m seeing right now.

I’m also guessing you’re attempting to install FOG 1.5.5 from the master branch of git (or you downloaded a tar.gz?)

It’s called the location plugin. It’s been there since 1.0.0

@andrewhancock91 yes

@Dominique check the /var/log/php-fpm/www-error.log

If I were to guess, you have lack of memory. Just a guess though.

If you scoped you dhcp you should be able set each subnet to look at their respective fog servers for their boot files.

@Fernando-Gietz Would you mind matching up working-1.6 schema.php and the working/dev-branch schema.php?

From what I can tell, the changes between 1.5.x and 1.6 schema won’t impact the 1.5.x much from what 1.6 is adding/changing. The only part I see a little concern is the FOG_USER_VALIDPASSCHARS as in 1.6 its switching to a regex pattern vs implicit keys.

Then make this db changes from 1.5 to 1.6 at least be common.

Also, the recommendation for the max-bitrate issue is it already exists and is based on the Master Storage Node’s bitrate setting. The rexmit-hello-interval should also be added based on the Master storage node (as opposed to global values.)

This is simply because the global value means EVERYTHING that does multicast will use the same rexmit and bitrate settings. Having it per master storage node makes this much more dynamic and site specific.

I’ve added a globalized switch for allowing the admins to have the eye display/hide the password. By default the schema will set the “Enabling” to on (which is the current functionality.)

Unfortunately, I don’t know if this can be brought into 1.5.x

Not because we couldn’t add it, but because of the divergence between 1.5.x and 1.6

I’ve added the code to 1.6 base code however and tested that it was working properly. Hopefully we can have a 1.6 pushed out relatively soon.

@lwafflard

It would not be too difficult to add the --rexmit-hello-interval

I’m pretty sure the --max-bitrate can already be defined by setting the bitrate element of the storage node that will be handling the Multicast stream.

https://github.com/FOGProject/fogproject/blob/dev-branch/packages/web/lib/service/multicasttask.class.php#L460

Adding addition commands would be useful is think, though we need a common mechanism in order to break out the extra commands. (E.G. comma separated list to break out into an array of additional commands)

Should these commands be per Master Storage Node, or global?

Again, not hard to add, but need to know the best approach. For that I consult with @Sebastian-Roth and @Quazz (or anybody else who uses Multicast).

I’m leaning more towards per master storage node so each node can be configured independently (which is why we did the same thing for bitrate as bitrates would seem – to me – to be per node’s network capabilities.)

@george1421 I need to add,

the preceeding . is NOT just a way of saying run, it’s also a shorthand way of sourcing the file, the same as:

source mypostdlscript.sh

Basically, source means to bring the file in, similar to requiring other files in order to access different variables/functions that you may want separated from the purpose of the main running script.

@Sebastian-Roth I think it’s worth it. I can’t imagine a scenario where you’d be putting an image on an iscsi target.

The persistent groups plugin is most likely still working.

First, understand how it works.

It’s a simple trigger that’s generated but the trigger gets it’s template from a default host assigned to that group.
The template host name must be the same of the group’s name. In that host, you define your wanted group settings. Then, when you add a “real” host to the group, it will obtain the information in that group.

This encrypted form of the password has since been removed.

There’s multiple reasons for this, and the quickest reasoning was the encrypted form of the password contained both the IV and Passcode used to decrypt it in the first place. It looked confusing, but ultimately it had no better security than being in plain text. That and it added complexity to the base code, by having to encrypt, and before sending to the fog client being decrypted and reencrypted.

As the data is passed only between the client and the server in an encrypted format of which the encryption password changes every 30 minutes, having it encrypt->decrypt->encrypt didn’t add any value either.

This is intentional.

What version of fog are you running?

Are you still running 1.5.4? Would you be willing to update to at least 1.5.5 (or even more preferably the dev-branch as it has a bunch of other fixes in queue for what will become 1.5.6?)