This is an old revision of the document!
This document presents a list of new features we are working on from October 2007 and forwards; i.e. post NAV 3.3. This is a dynamic document - watch out for updates!
The page is loosely sorted on priority. To see what in fact is committed for new NAV releases, see the roadmap. Also see lower priority tasks i TaskListLowPri.
In time, we are hoping to migrate these tasks into LaunchPad blueprints.
Assigned to | Morten Brekkevold |
---|---|
Estimated time | ? hrs |
Start date | |
Status | |
Due for | ? |
Today when you add a new device of an unknown type you have to manually add the type in edit database. You also have to fill in some less than obvious fields, i.e. frequency.
Change the type table:
Make add netbox simpler:
Improve gDD:
Assigned to | Morten Brekkevold |
---|---|
Estimated time | ? hrs |
Start date | |
Status | Completed |
Due for | ? |
Assigned to | Morten Brekkevold |
---|---|
Estimated time | ? hrs |
Start date | |
Status | low pri |
Due for | ? |
Assigned to | Morten Brekkevold |
---|---|
Estimated time | ? hrs |
Start date | |
Status | Done - by John Magne - June 2008 |
Due for | ? |
When a “wanted” mac address is seen by the camlogger this should trigger an alarm posted on the eventq. This is very useful when a certain machine is “wanted” but currently is off line.
Assigned to | Morten Brekkevold |
---|---|
Estimated time | 2 days |
Start date | |
Status | |
Due for | ? |
This task concerns itself with making somewhat of a “sudo” system for the NAV web UI, enabling the administrator to act as other NAV users. This idea arises from the oft requested need to edit a mortal user's alert profile. A general “sudo”-like mechanism of the web UI should not be too difficult to implement.
Assigned to | Morten Brekkevold |
---|---|
Estimated time | 40 hrs |
Start date | |
Status | |
Due for | ? |
getDeviceData, eventEngine and getBoksMacs use a home brew logging system. gDD is a huge, complex system, where this homebrew logging library is not nearly flexible enough for hard core debugging.
Assigned to | Morten Brekkevold |
---|---|
Estimated time | ? hrs |
Start date | |
Status | |
Due for | ? |
Assigned to | Morten Brekkevold |
---|---|
Estimated time | ? hrs |
Start date | |
Status | |
Due for | ? |
The HP plugin apparently only supports virtual HP stacks and does not understand physical stacks (e.g ProCurve 5308). Physical HP stacks can be understood pretty well by looking at ENTITY-MIB, so it might be a good idea to implement a generic device-plug in for ENTITY-MIB, and make sure the HP plug in does HP specific things afterwards.
Assigned to | Morten Brekkevold (and others) |
---|---|
Estimated time | ? hrs |
Start date | |
Status | |
Due for | 3.6 |
Design- and maintenance problems with the getDeviceData codebase, couple with our long term goal of reducing the number of programming languages in NAV, has prompted us to envision a new getDeviceData based entirely on Python code. It is likely that this would be based off the Twisted framework for asynchronous SNMP polling, which will reduce the complexity introduced by threading in the original gDD.
Tasks moved to https://blueprints.launchpad.net/nav.
Assigned to | John Magne Bredal |
---|---|
Estimated time | ? hrs |
Start date | |
Status | |
Due for | NAV 3.4 |
Arnold in NAV 3.1 supports taking machines off the network by setting the switch port they are connected to in shutdown. We would like to support an alternative; instead of shutting down the port, we instead change the vlan value of the port. This will allow for quarantine vlan solutions where the user is given limited network access and typically is redirected to a web page giving information on why he is taken off the network (followed by instructions on how he should proceed).
Minor changes:
Assigned to | John Magne Bredal |
---|---|
Estimated time | 120 hrs |
Start date | |
Status | |
Due for | NAV 3.4 |
Assigned to | John Magne Bredal |
---|---|
Estimated time | 80 hrs |
Start date | |
Status | |
Due for | NAV 3.4 or later |
Assigned to | Andreas Knudsen |
---|---|
Estimated time | 80 hrs ? |
Start date | |
Status | |
Due for | NAV 3.4? |
Assigned to | Kristian Klette |
---|---|
Estimated time | 120 hrs |
Start date | |
Status | |
Due for | NAV 3.4 |
The idea is to create an interactive visualization where node layout is automatic and can be zoomed to any extent.
Other traffic map ideas:
Also consider other enhancements to the traffic map:
jorgen.abrahamsen@uninett.no | |
Phone | +47 97 04 49 45 |
Assigned to | Jørgen Abrahamsen (and Morten) |
---|---|
Estimated time | 120 hours |
Start date | 06.02.2008 (dd.mm.yyyy) |
Status | in progress/being worked on |
Due for | NAV 3.4 or 3.5 and later |
Separate local reports in a local file so that NAV's own reports are not altered. Local reports with equivalent name as the NAV report takes precedence. The local report does not have to copy all the original report variables, only the ones that are to be replaced.
This page gives a listing of all reports defined with their title and a description. $description is not a variable today - this should be added. We suggest the report list is linked from the static report main page of today. We suggest an alphabetical listing.
This is interesting in some reports, i.e. where we give a machine count on all machines on all prefixes. A total on this report will give the total number of machines in the network. This functionality was also present in NAV v2.
Today, the entire report SQL is re-run when the button for the advanced search form is pressed. This is a waste of resources. The form should always be in the HTML output, and Javascript should be employed to dynamically display and hide the form from the flow of the page.
The overall goal being to improve performance and code readability. This task may be dropped if it involves a lot of work.
Tasks moved to https://blueprints.launchpad.net/nav.
Assigned to | Unassigned |
---|---|
Estimated time | ? hrs |
Start date | |
Status | |
Due for | Post NAV 3.4 |
Depends on |
Assigned to | Unassigned |
---|---|
Estimated time | 10 hrs |
Start date | |
Status | |
Due for | Post NAV 3.4 |
Depends on |