Bug 815412
Summary: | [UserPortal-gwtp] Differences between NewUserPortal v.s. OldUserPortal | ||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Product: | [Retired] oVirt | Reporter: | Avihai Shoham <ashoham> | ||||||||||||||
Component: | ovirt-engine-userportal | Assignee: | Einav Cohen <ecohen> | ||||||||||||||
Status: | CLOSED CURRENTRELEASE | QA Contact: | |||||||||||||||
Severity: | high | Docs Contact: | |||||||||||||||
Priority: | unspecified | ||||||||||||||||
Version: | unspecified | CC: | acathrow, dyasny, iheim, mgoldboi, tjelinek, ykaul | ||||||||||||||
Target Milestone: | --- | ||||||||||||||||
Target Release: | --- | ||||||||||||||||
Hardware: | Unspecified | ||||||||||||||||
OS: | Unspecified | ||||||||||||||||
Whiteboard: | |||||||||||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||||||||||
Doc Text: | Story Points: | --- | |||||||||||||||
Clone Of: | Environment: | ||||||||||||||||
Last Closed: | 2012-12-17 07:49:02 UTC | Type: | Bug | ||||||||||||||
Regression: | --- | Mount Type: | --- | ||||||||||||||
Documentation: | --- | CRM: | |||||||||||||||
Verified Versions: | Category: | --- | |||||||||||||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||||||
Cloudforms Team: | --- | Target Upstream Version: | |||||||||||||||
Embargoed: | |||||||||||||||||
Attachments: |
|
Created attachment 579587 [details]
newUserPortal
I decided to summary all differences between New userPortal and Old USerPOrtal in one bug. on top of what already filed (differences in RunOnce win) There are two more differences , between Old and New user portal , related to Edit VM 1) OldUsePortal has "High Availability" option while new user portal doesn't , see attached files 2)OldUsePortal has option of "Storage Allocation" in "Resource Allocation" menu , while New user portal doesn't , see attached files Created attachment 579590 [details]
Resource_OldUserPortal
Created attachment 579591 [details]
Resource_NewuserPortal
Created attachment 579592 [details]
HA_OldUserPortal
Created attachment 579593 [details]
HA_NewUserPortal
> 2)OldUsePortal has option of "Storage Allocation" in "Resource Allocation" menu
> , while New user portal doesn't
The problem here is, that the Resource Allocation can contain two different select boxes:
- Storage Domain
- Provisioning
while neither of them is available to the user (isDisksAvailable and privateProvisioning.isAvailable properties in the UnitVmModel).
In the new user portal, if it is not available, it is not shown at all (the same behavior is implemented also in webadmin). In the old user portal for some reason (I did not do a deep investigation) the "Storage Domain" is shown, but disabled and "Provisioning" is not shown at all.
Is the old user portal behavior correct? Should the "Storage Domain" be shown all the time, even if it is not available?
Missing linux boot options in Run Once dialog: fixed in patch: http://gerrit.ovirt.org/#change,3877 Missing High Availability in edit VM dialog: fixed in patch: http://gerrit.ovirt.org/#change,3878 verified
1)Missing linux boot options in Run Once dialog:
2)Missing High Availability in edit VM dialog:
are fixed on last dev hash commit b27eef27132cd152d58b6503324a9248374864ab
waiting for rnd to decide
>Is the old user portal behavior correct? Should the "Storage Domain" be shown
all the time, even if it is not available?
>Is the old user portal behavior correct? Should the "Storage Domain" be shown > all the time, even if it is not available? according to the comment in pre integration from ecohen (https://trac.qa.lab.tlv.redhat.com/trac/integration/ticket/649): "It doesn't matter that much whether the "storage allocation" part is hidden or disabled, as long as it is sync'd with the behavior in the web-admin." And it is in sync... Regarding last bullet "Storage Domain" in latest dev env hash commit 57397be91279fd856ce350418d0d5900cde108cf the UserPortal is sync'd with the behavior in the web-admin |
Created attachment 579586 [details] oldportal if you compare "run once" vm window ,between OldUserPortal v.s. NewUserPortal , you will see that new user portal is missing the option of "Linux Boot Options" see attached files Steps to Reproduce: 1.open Old user Portal 2.open New User Portal 3.Start RunOnce Expected results: We need to have the same design as the original user portal devel env last commit 0e4456026384a946e2df2a6b93d6d124829ea205