add boot menu to deploy associated image

[Wayne Workman]

The image assigned to the host is already pre-selected. If no key is pressed, the timeout will run down and the assigned image is used.

Changing this would require a lot of code changes. Perhaps that could be worked into the new access control plugin @Fernando-Gietz ??

[george1421]

@Wayne-Workman It more to the point, if I set a specific image for a system, I don’t want someone picking something else (maybe a dev image that hasn’t been approved yet). There are other use cases, but that is the most common.

[Wayne Workman]

@george1421 I think such things should be enforced by rules, policy, communication, and punnishment - rather than with code, personally.

Not up to me though. I would bet that @Fernando-Gietz could probably do something in the access control plugin for it.

[x23piracy]

Why should only show associated image require a lot of code changes? @Tom-Elliott @Wayne-Workman
Is there no easy way to say make everything else not showing up in that list without association?

I really would also like to have that option.

I have some notebooks out there where the employees reset to a default image again when they make test installation of our own software. Actually they can pick up every image that is on the node, and i like to prevent them from choosing what ever they want.

Regards X23

[Tom Elliott]

This isn’t about the difficulty in adding this, that’s simple. It’s we keep getting people who wanted one thing then later, it seems, they want it back to how it was.

Deploy image use to do exactly what’s wanted here until it was requested to allow the ability to select their own image. It was requested so often that I made the change. Now we’re here.

[Tom Elliott]

While it’s not a perfect system, I’ve moved this into Feature requests and asked as a question and solved it.

Why did I solve it? Because I’ve adjusted to code to allow users to decide if they want a list of images or not. A new item in FOG Settings under FOG Boot Settings will allow you to display the images as a list or not.

The way the code is laid out, if this box is checked (it is enabled by default now), it will present a list of images as you see today. This list will be preset on registered, or non-registered hosts.

If this box is not checked, there will still be a “list” but it will only contain the device’s assigned image and return to menu items. If the host is not registered, or does not have an image associated to it, it will present you with an error. The error will be:

Host is not valid, host has no image assigned, or there are no images defined on the server.

Hopefully this appeases everybody.

[x23piracy]

@Tom-Elliott so please give us the option to choose in settings what we need.

[george1421]

@Tom-Elliott Sweet that will solve both requests

[george1421]

@x23piracy Tom said in add boot menu to deploy associated image:

A new item in FOG Settings under FOG Boot Settings will allow you to display the images as a list or not.

It sounds like there is now a global option to do this.

[Tom Elliott]

@george1421 I should clarify, there “will be” the ability to make this choice when I push up the next RC.

If you all want to use this now, please install the working branch.

[george1421]

We all must understand the impact of turning on (or off depending on the logic used) this function. With the display only defined images enabled you will not be able to do a quick image on an unregistered host. Because an unregistered host will not be in fog so there will be nothing to display in that quick image menu. If you turn this feature off then you will be able to quick image any unregistered system, but you will also see all possible images when you try to quick image a registered host.

This is a handy feature as long as you understand the caveats of it being enabled/disabled.

[Tom Elliott]

@george1421 That’s precisely what my logic flow is.

If the image list is enabled, show a list of all defined images. This will work for unregistered and registered hosts. If a host is registered, the associated image will be selected for the user and will automatically begin imaging after the PXE Timeout period.

If the image list is disabled, it will only present a registered host it’s associated image and will begin imaging after the PXE Timeout period. If a registered host has no image associated, it will print the error. If an unregistered host selects the deploy image item, it will print the error.

In ALL cases (On or off) if you have no images defined it will print the error.

[x23piracy]

@Tom-Elliott don’t slap me but where exactly is the option located?

[Tom Elliott]

@x23piracy

@Tom-Elliott said in add boot menu to deploy associated image:

A new item in FOG Settings under FOG Boot Settings will allow you to display the images as a list or not.

[x23piracy]

@Tom-Elliott thanks, tested it’s working as expected. Thank You!

[lebrun78]

@Tom-Elliott
I checked, but I get this message,
“Host is not valid, host has no image assigned, or there are no images defined on the server.”
But I have a image assigned to this host, win10-3

[Tom Elliott]

@lebrun78 Then something is wrong with your configuration.

The message will only happen in the cases I described.

[lebrun78]

@Tom-Elliott
Trying to found the source of the problem, I’ve just created a new image, capture it from win10-3.

After reboot, I have always the same error.
In log I have the no error at capture

Where should I have a look ?