Improve Control Simulation Page

[DavidResende0]

Currently the Policy Simulation page (i.e. Compute -> Virtual Machines/Instances/etc) is not working correctly and the plan is to remove it entirely. However, there are some features that would be useful to move over to the Control -> Simulation. On top of this the page needs to eventually be converted to react and could also use a redesign.

This issue catalogs how the Policy Simulation page looked and opens a discussion on how the redesigned Control Simulation page should function.

Policy Simulation Page:

Current Control Simulation Page Design:

[DavidResende0]

Proposed Design Changes:

• Use the Current Policy Simulation Button to redirect to the Control Simulation page and in the page pre-load all the required fields needed to simulate that vm/instance/etc.
  

• The above change would also require that the Control Simulation page allowed users to select multiple vms/instances at once to test (change Single VM/Instance option to multiselect).

• Allow the user to add/remove policies from individual/groups of vms/instances within the Control Simulation page (would need ux redesign)

• Change tree view into a table format

[Fryguy]

Tree view actually might be ok, but we need to update the look and feel and present it better.

Additionally, we may want add a way to filter VMs by assigned policy profiles.

[jrafanie]

Tree view actually might be ok, but we need to update the look and feel and present it better.

Additionally, we may want add a way to filter VMs by assigned policy profiles.

Yeah, we already have event and target selection in the control simulation page. That page assumes policy profiles are assigned. From a UX perspective, you might want to select an event and a specifc policy profile to see which vms/instances pass/fail compliance. We probably still need to filter by host/provider or you could try to run RSOP on thousands of things.

[miq-bot]

This issue has been automatically marked as stale because it has not been updated for at least 3 months.

If you can still reproduce this issue on the current release or on master, please reply with all of the information you have about it in order to keep the issue open.