Send Netdot-devel mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
https://osl.uoregon.edu/mailman/listinfo/netdot-devel
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Netdot-devel digest..."
Today's Topics:
1. [Netdot - Feature #803] (In Progress) Rack management
([email protected])
2. [Netdot - Feature #803] Rack management ([email protected])
----------------------------------------------------------------------
Message: 1
Date: Thu, 29 Jan 2015 11:16:28 -0800
From: [email protected]
Subject: [Netdot-devel] [Netdot - Feature #803] (In Progress) Rack
management
To: [email protected], [email protected]
Cc: [email protected], [email protected],
[email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8
Issue #803 has been updated by Carlos Vicente.
Status changed from New to In Progress
Anton,
I can see the flexibility in the additional tables for location options. I
think it's similar in concept to what I did with DeviceAttr and IpblockAttr.
The downside of that is when trying to manipulate data (a simple search becomes
a complex select statement, for example). But maybe that's the price to pay.
The key would be to reduce that complexity for the user, with code.
Regarding the constraints for parent/child relationships, perhaps the easiest
would be to put that in the config file. For example:
<pre>
LOCATION_TREE_CONSTRAINTS => {
"rack" => [ "closet", "room", "cage" ],
"room" => [ "building", "site" ],
...
}
</pre>
This means: A rack can exist within a closet, a room or a cage, but nothing
else. That way the user can manipulate their own constraints, and we keep the
database simple.
----------------------------------------
Feature #803: Rack management
https://osl.uoregon.edu/redmine/issues/803#change-3269
Author: Robin Johansson
Status: In Progress
Priority: High
Assignee: Carlos Vicente
Category: DeviceManagement
Target version: 1.1.0
Resolution:
Would be useful if it was posble to manage rackspace in netdot, similar to what
racktables offer.
--
You have received this notification because you have either subscribed to it,
or are involved in it.
To change your notification preferences, please click here:
http://osl.uoregon.edu/redmine/my/account
------------------------------
Message: 2
Date: Thu, 29 Jan 2015 11:56:02 -0800
From: [email protected]
Subject: [Netdot-devel] [Netdot - Feature #803] Rack management
To: [email protected], [email protected]
Cc: [email protected], [email protected],
[email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8
Issue #803 has been updated by Carlos Vicente.
I agree with John's comment above about supporting front/back options.
Taking that and the location thing into account, we would have:
h2. Schema
* Create a new "rack" table with the following columns:
** name (text)
** size (int) default: 42 (in config file)
** location_id (bigint, fk)
** num_direction (bool)
** info (text)
* Remove location columns from device table (site, room, rack)
* Add the following columns to the asset table:
** rack (bigint, fk)
** rack_vert_pos (int) - (e.g. 1-42)
** rack_horz_pos (int) - values: (1=front, 2=back, 3=both)
* Add the following column to Product:
** ru_size (int)
I see that RackTables, for example, has a "interior" horizontal position. I
guess that could be useful in some cases, but I'm afraid of complicating the
schema any further.
As always , feedback welcome.
----------------------------------------
Feature #803: Rack management
https://osl.uoregon.edu/redmine/issues/803#change-3270
Author: Robin Johansson
Status: In Progress
Priority: High
Assignee: Carlos Vicente
Category: DeviceManagement
Target version: 1.1.0
Resolution:
Would be useful if it was posble to manage rackspace in netdot, similar to what
racktables offer.
--
You have received this notification because you have either subscribed to it,
or are involved in it.
To change your notification preferences, please click here:
http://osl.uoregon.edu/redmine/my/account
------------------------------
_______________________________________________
Netdot-devel mailing list
[email protected]
https://osl.uoregon.edu/mailman/listinfo/netdot-devel
End of Netdot-devel Digest, Vol 94, Issue 11
********************************************
