Hi Burton,
Burton M. Strauss III writes:
> Dinesh and Luca:
>
> I really don't like the FC enabled menus. Some of the reorg is really nice
> (I wish I had thought of it - it flows so much better), but the intermixing
> of FC, SCSI and IP bothers me.
Thanks for your feedback. I'm in agreement with you related to the
intermixing. It is a Frankenstein of menus :)
>
> Given that FC is pretty much all or nothing - for those who need it, it's
> all that matters and for those who don't it's irrelevant (and that's most
This is not entirely true when you deploy ntop in situations where there is
FCIP (FC tunnelled over TCP/IP) and people like to look at traffic to
understand how much of their traffic is storage, voip etc.
> ntop users today), would it not be better to group ALL the FC stuff into
> separate menus.
I see the following problems with the proposed grouping:
- the current grouping makes FC look like a second-class citizen (three
separate top-level menus for IP are mixed into a single menu for FC).
- Having SCSI stand as a separate high-level entry is treating it differently
from other protocols at its level such as HTTP & Kazaa which are
potentially as important.
- It doesn't really solve the problem of those who are typical ntop users
today - those that are interested in FC or IP, but not both - because it
leaves a bunch of entries that are uninteresting.
What I was thinking about was the following:
- Get rid of the basic set of static html files completely (the list that
you included in your html file including Sessions.html).
- Generate the files dynamically.
- Depending on the use of the flags "--fc-only" and "--no-fc", get rid of
generating the appropriate set of menu items.
Since the menu items are generated dynamically, we can also display the first
page of the top-level HTML menu in the main pane. For example, when users click
on "Summary", display the page for "Traffic" along with displaying the submenu
panel. I have seen many people get confused when they click on a top-level menu
item and the main page doesn't change. This enhancement could be done
separately.
If we agree with this, then we can deal with the immediate problem of menus and
then spend some time talking about what is a better way of grouping and
displaying information.
> Given that I don't have FC or iSCSI, I don't know if these make sense for
> those users. Oh, and with the available room, you can probably expand the
> descriptions a few chars (what is TM?).
I agree with your critique of names, TM is bad !. Here is a link to a captured
trace with FC traffic for your perusing pleasure :) BTW, in case neither you
nor Luca were aware, I have added support for all FC & SCSI stuff in Ethereal
and so you can browse the capture file using Ethereal (pick the latest version
of most of the bug fixes).
http://www.employees.org/~ddutt/hostdisk-isl.cap.bz2
Dinesh
--
My life is my message - Gandhi
_______________________________________________
Ntop-dev mailing list
[EMAIL PROTECTED]
http://listgateway.unipi.it/mailman/listinfo/ntop-dev
