Differences

This shows you the differences between two versions of the page.

--- tasklist [2007/05/11 10:53] – jodal
+++ tasklist [2007/05/11 13:19] (current) – Moved to devel. jodal
@@ Line 1: / Line 1: @@
-[[TableOfContents]]
-This document presents a list of new features we are working on from February 2007 and forwards;
-i.e. post NAV 3.2.
-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 links from the road map table of [[NAVPlanned]].
-Also see lower priority tasks i TaskListLowPri.
--------
-====== Morten's Tasks ======
-===== MB1: Implement support for interfaces instead of module/port =====
-|| Assigned to    || Morten Brekkevold ||
-|| Others         || Stein Magnus Jodal can do the Python webfront parts ||
-|| Estimated time || ? hrs     ||
-|| Start date     ||           ||
-|| Status         ||           ||
-|| Due for        || NAV 3.2   ||
-  * Support the use of interfaces instead module/port. Module/port does not in
- all cases give an intuitive description of a switch port. The interface name is
- often better, we need to ensure (in gDD) that interface name is descriptive in
- **all** cases.
-  * We would then like to change the cam table by replacing the fields module and
- port with the new field interface (we need these fields here to support retrieving
- data from historic switch ports that are gone from the swport table).
-  * Front end tools that are affected are:
-   * IP device center
-   * machine tracker
-   * report
-   * network map?
-   * network explorer?
-   * l2 trace?
-===== MB2: Support auto insertion of types =====
-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:
-  * delete the cdp and tftp fields.
-  * set 3600 as default for frequency, this should also be shown when manually updating the type table in edit database.
-Make add netbox simpler:
-  * set the typeid=unclassified, leave a more qualified setting to gdd.
-Improve gDD:
-  * when gdd sees a netbox with type unclassified, set the correct type based on sysobjectid. If the sysobjectid does not exist in the type table add it with a best guess typename and type description.
-   * the same mechanism should by used for detected type changes (the ip netbox is replaced with newer equipment of a different type).
-===== MB3: Support the ability to except certain prefixes from data collection =====
-|| Assigned to    || Morten Brekkevold ||
-|| Estimated time || ? hrs      ||
-|| Start date     ||            ||
-|| Status         ||            ||
-|| Due for        || ?          ||
-  * Support the ability to except certain prefixes from data collection.
- Implement config file support.
-===== MB4: Collect system.sysname in addition to dns names =====
-  * Today the netbox.sysname value is based upon dns. If dns does not resolve the ip address is used as
- name. We should in addition collect the name that is configured on the device, and perhaps make
- it configurable in a config file what should be the primary name source used in the front
- end tools.
-  * collect system.sysLocation and sysContact as well. Store it in netboxinfo (perhaps).
-===== MB5: Make logging from networkDiscovery more available =====
-|| Assigned to    || Morten Brekkevold ||
-|| Estimated time || ? hrs      ||
-|| Start date     ||            ||
-|| Status         ||            ||
-|| Due for        || ?          ||
-  * Translate networkDiscovery logging to English (bugid 1516904)
-  * Make the reports more available (admin tool on web or something).
-===== MB6: Trigger alarms on certain mac addresses (FR 1556395) =====
-When a "wanted" mac address is seen by the camlogger this sould trigger an alarm posted on
-the eventq. This is very useful when a certain machine is "wanted" but currently is offline.
-===== MB7: Admin can change his/her effective user ID =====
-|| 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.
-  * A "sudo" tool will move the session's //user// attribute into a //realUser// attribute, and attach the effective account object to the session's //user// attribute.  This should work for the entire web interface.
-  * The MainTemplate must be able to differentiate whether a real user is logged in, or if someone is just effectively operating as that user.  MainTemplate must clearly signify this state in the interface, so the administrator knows why his/her effective privileges have been dropped.
-  * The "sudo" tool must have a "return to being the administrator" function, which should be available from the MainTemplate near the "logout user" and/or "currently logged in as user" elements.
-  * The ability to to "sudo" in the web interface should be a configurable privilege in the user admin panel.
-===== MB8: Support delayed SMSes =====
-|| Assigned to    || Morten Brekkevold ||
-|| Estimated time || 40 hrs     ||
-|| Start date     ||            ||
-|| Status         ||            ||
-|| Due for        || ?          ||
-NAV v2 had the functionality of sending delayed SMS messages. The idea was that the
-guard on duty should be able to sleep  through less important alerts during the night.
-In the morning he/she should get updates on SMS. These updates should **not** include
-events that have fixed themselves during the night.
-A modification of alert engine and alert profiles is needed to implement this support.
-===== MB9: New logging system for Java based subsystems =====
-|| Assigned to    || Morten Brekkevold ||
-|| Estimated time || 40 hrs     ||
-|| Start date     ||            ||
-|| Status         ||            ||
-|| Due for        || ?          ||
-getDeviceData, eventEngine and getBoksMacs use a homebrew logging system. gDD is a huge,
-complex system, where this homebrew logging library is not nearly flexible enough for
-hard core debugging.
-  * The Java subsystems should be refactored to use Log4j (http://logging.apache.org/log4j/).
-===== MB10: Implement a cleanup function for the device table =====
-|| Assigned to    || Morten Brekkevold ||
-|| Estimated time || ? hrs      ||
-|| Start date     ||            ||
-|| Status         ||            ||
-|| Due for        || ?          ||
-===== MB11: Improve HP stack collection / make generic ENTITY-MIB plugin =====
-|| 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-plugin for ENTITY-MIB, and make sure the HP plugin does HP specific things afterwards.
-===== MB12: Remove CDP and TFTP fields for equipment types =====
-|| Assigned to    || Morten Brekkevold ||
-|| Estimated time || 14 hrs      ||
-|| Start date     ||            ||
-|| Status         ||            ||
-|| Due for        || 3.3        ||
-The CDP and TFTP fields required for equipment types are unused.  A device's CDP ability can been discovered through the device's OID support classification, and the TFTP field is not used by anything in NAV.
--------
-====== Stein Magnus' Tasks ======
-===== SMJ1: Enhance Device History =====
-|| Assigned to    || Stein Magnus Jodal ||
-|| Estimated time || ? hrs     ||
-|| Start date     || (2007-02-16) ||
-|| Status         ||           ||
-|| Due for        || NAV 3.3   ||
-  * Make it possible to link from another tool to device history for a
- certain device and time frame
-  * There are bugs in device history in terms of selecting a time frame
-  * It should be easy to see events of a certain type; i.e. see all software upgrades/changes for
- a router/switch - very interesting data.
-===== SMJ2: Improve IP Device Center =====
-|| Assigned to    || Stein Magnus Jodal ||
-|| Estimated time || 80 hrs     ||
-|| Start date     || (2007-03-06) ||
-|| Status         ||            ||
-|| Due for        || NAV 3.3    ||
-  * Improve overall performance
- (Performance improved about 75% in r3925, but a rewrite is wanted in the future.)
-  * The 'Recent alerts' table should be improved
-   - Present more relevant information in the 'Recent alerts' view
-   - Modify 'Device history' (subtool of device management) so that it
-      takes a netbox and to/from date as parameters
-   - Link from 'Recent alerts' to 'Device history' for the given netbox
-      and time interval
-  * Routerport view
-   Unfortunately we do not gather data of all router ports, only those
-   in operation. This means that the router port view does not give a
-   complete physical view of the box. Further we do not have data on
-   duplex and trunk. In essence, the only relevant things to show is speed:
-   Color legend: [] not active [] 10Mbps [] 100M [] 1G [] 10Gbps
-   The port history view is not relevant for router ports either.
-   Note: For GSW we should show both the switch port and router port view.
-  * A pop up menu from the swport view that can point you to relevant links,
- i.e. the machines behind swport machine tracker page.
-===== SMJ3: Enhance the report tool =====
-|| Assigned to    || Stein Magnus Jodal (and Morten) ||
-|| Estimated time || ? hours   ||
-|| Start date     ||           ||
-|| Status         ||           ||
-|| Due for        || NAV 3.3   ||
-  * Add support for local reports.
-   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.
-  * Make an automated report page.
-   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.
-  * Implement a sum function ($sum).
-   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.
-  * Morten: Add a **duplex mismatch** report.
-   This report should show analyze all interconnection between
-   switches and look at the duplex value on each side of the
-   link. If there is a mismatch a row in the report should
-   be produced. Ideally this report should be empty at all times.
-   The report can be produced using one (rather complex) SQL
-   sentence in report.conf. We have done something simular
-   in NAV v2 - NTNU has a solution for their v3!
-  * Morten: Also add a **spanning tree blocked ports** report.
-   Once again - steal from the NTNU v3 installation.
-==== Not NAV 3.3 ====
-  * Enhance / partially rewrite the report code base.
-   The overall goal being to improve performance and code readability.
-   This task may be dropped if it involves a lot of work.
-===== SMJ4: Improve the Machine Tracker =====
-|| Assigned to    || Stein Magnus Jodal ||
-|| Estimated time || 40 hrs    ||
-|| Start date     ||           ||
-|| Status         ||           ||
-|| Due for        || NAV 3.3   ||
-  * The mac search result should include port description. Perhaps link to report?
-  * The switch search has several caveats. It does not give a proper error message if a
-   name that is not a switch it entered, further no error is given if module or port names
-   out of range is given. Changes here alse affect the change to interface name instead of
-   module/port. Further in accordance to FR 1556369 it should be possible to enter the switches
-   ip address instead of name.
-  * Support search all the way to room using the cabling and
-   patch data input from the Edit Database tool.
-  * Use proper tabs in the tool
--------
-====== John Magne's Tasks ======
-===== JM1: Implement NAV SNMP trap demon =====
-|| Assigned to    || John Magne Bredal  ||
-|| Estimated time || 90 hrs    ||
-|| Start date     ||           ||
-|| Status         ||           ||
-|| Due for        || NAV 3.3   ||
-  * NAV v2 had an SNMP trap solution. We need a basic mechanism to support the reception of external snmp traps. This will supplement the [[http://drift.uninett.no/~andreas/mailin/|mailin solution]].
-  * Consider integration with gDD for some instances. snmp traps could in some cases trigger new data collection; i.e. a trap that reports on new mac adresses seen behind a switch port (maybe this should allow for a cam database update directly?).
-  * The NAV SNMP trapd should be configurable. It should perhaps per default discard unknown traps (just log them, not do anyting intelligent).
-  * A trap NAV understands should be posted on eventq with the proper eventtype set, as done in mailin. Event handlers will be needed, as in mailin.
-  * It should be possible to trigger a plugin for certain traps. I.e. a script that updates the swport.link value based
-on link up/down traps is very interesting. Further a script that closes/opens cam entries (if traps regarding
-apperance/disapperance of mac addresses can be sent).
-  * Focus particularly on supporting traps regarding defect power (scenario where the redundant power is out).
-===== JM2: New features in Arnold =====
-|| Assigned to    || John Magne Bredal ||
-|| Estimated time || ? hrs     ||
-|| Start date     ||           ||
-|| Status         ||           ||
-|| Due for        || NAV 3.3   ||
-  * Switch vlan in addition of shutdown of ports.
-Arnold in NAV 3.1 supports taking machines off the network by setting the switchport 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 quarantene 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:
-  * Close ports based on mac-addresses
-  * Open all or one when several ports are closed based on same ip/mac
-  * A timer for incremental closing of ports to prevent skyhigh numbers
-  * More information on the webpage.
-===== JM3: Improve Cricket in NAV =====
-|| Assigned to    || John Magne Bredal ||
-|| Estimated time || 120 hrs    ||
-|| Start date     ||            ||
-|| Status         ||            ||
-|| Due for        || NAV 3.2 and 3.3 ||
-  * Collect more counters from the interface mib. Take a look at what UNINETTs genplot collects. For instance input ignores, output discards, interface resets.
-  * Reimplement makecricketconfig making it more modular and easier to expand with new statistics. It is an overall goal that NAV admins should fairly easily be able to add their own set of statistics.
-  * Add support for wireless users statistics
-    * Expand the oidDB with the new OIDs. Wireless base stations should then be classified to answer to the relevant new OIDs.
-    * Build cricket config tree foe wireless. Focus on octets, errors and users.
-  * Add support for UPS traffic statistics collection
-   * Do expansion in a simular manner as for wireless.
-  * Add support for weathergoose statistics
-===== JM4: Strengthen RRDbrowser =====
-|| Assigned to    || John Magne Bredal ||
-|| Estimated time || 80 hrs    ||
-|| Start date     ||           ||
-|| Status         ||           ||
-|| Due for        || NAV 3.3 or later ||
-  * RRDbrowser is a powerful tool, but suffers from being hidden way down in the user interface. With a better, general interface to RRDbrowser, perhaps combined with sorted statistics (T9) this could be the new NAV statistics tool (which in turn can link to cricket).
-  * Take a look at the nav-dev posting of Sun, 21 Sep 2003 12:32:48 from faltin with title "Statistical viewer, herunder multiselect!"
-   * simplify this, focus on implementing the most wanted features.
-  * It is sometimes interesting to view a sum of underlying RRD data in one graph. An example is the sum of all wireless users in a building or on a campus, etc.
--------
-====== Andreas' Tasks ======
-===== AK1: Strengthen wireless data collection =====
-|| Assigned to    || Andreas Knudsen ||
-|| Estimated time || 80 hrs ? ||
-|| Start date     ||          ||
-|| Status         ||          ||
-|| Due for        || NAV 3.3? ||
-  * Make a new device handler to gDD that collect interesting information from wireless base stations. In particular:
-   * configured channel IEEE 802.11b and 802.11g
-   * configured channel IEEE 802.11a
-   * mac address used for IEEE 802.11b and 802.11g
-   * mac address used for IEEE 802.11a
-  * Input the selected data as (var,value) in netboxinfo.
-  * Make reports that can view the collected data.
-  * Consider enhancements to IP device center in this respect.
--------
-====== Summer Student Tasks ======
-===== SS1: New interactive and dynamic layout engine in Traffic Map =====
-|| Assigned to    || Unassigned ||
-|| Estimated time || 40 hrs    ||
-|| Start date     ||           ||
-|| Status         ||           ||
-|| Due for        || Post NAV 3.3 ||
-  * Make use of the Prefuse library (http://prefuse.sf.net/) to reimplement the visualization of the Traffic Map component.  Observe the following ideas:
-   * Implement a DeviceRenderer to render node icons from a scalable SVG source file.
-   * Implement a new EdgeRenderer class to render edges colored for both uplink and downlink traffic stats (just as the current version displays it).
- The idea is to create an interactive visualization where node layout is automatic and can be zoomed to any extent.
-Other traffic map ideas:
-==== New physcal view of the network ====
-  * Show a physical view of the network with interconnection of all network devices regardless of layer 3 and layer 2
-   funtionality. If the zoom function is good end user machines can be shown as well. The various links between the
-   nodes in the graph may eiter be a layer 3 p2p link, a layer two trunk, or a layer two specific vlan connection.
-   Avoid using the layer three cloud that vlanplot uses, assume this always is implemented with underlying switches
-   that NAV should discover.
-   * This requires that every physical router port is connected either directly to another router (serial etc) or
-     two a switch. If we are missing the gwport.to_netbox info we could use vlanplots layer3 view instead.
-==== Traffic Map also a status monitor ====
-  * Make the Traffic map a status monitor by introducing green and red nodes (containers, routers, switches, network clouds). Allowing for intermediate colors to reflect that a given percentage of the nodes contained are down.
-==== Support geographical layout ====
-  * Assuming the room table has utm location information show a correct geographical layout og the map on
-   top of geographical maps (with changing detail depending on zoom level).
-==== Alternative ideas to improvements of vlanplot ====
-Also consider other enhancements to the traffic map:
-  * container hierarchi / autogenerate containers
-  * support parameters making it possible to link directly to a container
-  * autolayout algorithm on/off pr container
-  * consider showing all subnests on the top level. Possibly add a button for this.
-  * strenghten the admin view when moving routers around.
-===== SS2: Support generic (and HP) syslog messages in the syslog analyzer =====
-  * HP has syslog messages with four levels. Map these to equivalent cisco levels and support the HP log format so that the messages can be imported in the NAV logger database.
-  * The syslog parser should be made general så that messages fra UPSes and whst not can be included.
-===== SS3: Support IPv6 in NAV =====
-|| Assigned to    || Unassigned ||
-|| Estimated time || 160 hrs    ||
-|| Start date     ||            ||
-|| Status         ||            ||
-|| Due for        || Post NAV 3.3 ||
-NAV does not support IPv6 today. Look into support in this order of priority:
-  - Gather data from all routers for IPv6 router ports / prefixes
-  - Complement this with a IPv6 prefix matrix
-  - Gather IPv6 machine tracker data (IPv6 "arp"/neighboring cache).
-  - Consider IPv6 traffic statistics (there are separate IPv6 traffic counters, we think...)
-  - Look at collecting snmp data from netboxes using IPv6. This we consider far fetched.