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])
----------------------------------------------------------------------
Message: 1
Date: Tue, 30 Dec 2014 12:25:19 -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.
Category set to DeviceManagement
Priority changed from Normal to High
Target version changed from 1.0 to 1.1.0
Details:
h2. Schema
* Create a new "rack" table with the following columns:
** name (text)
** size (int) default: 42 (in config file)
** room (bigint, fk)
** num_direction (bool)
** info (text)
* Remove location columns from device table (site, room, rack)
* Add the following columns to the asset table:
** site (bigint, fk)
** rack (bigint, fk)
** rack_pos (int)
* Add the following column to Product:
** ru_size (int)
h2. Logic
* Site and rack columns in Asset table are redundant (because asset may not be
on rack)
** Ensure that there are no discrepancies
** Selecting the site should narrow the options for rack selection
* num_direction specifies how racks are numbered:
** 0 (false): bottom-up (default in config file)
** 1 (true): top-bottom
* Ensure that two assets cannot occupy the same rack positions
* Ensure that two racks in same room cannot have the same name
h2. Unit Tests
* Create unit tests for every new class and method
* Add unit tests to existing, related classes and methods if necessary
h2. UI
* Create new "rack.html" Mason component to visualize racks
** Link at top of rack to edit rack record
** Ability to add and remove assets from rack positions
** If asset is associated with a device, display device name (if more than one,
use hover window)
* Add rack search/add section under Cable Plant menu
** At this point, it may be necessary to rename "Cable Plant" to "Physical
Plant".
h2. Migration
* Write script to upgrade schema and migrate data
The new model implies that device location information will be lost if the
device does not have an associated asset.
Migration script may need to include step to add a dummy asset record, or
alternatively throw an error and roll back changes.
----------------------------------------
Feature #803: Rack management
https://osl.uoregon.edu/redmine/issues/803#change-3263
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
------------------------------
_______________________________________________
Netdot-devel mailing list
[email protected]
https://osl.uoregon.edu/mailman/listinfo/netdot-devel
End of Netdot-devel Digest, Vol 93, Issue 10
********************************************
