Differences

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

--- devel:tasklist3.3 [2007/09/27 14:15]
faltin
+++ devel:tasklist3.3 [2007/10/03 08:02] (current)
jodal SMJ4: Err, SMJ4.5 already existed. SMJ4B it is then.
@@ Line 1: / Line 1: @@
-====== Task list ======
+====== NAV 3.3 tasks ======
+This document presents a list of new features we have been working on for NAV 3.3, from February 2007 till September 2007.
-This document presents a list of new features we have been working on from February 2007 till September 2007;
-i.e. for the NAV 3.3-release.
 ====== Morten's Tasks ======
@@ Line 20: / Line 15: @@
 ^ Estimated time | ? hrs       |
 ^ Start date     | 2007-07-09  |
-^ Status         | In progress |
+^ Status         | Done |
 ^ Due for        | NAV 3.3     |
@@ Line 36: / Line 31: @@
     * //(done 2007-08-15)// l2trace
-===== MB2: Support auto insertion of types =====
-^ 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:
-  * delete the CDP and TFTP fields. 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.
-  * 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 type name 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         | Complete?  |
-^ Due for        | ?          |
-  * Support the ability to except certain prefixes from data collection. Implement config file support.
-  * (2007-08-13) Possibly already implemented by Jostein Gogstad on his IPv6 branch.  Needs further testing.
-===== 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) =====
-^ Assigned to    | Morten Brekkevold |
-^ Estimated time | ? hrs      |
-^ Start date     |            |
-^ Status         |            |
-^ 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.
-===== 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 home brew 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-plug in for ENTITY-MIB, and make sure the HP plug in does HP specific things afterwards.
 ====== Stein Magnus' Tasks ======
@@ Line 231: / Line 99: @@
   * (done 2007-07-09) Show all port views in module view, not just switch port status.
   * (done 2007-07-10) Show prefixes related to a gwport in the port view.
-===== SMJ3: Improve the report tool =====
-^ Assigned to    | Stein Magnus Jodal (and Morten) |
-^ Estimated time | ? hours   |
-^ Start date     |           |
-^ Status         | Postponed due to collision with SS3.2 |
-^ Due for        | NAV 3.3 and later |
-  * 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 similar
-   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.
-==== Post 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.
@@ Line 312: / Line 126: @@
   * (done 2007-07-13) MAC search has been modified to search more effectively in the DB (mac field changed from varchar to macaddr datatype).
-The following needed further clarification at a meeting, and has not yet been implemented:
+The following needed further clarification at a meeting, and has not been implemented in 3.3. It has been moved to a separate task, see SMJ4B for updates.
   * Originally: Support search all the way to room using the cabling and patch data input from Edit DB.
@@ Line 337: / Line 151: @@
   * The single switch port view sports a link to the machine tracker, to track the active mac addresses on a given port.  Interface names are now stored in the cam data instead of port numbers, so the search URL must include the interface name instead of the port number to yield correct results.
-===== SMJ5: Rewrite Alert Engine =====
-^ Assigned to    | Stein Magnus Jodal |
-^ Estimated time | 80 hrs    |
-^ Start date     |           |
-^ Status         |           |
-^ Due for        | NAV 3.4   |
-Rewrite Alert Engine (now Perl) in Python with all existing features, plus the following missing features:
-  * Support all operators from AlertProfiles (defined in subsystem/alertprofiles/config.php:31)
-  * Support subcat
-===== SMJ6: Merge IP Info and IP Device Center =====
-^ Assigned to    | Stein Magnus Jodal |
-^ Estimated time | 80 hrs    |
-^ Start date     |           |
-^ Status         |           |
-^ Due for        | NAV 3.4   |
-^ Depends on     | SMJ4      |
-The features of IP Info is mostly a subset of IP Device Center, thus IP Info should be merged into IP Device Center.
-  - Add room/patch support to Machine Tracker. This is a part of SMJ4.
-  - Extend IP Device Center to show IP/hostname for hosts which is unknown to NAV, just like IP Info does today.
-  - Remove the IP Info subsystem.
-  - Rename IP Device Center (sysname devBrowser, webname browse) to IP Device Info (sysname and webname ipdevinfo, with redirect from webname browse).
-  - Change all links from /browse to /ipdevinfo.
-  - Add IP Device Info search box on the front page, in addition to the existing search box at the reports main page.
 ====== John Magne's Tasks ======
@@ Line 393: / Line 176: @@
   * 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 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:
-  * 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.
-  * Re implement 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 similar 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.
-====== Kristian Klette's Tasks ======
-===== SS1: New interactive and dynamic layout engine in Traffic Map =====
-^ Assigned to    | Kristian Klette |
-^ Estimated time | 120 hrs         |
-^ Start date     |                 |
-^ Status         |                 |
-^ Due for        | NAV 3.4         |
-  * Make use of the Prefuse library (http://prefuse.sf.net/) to re implement the visualization of the [[:trafficmap|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 functionality. If the zoom function is good end user machines can be shown as well. The various links between the nodes in the graph may either 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 hierarchy / auto generate containers
-  * support parameters making it possible to link directly to a container
-  * auto layout algorithm on/off pr container
-  * consider showing all subnets on the top level. Possibly add a button for this.
-  * strengthen the admin view when moving routers around.
-====== Jostein Gogstad's Tasks ======
-===== SS3: Support IPv6 in NAV =====
-^ Assigned to    | Jostein Gogstad |
-^ Estimated time | 160 hrs         |
-^ Start date     |                 |
-^ Status         | Completed / Untested |
-^ Due for        | NAV 3.4         |
-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.
-====== Summer Student Tasks ======
-===== SS2: Support generic (and HP) syslog messages in the syslog analyzer =====
-^ Assigned to    | Unassigned      |
-^ Estimated time | ? hrs           |
-^ Start date     |                 |
-^ Status         |                 |
-^ Due for        | Post NAV 3.3    |
-  * 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 more generic, so that messages from UPSes and whatnot can be included.

NAV Wiki

User Tools

Site Tools

Differences

Page Tools