Topics created by GeorgeBells

@GeorgeBells

This depends on how you downloaded fog in the past.

You could:

cp -r /path/to/fogproject/installation/packages/fog/lib/plugins/* /var/www/fog/lib/plugins/

Otherwise you could download it with:

git clone https://github.com/fogproject/fogproject cd fogproject/packages/web/lib cp -r plugins/* /var/www/fog/lib/plugins/

Hi

I’ve just tested this an it worked without issues - Thank you. I will try to post the contents of those files shortly. My question is, is this new init file good to be made the default somehow?

Hello,

I am using fog to manage a data center deployment consisting of over 1000 servers.

I am replying here as the UX feedback provided by @GeorgeBells here perfectly sums up issues I’ve been having as well.

If a feature request / ‘fix’ per details referenced above is NOT possible or planned, then I sincerely urge the dev team to consider allowing users to assign Snapins directly to images.

All of my equipment is of a similar spec, and the image I flash to them contains pre-configured FOG client as well as auto-setup scripts to configure UUID-based values on first boot.
All of my “snapins” are entirely image-specific by design.

I would like to quick register all new equipment, immediately flash the same specific image, and then deploy the same snapin every time.

Thank you - That is helpful. It seems the persistent groups plugin works more along of the line of what I expected from the default groups.

It seems then that it is not possible to have snap-ins defined as defualt, associated to an image or ALL hosts regardless of groups? Perhaps that goes against what a ‘snap-in’ is reallly intended for…