Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1147682

Summary: Disks are the only object to use Alias instead of Name
Product: [oVirt] ovirt-engine Reporter: Matt Reid <mreid>
Component: Frontend.WebAdminAssignee: Tal Nisan <tnisan>
Status: CLOSED WONTFIX QA Contact: Aharon Canan <acanan>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: ---CC: amureini, bugs, gklein, lsurette, rbalakri, Rhev-m-bugs, scohen, tnisan, yeylon, ykaul
Target Milestone: ---Keywords: UserExperience
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-04-11 12:16:25 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Storage RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Disks table none

Description Matt Reid 2014-09-29 20:33:40 UTC 
Description of problem:
In the Disks table, Disks use an Alias. Storage uses a Domain Name. The other 9 tabs use Name.

Do Disks need to use Alias rather than be consistent with everything else and use Name?

Version-Release number of selected component (if applicable):
3.4
Comment 1 Matt Reid 2014-09-29 20:36:22 UTC 
Created attachment 942490 [details]
Disks table
Comment 2 Tal Nisan 2014-09-30 07:59:13 UTC 
If I recall correctly disks also used to have a name but it was removed so now we have the alias and description, Einav any recollection about why we decided to stick with the alias?
Comment 3 Einav Cohen 2014-10-01 23:47:50 UTC 
(In reply to Tal Nisan from comment #2)
> If I recall correctly disks also used to have a name but it was removed so
> now we have the alias and description, Einav any recollection about why we
> decided to stick with the alias?

AFAIR:

disks used to have an "automated" name (e.g. "Disk1", "Disk2", ...) but it was not unique across the system, as it didn't have to be (Disk didn't used to be a standalone object like today). 

After making the Disk a standalone object, we wanted the Disk to have a human-readable identifier, but something that will (most likely) be unique across the system. we could not use the already existing "Name" since it contained very non-unique values (as I mentioned earlier: "Disk1", "Disk2", etc.). 

We could not just change the "Name" values for the entities in an upgrade-script or similar - obviously we had to retain data integrity / backward compatibility.
 
Therefore, we had to add a new property that would be used as the human-readable Disk identifier that will be (more or less) unique across the system (unlike "Name"), and we named it "Alias". 

In 4.0 (in which we will be allowed to break backward compatibility), we may simply rename "Alias" to "Name" and get rid of name; but before that - we need to keep "Name" and "Alias" as they are today (I am referring here to the REST API as well, not only the GUI - properties names in the GUI and in the REST API should be consistent).
Comment 4 Allon Mureinik 2015-06-23 14:36:36 UTC 
As per comment 3, this is not a 3.6.0 item, due to backwards compatibility requirements.
Comment 5 Red Hat Bugzilla Rules Engine 2015-11-30 20:51:01 UTC 
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.
Comment 6 Allon Mureinik 2016-04-11 12:16:25 UTC 
Closing old bugs. If there's a real business case for this BZ, please reopen and explain it.