| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
|
@borisstoyanov a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress. |
Sorry, something went wrong.
|
Packaging result: ✔centos6 ✔centos7 ✔debian. JID-2668 |
Sorry, something went wrong.
|
@borisstoyanov a Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has been kicked to run smoke tests |
Sorry, something went wrong.
There was a problem hiding this comment.
LGTM, manually checked the restriction logic and the readonly setting
Sorry, something went wrong.
|
@shwstppr please fix conflicts and rebase against latest master |
Sorry, something went wrong.
Done @rhtyd |
Sorry, something went wrong.
|
@shwstppr a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress. |
Sorry, something went wrong.
|
Packaging result: ✔centos6 ✔centos7 ✔debian. JID-2754 |
Sorry, something went wrong.
This change allows instance Settings tab to be visible but inaccessible when instance is running. A warning is shown when user tries to access Settings for a running instance and tab content is greyed out. It also allows some admin defined instance settings/details to be made static for user. User will be able to see them in instance settings tab but cannot change their values as action buttons are disabled and greyed out. This can be achieved by providing a comma-separated list details for global settings key 'user.vm.readonly.ui.details'. A new value 'readonlyuidetails' has been added in UserVMResponse for UI manipulate editing functionality of settings/details. Signed-off-by: Abhishek Kumar <abhishek.mrt22@gmail.com>
|
Rebased to latest master @DaanHoogland @rhtyd |
Sorry, something went wrong.
|
@DaanHoogland a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress. |
Sorry, something went wrong.
|
Packaging result: ✔centos6 ✔centos7 ✔debian. JID-2758 |
Sorry, something went wrong.
|
@DaanHoogland a Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has been kicked to run smoke tests |
Sorry, something went wrong.
|
@rhtyd a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress. |
Sorry, something went wrong.
|
Packaging result: ✔centos6 ✔centos7 ✖debian. JID-2768 |
Sorry, something went wrong.
|
Trillian test result (tid-3574)
|
Sorry, something went wrong.
@shwstppr you wrote about a comma seperated list... do you have an example for that? |
Sorry, something went wrong.
|
I apologise for merging before rename to remove the [WIP] tag. |
Sorry, something went wrong.
|
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Description
Problem: Instance settings tab is visible only for stopped VMs but hidden otherwise. This creates confusion as users may not know that VMs need to be stopped to access settings page. Some VM details need to be read-only for the user.
Root Cause: The UI Code hides the settings tab for VMs that are not in stopped state. Instance setting tab should always be visible, but only changeable when VM is stopped. Required instance details are not read-only for the user.
Solution: The settings tab is now always visible for VMs. If VM is not in the stopped state, no interactions are allowed in the settings tab view by greying out its content and a popup is shown to advise users for stopping the VM. VM details can be made read-only in UI for the user using “user.vm.readonly.ui.details” which accepts a comma-separated list of details. For user, read-only details will be shown in the settings tab in UI but the action button for them will be disabled and greyed out. Admin can still update such details.
Types of changes
Screenshots (if appropriate):
Snapshot when VM is stopped.



Snapshot when VM is not stopped but Settings tab is clicked and Popup appears
When popup is dismissed
VM setting/detail made read-only

How Has This Been Tested?