SVN 6919 Snapin uploaded with wrong permissions

[Hanz]

Snapins are being uploaded without at least execution privileges as I have to chmod the files manually in /opt/fog/snapins. Also, snapin deployment is not waking computers (didn’t create thread since I didn’t know if it was supposed to honestly)

[Tom Elliott]

Snapin tasks should not wake computers because snapins are only handled by the fog client.

I’ll take a look at the permissions though.

[Hanz]

@Tom-Elliott in hindsight, that does make sense about the waking, but if it was scheduled for immediate deployment could it be made to run WOL, or possibly allow double tasking a single host if one is WOL

[Wayne Workman]

@Hanz That’s a feature request.

[Tom Elliott]

@Hanz What do you mean by double tasking? I ask this because imaging tasks (other than download – without snapin, and uploads) automatically creates the snapin tasking as well. The other way around, could be done, just needs logic to be added to make the adjustment. Snapin Only taskings (Single or all) do not have any requirement for OS to be booted forcibly.

Adding WOL for Snapin taskings is actually very simple, because I can just tell the package generation to not immediately return at that point, at which point it would cause WOL (or I can just add the WOL snippets into the snapin generation portion).

[Wayne Workman]

@Tom-Elliott I’d suggest making it a check-box. “Wake host for task”

[Hanz]

@Tom-Elliott maybe better idea to add option under snapin mgmt…if you try to task snapin, and then Wol, won’t work already taking host. WOL then snapin would, but hard to catch all computers before they boot to technically immediately deploy them.

Wayne beat me typing.

[Tom Elliott]

@Hanz All tasks are checked and sent WOL (as set/needed) via the FOGScheduler service. So if one WOL fails to run, the next check should start it.

[Wayne Workman]

@Tom-Elliott said:

@Hanz All tasks are checked and sent WOL (as set/needed) via the FOGScheduler service. So if one WOL fails to run, the next check should start it.

Is that new? I don’t want computers that are off just turning on for a snapin… it can wait lol. That said - I would like the option of WOL for snapins.

[Tom Elliott]

@Wayne-Workman The FOGScheduler service has been checking for WOL to occur for quite some time, though it was only implemented (I believe) in the trunk versions. Snapin tasks do not generate WOL packets anyway. In either case, it doesn’t hurt anything either (or shouldn’t at least).

[Hanz]

@Tom-Elliott sry to get ahead on the feature requests, I’ll start checking that section first. And I second the idea of at least an option to check that to make it generate one.

[Tom Elliott]

@Hanz I’ve added a checkbox that enables the users to allow/disallow WOL requests with the exception of a wake up tasking (because that would seem a rather poor choice…let’s do a WOL Task, and let’s not allow it to do WOLL).

[Wayne Workman]

@Tom-Elliott I didn’t know you can allow/disallow options so easily… How about removing the “restart after completion” checkbox for snapins being deployed? The snapins area has the correct checkbox for rebooting after completion.