Organize scope-list in Subnet Matrix-frontend
Bug #1511363 reported by
Gro-Anita Vindheim
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Network Administration Visualized |
Fix Released
|
Wishlist
|
John-Magne Bredal |
Bug Description
NAV as IPAM (part 1)
-------------------
Our NAV-monitored network is growing (due to the NTNU merger, but also because we use more and more RFC1918-addresses),
and we find ourselves adding scopes in seeddb to monitor utilization.
We plan to use the subnet matrix-view to get an overview, but the front-end (start page showing multiple scopes) becomes rather messy when NAV har more than, say, 3 scopes.
We would like the start page to be organized f.ex in three columns:
<Official IPv4 adresses> <RFC1918-addr> <IPv6 addresses>
and each of these columns sorted by cidr.
I think this is an easy task, but it would be very useful to us :)
Changed in nav: | |
assignee: | nobody → John-Magne Bredal (john-m-bredal) |
milestone: | none → 4.4.0 |
Changed in nav: | |
importance: | Undecided → Wishlist |
Changed in nav: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Fix here: /nav.uninett. no/hg/default/ rev/2ee0429aa20 d
https:/