Send Netdot-devel mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
https://osl.uoregon.edu/mailman/listinfo/netdot-devel
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Netdot-devel digest..."
Today's Topics:
1. [SCM] Netdot branch master updated. netdot-1.0.4-56-gca6e8bc
([email protected])
2. [Netdot - Feature #531] Solve the problem of overlapping VLAN
and address space ([email protected])
----------------------------------------------------------------------
Message: 1
Date: Tue, 23 Apr 2013 14:11:55 -0700
From: [email protected]
Subject: [Netdot-devel] [SCM] Netdot branch master updated.
netdot-1.0.4-56-gca6e8bc
To: [email protected]
Message-ID: <[email protected]>
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "Netdot".
The branch, master has been updated
via ca6e8bc97712d24650af4d0ebb25a3b9d57c3bbe (commit)
via 8fe5c1637d7ab939640982f61f4686bd0d6b95f2 (commit)
via da5f54dfb9e70be04be87e785421e4dd8eecf6ec (commit)
via f365efd33b8a77c3d195e1f338701a83b1804031 (commit)
via f2eba25a82194da38d619f9d94bbb3017be399a6 (commit)
via 02e3c1740d8253b4708c1a1187757b397fa271d0 (commit)
via 5626c865be7a1a47234914d31bddfd2eb682bf5a (commit)
via dbb47a09085238ac7baa06a8fa01abdfac02eb65 (commit)
via 73b8d67dcf5d33799c365c54497bb371807aeb1d (commit)
via 763a37251c79baddb83b47f47c08ed28ce88d4f3 (commit)
via 2869589d9fc6aaf8581f3f6053a0fd70acd4936a (commit)
via 915bb9ca50a28025859ca8e531b52219cd138af0 (commit)
via d4e3d3ea90055994ab103eed19e1602b9d758420 (commit)
via f6fc05f4c91fbcaf1c8a5ac4019b0d62cac724db (commit)
via db58f9af94de00ba2498007ccfac2a482dba3b9f (commit)
via b50c577fbe3a42c747436388b73e620202561726 (commit)
via 6ef6f307e00ad8f04b61c678cb6d8e0f942edf85 (commit)
via 9760083cd726ec9ae779318b2bc0737fde20dd9e (commit)
via fad9c81abf551d5445973bc11ac0272b1b9d613f (commit)
via 825b74e83dbcc3259b6f2dbeb9beed30d5423306 (commit)
via 778e2b4dd2d2e3aa813867d7c1b1686b7fcac3dd (commit)
via 677cb0786a9f75cec67a3c4be8c076a9df5e9a72 (commit)
via 64daae1923f58f2145b90ff5272f5048c43de18d (commit)
via 2cb03664aec31d3347f152eef3c5bff379d88e5d (commit)
via 093464b335ecff59821d777e875ff83b29d8fe03 (commit)
from c6a46545611288ad58eba299faa3417efa04fc82 (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
-----------------------------------------------------------------------
Summary of changes:
bin/check_bgppeer.pl | 10 +-
bin/device_checks.pl | 3 +-
etc/Default.conf | 16 +-
etc/default_data | 2 +-
etc/netdot.meta | 61 ++++++-
htdocs/contacts/entities.html | 1 +
htdocs/management/device.html | 20 ++-
htdocs/management/ip.html | 8 +-
htdocs/rest/host | 2 +-
lib/Netdot.pm | 4 +-
lib/Netdot/Exporter.pm | 79 +++++---
lib/Netdot/Exporter/Nagios.pm | 402 +++++++++++++++++++++----------------
lib/Netdot/Exporter/Smokeping.pm | 16 +--
lib/Netdot/Model/Device.pm | 131 ++++++++-----
lib/Netdot/Model/DhcpScope.pm | 5 +-
lib/Netdot/Model/Ipblock.pm | 18 ++-
lib/Netdot/Model/RR.pm | 17 ++-
lib/Netdot/REST.pm | 33 ++--
upgrade/updatedb | 42 ++++
19 files changed, 566 insertions(+), 304 deletions(-)
hooks/post-receive
--
Netdot
------------------------------
Message: 2
Date: Wed, 24 Apr 2013 06:47:41 -0700
From: [email protected]
Subject: [Netdot-devel] [Netdot - Feature #531] Solve the problem of
overlapping VLAN and address space
To: [email protected], [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8
Issue #531 has been updated by Henrik Lans.
I definitely vote for this feature to be introduced as soon as possible in
Netdot, and using a structure similar to the one in the last post. As an
additional driver to the cases described above, I work in an ISP which is
absorbing a number of smaller networks that we've acquired over the years, and
it turns out that they too use RFC 1918 address space - who knew? ;-) We'd
very much like to use a single Netdot-instance to collect all our IP tracking,
but that means support for overlapping/conflicting space. We have no issue
with using a separate root objects ("admin domain X" in your hierarchy) for
each ISP network.
----------------------------------------
Feature #531: Solve the problem of overlapping VLAN and address space
https://osl.uoregon.edu/redmine/issues/531#change-3068
Author: Carlos Vicente
Status: New
Priority: Normal
Assignee: Carlos Vicente
Category:
Target version: 1.0
Resolution:
Solve the problem of overlapping VLAN and address space
--
You have received this notification because you have either subscribed to it,
or are involved in it.
To change your notification preferences, please click here:
http://osl.uoregon.edu/redmine/my/account
------------------------------
_______________________________________________
Netdot-devel mailing list
[email protected]
https://osl.uoregon.edu/mailman/listinfo/netdot-devel
End of Netdot-devel Digest, Vol 73, Issue 10
********************************************
