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: Thu, 5 Feb 2015 08:43:11 -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.


One more thing to consider: Add an image field (blob) to the product record. 
This would allow Netdot to draw that rack with more realistic pictures of what 
each product looks like, instead of just color-filled rectangles.
----------------------------------------
Feature #803: Rack management
https://osl.uoregon.edu/redmine/issues/803#change-3271

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 95, Issue 2
*******************************************

Reply via email to