View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
1081 | RackTables | default | public | 2013-11-22 12:39 | 2013-12-18 03:57 |
Reporter | cyb3rwulf | Assigned To | adoom42 | ||
Priority | normal | Severity | tweak | Reproducibility | always |
Status | closed | Resolution | fixed | ||
Product Version | 0.20.5 | ||||
Target Version | 0.20.6 | Fixed in Version | 0.20.6 | ||
Summary | 1081: Object tab_default "mounted to" (Row/Rack or Container) appearance of Objects which are physical and virtual mounted | ||||
Description | Physical Servers which are hypervisors holding a cluster appear to be mounted in that cluster instead to be mounted in their rack. Thats not very useful if you want to do a quick lookup where there are physically mounted. I understand that it is not so easy to say for all users which setup is usefull, because that depends on the personal usecase. So I've got the following idea: How about grant the possibility to set one "mounted to" entry for an object as some kind of "$master", maybe by using a drop down menu or something like that? This "$master" should be shown then in the "Row/Rack or Container" column in the objects tab_default. As default value you could e.g. use the "first added" mount entry. | ||||
Tags | No tags attached. | ||||
cyb3rwulf, As I understand your case, there are Server objects mounted in a rack. A VM Cluster acts as the Container for one or more servers. In the list of Objects, the "Row/Rack or Container" column displays the VM Cluster, whereas you would like the Row/Rack to be displayed instead. I'll begin with some background information. The Row/Rack/Container column is currently calculated in a sub-optimal way (see $SQLSchema in database.php). It is legitimate for an object to have multiple containers and be mounted in multiple racks, yet this column only displays one piece of information. There are at least three possible ways to approach the problem you described. 1. Use your suggestion, adding a field which allows you to specify which mount point or container is displayed (master). 2. Change all applicable code in order to accommodate objects which have multiple containers and/or are mounted in multiple places. Display all data in an elegant way and ensure that query performance stays at a reasonable level. 3. Continue to return a single container and single mount point for each object, but change the logic that determines which piece gets displayed on the object listing page. If the object is mounted, display the first element of Row/Rack data. If it is not, show the first container. If it is unmounted and has no container, display 'Unmounted'. The third option is the easiest, and can be achieved by changing the if/elseif order in the renderDepot() function. Options 1 and 2 cover more scenarios but are more costly in terms of complexity, development time, performance or a combination. Please comment. |
|
The third option may work for now. But I think it won't be so bad to keep the other options in mind for future development steps. | |
The fix was easier than expected. The list of objects will now display all containers and racks for each object. | |
Date Modified | Username | Field | Change |
---|---|---|---|
2013-11-22 12:39 | cyb3rwulf | New Issue | |
2013-11-22 17:56 | adoom42 | Note Added: 0001963 | |
2013-11-22 17:56 | adoom42 | Assigned To | => adoom42 |
2013-11-22 17:56 | adoom42 | Status | new => feedback |
2013-11-24 12:26 | cyb3rwulf | Note Added: 0001965 | |
2013-11-24 12:26 | cyb3rwulf | Status | feedback => assigned |
2013-11-24 22:48 | adoom42 | Note Added: 0001973 | |
2013-11-24 22:48 | adoom42 | Status | assigned => closed |
2013-11-24 22:48 | adoom42 | Resolution | open => fixed |
2013-11-24 22:48 | adoom42 | Fixed in Version | => 0.20.6 |
2013-11-24 22:48 | adoom42 | Target Version | => 0.20.6 |
2013-12-18 03:57 | adoom42 | Relationship added | related to 1115 |