Created
October 10, 2012 10:53
-
-
Save norrs/3864753 to your computer and use it in GitHub Desktop.
tickets_to_nav.txt
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
#1 Link to netmap with VLAN argument | |
Possible to create a hyperlink to netmap with VLAN id to choose as a selected vlan. | |
Should also be able to create a hyperlink to a specific view. | |
Example on hashbangs: | |
#!netmap/vlan/navvlanid | |
#!netmap/1234/vlan/navvlanid | |
Related to #9 / depends? | |
#2 Fade out devices which is not a part of a selection (instead of marking marked nodes with a circle) | |
-- | |
only room/location? or VLAN selection as well? | |
#3 List over available views in admin page should include author of view in table. | |
#4 Update icons in netmap | |
-- | |
Switch icons should be blue and not red. | |
Grey for elink nodes | |
Related to | |
#12 | |
#5 Error processing for data loading done asyncrhnoioously | |
-- | |
User should get an error message / action to tell the user to try reload the page. etc. | |
#6 Be able to view nodes related to a subcategory | |
-- | |
Example: view nodes in subcategory "PRINT", should only view VLAN-topology from routers and down to related netboxes in selected subcategory. | |
Question: Should rest of the topology be removed from the graph (not rendering at all) or use the fading tecniqeue as mentioned in #fade-ticket ? | |
Dependn on https://bugs.launchpad.net/nav/+bug/1062146 Subcategories should be simplified into a group or tag concept | |
Related to #1 | |
#7 Limit topology graph to selected organization | |
-- | |
Limit on netbox or VLAN? | |
#8 Enhancement on zooming | |
If search returns only 1 result: zoom to selected box up close, center it's position in view | |
Else: find bounding box for matching devices in search, set proper scaling and center boundingbox to center in view so all devices matching the results are shown. | |
Devices matching search should be highlighted, either by circle around the nodes or fadeout rest of the topology. | |
#9 Zoom-to-extend on selected vlan | |
-- | |
Find bounding box for devices in selected vlan, zoom and translate bounding box. | |
Depends on #8 | |
#10 Export to SVG | |
-- | |
Include a bundle (zip) with required resources for SVG (images, css?) and bundle it together with SVG markup in a zip file so user can simply open it in any SVG program or user's favorite browser. | |
#11 Topology drawing of multiple links/edges between two nodes: | |
-- | |
Draw only one line between the netboxes. | |
Line between netboxes which has multiple links should have two circles at each end to indicate this link contains multiple links. | |
Clicking a edge with multiple links should show interface pairs in a table. Maybe include traffic counters .. | |
Traffic load is colored by the most deprived of the parallel links (most congested in the percentage of nominal bandwidth) | |
#12 Tactical view | |
-- | |
Netboxes should be colored by their status (UP, DOWN, SHADOW, UNKNOWN, NOT_MONITORED?) | |
Depends on #4 | |
#13 Better description of traffic counters for selected link. | |
-- | |
"in" and "out" doesn't really tell which direction the traffic flows on the selected link. Better description needed. | |
Give identifiers on netboxes (A and B) and use: A -> B: traffic. B -> A: traffic |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment