On Tue, 10 Jan 2006, Ingeborg Hellemo wrote:

Vidar.Faltinsen@uninett.no said:

...

We are currently working on a list of new features to implement. I could present the list, but at this stage I will rather ask the NAV community... what do you want?

The University og Troms? now proudly presents their wish list:

(Well Vidar, you asked for it...)

Thank you, Ingeborg! Your input is of great value. In most cases I agree. Let's go ruby!

Programming/packaging style:

• Fewer languages

We will not introduce new languages. And - I see yoir point (hard to miss).

• Please make today's features work before you put all your resources on new

features.

We will - this is important.

I will not comment on all the details for now.

Best wishes for the new NAV year...

Thank you, and the same!

- Vidar

From kjetil.olsen at usit.uio.no Thu Jan 12 09:41:14 2006

From: kjetil.olsen at usit.uio.no (Kjetil Otter Olsen) Date: Thu Jan 12 09:41:21 2006 Subject: [Nav-users] Feature requests anyone? In-Reply-To: Pine.LNX.4.64.0601120025060.13344@tyholt-ng.uninett.no References: 200601100953.k0A9rrTV049797@dis.cc.uit.no Pine.LNX.4.64.0601120025060.13344@tyholt-ng.uninett.no Message-ID: 1087.129.240.76.159.1137055274.squirrel@webmail.uio.no

We have had a local "brainstorming" here at UiO and we have come up with a couple of things and sorted them into three categories.

The first feature-category is to get things already in NAV3 operational :-) In this category we have the following issues: - vlanplot is unstable, especially the buttons controlling moves and updates tend to disappear now and then.. - we also see that vlanplot behaves quite different in different browsers, this is quite annoying for those of us using multiple platforms And of course the stuff that I have already posted to the list (on January 4th, without any response so far...)

The second feature-category is genuine new features; - Use of SNMPv2 counters (also mentioned before, but not there yet...) - Better "group-functionality" regarding users, sub-groups etc (and of course be able to restrict access on group basis) - Differenciate between anonymous (not logged in) users and users that have been authenticated (but have no privileges) - A system to check that all NAV-processes are up and running (and doing what they are supposed to do) - A more generic RADIUS-module to match 802.1x user-login to IP-address and port switch-port - Add a hook in the alarmmodule to be able to run an external script when an alarm occurs (to be able to export alarms to other systems like Tivoli Enterprise Console). This was implemented in one of the RCs, but did not get into the final version.

The third feature-category is more exotic, something for NAV7 or so I guess; - Extract and Open the "event-engine" of NAV to make it usable as a generic standalone eventhandler og alarm-console.

This is just a few words from our brainstorming. Please ask for more details if needed!!!

--Kjetil