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] Rack management ([email protected])
2. Rack management and "location" redesign (Carlos Vicente)
3. Rack management and "location" redesign (Carlos Vicente)
----------------------------------------------------------------------
Message: 1
Date: Thu, 1 Jan 2015 11:06:04 -0800
From: [email protected]
Subject: [Netdot-devel] [Netdot - Feature #803] Rack management
To: [email protected], [email protected]
Cc: [email protected], [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8
Issue #803 has been updated by Carlos Vicente.
The more ideal alternative to the site->floor->room->closet->rack hierarchy is
to store all of these objects in a single "location" table, in combination with
a "location_type" table. For example:
<pre>
location
--------
id
name
description
type
etc.
location_type
-------------
id
name
description
</pre>
This representation has the following advantages:
* Assets and other objects would only need a pointer to "location". User can be
as specific as needed (site vs. room vs. rack)
* Easier to add new location types
But it has the following problems:
* Code changes touching many tables and UI components
* There are fields that are only particular to certain tables (although we have
similar cases already (e.g. Entity table)
Feedback welcome
----------------------------------------
Feature #803: Rack management
https://osl.uoregon.edu/redmine/issues/803#change-3264
Author: Robin Johansson
Status: New
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, 1 Jan 2015 14:29:18 -0500
From: Carlos Vicente <[email protected]>
Subject: [Netdot-devel] Rack management and "location" redesign
To: [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=windows-1252
Happy 2015 everyone!
Adding ?rack management? features will likely be the next big task in Netdot
development. I added some specifics and comments in:
https://osl.uoregon.edu/redmine/issues/803
Adding this is not hard per se, but it made me think about the idea of a more
flexible ?location? object. It would be a big change, so I?d appreciate your
feedback.
Best,
cv
------------------------------
Message: 3
Date: Thu, 1 Jan 2015 14:29:18 -0500
From: Carlos Vicente <[email protected]>
Subject: [Netdot-devel] Rack management and "location" redesign
To: [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=windows-1252
Happy 2015 everyone!
Adding ?rack management? features will likely be the next big task in Netdot
development. I added some specifics and comments in:
https://osl.uoregon.edu/redmine/issues/803
Adding this is not hard per se, but it made me think about the idea of a more
flexible ?location? object. It would be a big change, so I?d appreciate your
feedback.
Best,
cv
------------------------------
_______________________________________________
Netdot-devel mailing list
[email protected]
https://osl.uoregon.edu/mailman/listinfo/netdot-devel
End of Netdot-devel Digest, Vol 94, Issue 1
*******************************************
