Differences

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

--- historyofnav [2007/05/11 13:30]
jodal Fix navplanned link.
+++ historyofnav [2012/01/29 20:07]
faltin [2006]
@@ Line 3: / Line 3: @@
-===== 1999 =====
-The development of NAV started in 1999. Prior to that NTNU, like so
+===== 1999 - NAV v1 =====
+The development of NAV started  at [[http://www.ntnu.no|NTNU]] in 1999. Prior to that NTNU, like so
 many others, had acquired a traditional network management system (HP
-Openview) that hopefully would fulfill our needs. After thorough
+Openview) that hopefully would fulfil our needs. After thorough
 investigation and adjustment of the system we found however that it
 lacked functionality in many areas. We decided to implement a basic
@@ Line 13: / Line 16: @@
 The name NAV came about later, in the initial stages we called our
-system //!NettInfo//. The first tasks we solved were:
+system //NettInfo//. The first tasks we solved were:
   * A rudimentary collection system that gathered router port data using SNMP.
@@ Line 37: / Line 40: @@
 Trygve Lunheim, Tor-Arne Kvaløy, Eric Sandnes,
 Stig Venås, Gro-Anita Vindheim, Knut-Helge Vindheim.
 ===== 2000 =====
 The development at the time was focused around perl and php. In 2000
-we introduced java in an upgraded version of the traffic map. We
+we introduced java in an upgraded version of the traffic map (vlanplot). We
 also introduced mySQL for our database. Further:
@@ Line 60: / Line 62: @@
-===== 2001 =====
+===== 2001 - NAV v2 =====
 In early 2001 UNINETT gained interest in our system. They asked
@@ Line 197: / Line 199: @@
 new equipment types:
-  * An OID database is introduced containing information on all SNMP OIDs NAV used in the collection process.  The new collection engine, getDeviceData, uses the OID datebase. When new equipment is added to NAV it is tested against all the OIDs and classified accordingly.
+  * An OID database is introduced containing information on all SNMP OIDs NAV used in the collection process.  The new collection engine, getDeviceData, uses the OID database. When new equipment is added to NAV it is tested against all the OIDs and classified accordingly.
 The new collection system (getDeviceData) uses a plug in-based architecture, working
@@ Line 219: / Line 221: @@
   * Device management with the ability to track milestone events of physical devices from order and arrival through the operational stages.
-Also worth mentioning; NAV has so far been presented on numerous occations/
+Also worth mentioning; NAV has so far been presented on numerous occasions/
 conferences in Norway. In 2003 NAV is for the first time
 presented internationally:
@@ Line 234: / Line 236: @@
 Magnus Thanem Nordseth, Andreas Åkre Solberg, Magnar Sveen,
 Stian Søiland, Gro-Anita Vindheim, Morten Vold, Arne Øslebø.
@@ Line 241: / Line 244: @@
 was to finish off unfinished work, fixing bugs and testing the
 system thoroughly. In terms of new functionality, a conservative model was followed.
-Our focus was on completing NAV3 and thus permanantly leaving NAV2 behind.
+Our focus was on completing NAV3 and thus permanently leaving NAV2 behind.
 Many hours were put into further
@@ Line 258: / Line 261: @@
 Documentation was improved and translated to English, and a new [[http://metanav.ntnu.no|wiki web site]]
-(based on !MoinMoin) was established, also allowing for a more distributed contribution
+(based on MoinMoin) was established, also allowing for a more distributed contribution
 of documentation.
-A total of 8 NAV 3.0 beta releases was relased in 2004, beta4  (May 11) being the first GPL release
+A total of 8 NAV 3.0 beta releases was released in 2004, beta4  (May 11) being the first GPL release
 and beta7 (July 27) being the first with a changelog (which has been updated since).
@@ Line 269: / Line 272: @@
 Stian Søiland, Gro-Anita Vindheim, Morten Vold (project leader), Arne Øslebø.
-===== 2005 =====
+===== 2005 - NAV v3.0 =====
 was a relatively slow year for NAV. NTNU and UNINETT did not have so much resources to put into the
@@ Line 275: / Line 278: @@
 In June we finally announced our first release candidate (rc1), followed by a second in July.
-NAV 3.0.0 was finally released on September 16 2005.
+NAV 3.0.0 was finally released on September 16 2005 with the following highlights:
-For details on the improvements made in the 2005 releases, we refer to the
+  * Completely new web interface - new look
+  * New authentication and authorization system
+  * New Java based snmp collector: getDeviceData
+  * New database design
+  * New event- and alarm system (event engine, alert engine, alert profiles)
+  * Module monitor
+  * New message system
+  * New tool Network discovery, improved vlanplot (the network map)
+For further details on the improvements made in the 2005 releases, we refer to the
 [[http://svn.itea.ntnu.no/repos/nav/navme/tags/3.0.0/CHANGES|3.0 change log with its history]].
 Project participants in 2005: John Magne Bredal, Kristian Eide, Vidar
 Faltinsen, Gro-Anita Vindheim, Morten Vold (project leader).
 ===== 2006 =====
-has been a definite upswing for NAV. Project development is now supported by the UNINETT
+has been a definite upswing for NAV. Project development is now
-[[http://www.gigacampus.no/om.en.html|GigaCampus programme]] with an overall goal
+supported by the UNINETT
-of getting NAV up and running at most major universities and university colleges in Norway within 2008. Morten Vold is devoted full time
+[[https://openwiki.uninett.no/gigacampus:about|GigaCampus programme]] with an
-to NAV (he is now employed by UNINETT). Vidar Faltinsen is back as project leader. From NTNU John Magne Bredal is working 40% with NAV. We have
+overall goal of getting NAV up and running at most major universities
-also recruited a new student during the summer months; Stein Magnus Jodal.
+and university colleges in Norway within 2008. Morten Brekkevold
+(previously Vold) is devoted full time to NAV, now being employed by
+UNINETT.  Vidar Faltinsen made a comeback as project leader.  John
+Magne Bredal at NTNU devoted 40% of his time working with NAV.  We
+also recruited a student, Stein Magnus Jodal, to work on NAV as a
+summer intern, and we kept him on for the fall.
+The Universities of Tromsø and Bergen began sponsoring a FreeBSD port
+of NAV, while Tromsø offered to contribute their own code to NAV.  The
+Debian developer Morten Werner Olsen at The University of Oslo was
+commisioned by UNINETT to maintain a Debian NAV package.  A SuSE
+package was maintained by NTNU and Centos RPMs were contributed by
+Alexander Krapivin at MSU, Moscow, Russia.
+A strategy of targeting new feature releases twice a year was
+established (with bugfix releases in between).  NAV 3.1 was released
+in June and 3.2, with an original schedule of October, was released in
+February 2007.
+NAV gained the capability to actively block switch ports through the
+addition of the NTNU-contributed Arnold tool.  Adding the ability to
+collect high speed traffic counters (64 bits) made it possible to
+reduce the Cricket collector frequency for gigabit switch ports from
+every 1 minute to every 5 minutes, thus removing the need to have a
+separate configuration tree for gigabit ports. The IP Device Center (later renamed to IP Device Info) was introduced.
+We established a project page for NAV at SourceForge.  This was used
+for bug tracking and hosting source code releases.  A month after the
+.1 release, we had seen approximately 160 downloads from around the
+world (at the same time, the 3.0 version had been downloaded 674
+times).
+Project participants in 2006: John Magne Bredal, Vidar Faltinsen
+(project leader), Stein Magnus Jodal, Morten Brekkevold.
+===== 2007 =====
-The university of Tromsø is making contributions to NAV. Together with the University of Bergen they are sponsoring a FreeBSD ports of NAV.
+The NAV year of 2007 opened with the belated 3.2 release in February.
-University of Oslo is maintaining the NAV debian package. A Suse package is maintained by NTNU and a Centos RPM is contributed by
+The 3.2 release also marked our first step towards realizing a new
-Alexander Krapivin at MSU, Moscow, Russia. We are in dialogue with others as well.
+long-term goal: Reduce the number of dependencies and programming
+languages utilized in NAV.
-A strategy with feature releases twice a year is established (bug fixes in between).  NAV 3.1 was released in June and 3.2 is scheduled for October.
+The 3.2 release replaced the messages system with separate maintenance
-  * See [[http://svn.itea.ntnu.no/repos/nav/navme/tags/3.1.0/CHANGES|change log for 3.1]]
+and message systems, rewritten from scratch, after many usability
-  * See plans for 3.2 at the [[roadmap]].
+complaints from users.  The Perl SMS daemon was rewritten in Python,
+adding support for SMS dispatcher plugins.  Much of the
+behind-the-scenes HTML and CSS was cleaned up and restructured. The
+release also brought numerous small improvements to NAV overall.
-We have established a home page for NAV at [[http://sourceforge.net/projects/nav/|SourceForge]]. Releases and binaries are available from here. We are also
+October 1st brought the NAV 3.3 feature release.  This release added
-using the !SourceForge bug tracker system for bugs. We see a lot of traffic on the
+the long-awaited plugin based SNMP trap daemon, which enabled NAV to
-[[http://desperados.itea.ntnu.no/pipermail/nav-users/|nav-users mailing list]]. A month after the 3.1 release we have seen
+translate traps into NAV events and alerts.  Browsing and searching of
-approximately 160 downloads from around the world (the 3.0 version is downloaded 674 times as of 20 July 2006).
+device history was greatly improved.  The web interface received a
+major facelift.  Switch/router interface names replaced port numbers
+as identifiers in most parts of the web interface.
-Project praticipants in 2006: John Magne Bredal, Vidar Faltinsen (project leader), Stein Magnus Jodal, Morten Vold.
+The 2007 development project saw Morten Brekkevold take over as the
+project leader.  Kristian Klette was taken on as a new student intern,
+and started working on a Traffic Map replacement, based on the Prefuse
+visualization library.
+Project participants in 2007: John Magne Bredal, Vidar Faltinsen,
+Stein Magnus Jodal, Kristian Klette, Morten Brekkevold (project
+leader).

NAV Wiki

User Tools

Site Tools

Differences

Page Tools