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. [Netdot - Bug #1729] (In Progress) unable to import NAPTR
from bind format data ([email protected])
2. [Netdot - Bug #1729] unable to import NAPTR from bind format
data ([email protected])
3. [Netdot - Feature #1756] (New) Migration to Pg
([email protected])
4. [Netdot - Feature #1756] Migration to Pg ([email protected])
5. IPv6 patches (Wim Vandersmissen)
6. [Netdot - Bug #1757] (New) Displaying spanning tree graphs
([email protected])
7. [Netdot - Bug #1757] (Feedback) Displaying spanning tree
graphs ([email protected])
8. Re: [Netdot - Bug #1757] (Feedback) Displaying spanning tree
graphs (Andy Linton)
9. [Netdot - Bug #1757] (Resolved) Displaying spanning tree
graphs ([email protected])
----------------------------------------------------------------------
Message: 1
Date: Mon, 6 May 2013 13:12:14 -0700
From: [email protected]
Subject: [Netdot-devel] [Netdot - Bug #1729] (In Progress) unable to
import NAPTR from bind format data
To: [email protected], [email protected],
[email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8
Issue #1729 has been updated by Anton Berezin.
Status changed from New to In Progress
This is a bug in Net::DNS::ZoneFile::Fast. Either wait for it to be fixed in
the next release of the module (after which Netdot's dependency should be
updated), or apply the patch manually. The actual reason that the bug is seen
in Netdot is because \r (^M) is added to each line submitted via a textarea;
so, an alternative would be to patch Netdot to strip \r's before invoking
Net::DNS::ZoneFile::Fast parser.
See https://rt.cpan.org/Ticket/Display.html?id=85099
----------------------------------------
Bug #1729: unable to import NAPTR from bind format data
https://osl.uoregon.edu/redmine/issues/1729#change-3069
Author: Karl Putland
Status: In Progress
Priority: Normal
Assignee: Anton Berezin
Category: DNS
Target version: 1.0.5
Resolution:
Trying to import these
srv.myvtel.com. IN NAPTR 10 0 "s" "SIP+D2U" "" _sip._udp.myvtel.com.
srv.myvtel.com. IN NAPTR 20 0 "s" "SIP+D2T" "" _sip._tcp.myvtel.com.
results in
Transaction aborted: Error parsing Zone data: bad NAPTR data, line 4
Stack:
[/usr/local/share/perl/5.14.2/Net/DNS/ZoneFile/Fast.pm:240]
[/usr/local/share/perl/5.14.2/Net/DNS/ZoneFile/Fast.pm:1003]
[/usr/local/share/perl/5.14.2/Net/DNS/ZoneFile/Fast.pm:157]
[/usr/local/netdot/lib/Netdot/Model/Zone.pm:653]
[/usr/local/netdot/htdocs/management/zone.html:46]
[/usr/local/netdot/htdocs/management/zone.html:47]
[/usr/local/netdot/htdocs/management/autohandler:81]
[/usr/local/share/perl/5.14.2/HTML/Mason/Request.pm:951]
[/usr/local/netdot/htdocs/masondata/obj/1292882063/management/autohandler.obj:21]
[/usr/local/netdot/htdocs/autohandler:76]
--
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
------------------------------
Message: 2
Date: Mon, 6 May 2013 13:16:09 -0700
From: [email protected]
Subject: [Netdot-devel] [Netdot - Bug #1729] unable to import NAPTR
from bind format data
To: [email protected], [email protected],
[email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8
Issue #1729 has been updated by Carlos Vicente.
Anton Berezin wrote:
> This is a bug in Net::DNS::ZoneFile::Fast. Either wait for it to be fixed in
> the next release of the module (after which Netdot's dependency should be
> updated), or apply the patch manually. The actual reason that the bug is
> seen in Netdot is because \r (^M) is added to each line submitted via a
> textarea; so, an alternative would be to patch Netdot to strip \r's before
> invoking Net::DNS::ZoneFile::Fast parser.
>
> See https://rt.cpan.org/Ticket/Display.html?id=85099
I think attacking the problem from both sides is probably a good idea.
Thanks
cv
----------------------------------------
Bug #1729: unable to import NAPTR from bind format data
https://osl.uoregon.edu/redmine/issues/1729#change-3070
Author: Karl Putland
Status: In Progress
Priority: Normal
Assignee: Anton Berezin
Category: DNS
Target version: 1.0.5
Resolution:
Trying to import these
srv.myvtel.com. IN NAPTR 10 0 "s" "SIP+D2U" "" _sip._udp.myvtel.com.
srv.myvtel.com. IN NAPTR 20 0 "s" "SIP+D2T" "" _sip._tcp.myvtel.com.
results in
Transaction aborted: Error parsing Zone data: bad NAPTR data, line 4
Stack:
[/usr/local/share/perl/5.14.2/Net/DNS/ZoneFile/Fast.pm:240]
[/usr/local/share/perl/5.14.2/Net/DNS/ZoneFile/Fast.pm:1003]
[/usr/local/share/perl/5.14.2/Net/DNS/ZoneFile/Fast.pm:157]
[/usr/local/netdot/lib/Netdot/Model/Zone.pm:653]
[/usr/local/netdot/htdocs/management/zone.html:46]
[/usr/local/netdot/htdocs/management/zone.html:47]
[/usr/local/netdot/htdocs/management/autohandler:81]
[/usr/local/share/perl/5.14.2/HTML/Mason/Request.pm:951]
[/usr/local/netdot/htdocs/masondata/obj/1292882063/management/autohandler.obj:21]
[/usr/local/netdot/htdocs/autohandler:76]
--
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
------------------------------
Message: 3
Date: Mon, 6 May 2013 13:50:49 -0700
From: [email protected]
Subject: [Netdot-devel] [Netdot - Feature #1756] (New) Migration to Pg
To: [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8
Issue #1756 has been reported by Carlos Vicente.
----------------------------------------
Feature #1756: Migration to Pg
https://osl.uoregon.edu/redmine/issues/1756
Author: Carlos Vicente
Status: New
Priority: Normal
Assignee:
Category: Netdot
Target version: 1.0.6
Resolution:
As discussed previously, we would like to start supporting PostgresQL only.
This ticket will track the migration tasks, which include:
* Using Pg's native support for IPv4 and IPv6 addresses
* Using table partitions to keep forwarding and ARP tables for longer
* Remove MySQL-specific pieces of code
* Write script to migrate the data
--
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
------------------------------
Message: 4
Date: Mon, 6 May 2013 13:57:52 -0700
From: [email protected]
Subject: [Netdot-devel] [Netdot - Feature #1756] Migration to Pg
To: [email protected], [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8
Issue #1756 has been updated by Wim Vandersmissen.
I'd love to keep mysql support if possible though, latest MySQL also has native
IPv4/IPv6 support (or using UDF functions in older versions), partitioning also
exists.
----------------------------------------
Feature #1756: Migration to Pg
https://osl.uoregon.edu/redmine/issues/1756#change-3071
Author: Carlos Vicente
Status: New
Priority: Normal
Assignee:
Category: Netdot
Target version: 1.0.6
Resolution:
As discussed previously, we would like to start supporting PostgresQL only.
This ticket will track the migration tasks, which include:
* Using Pg's native support for IPv4 and IPv6 addresses
* Using table partitions to keep forwarding and ARP tables for longer
* Remove MySQL-specific pieces of code
* Write script to migrate the data
--
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
------------------------------
Message: 5
Date: Mon, 06 May 2013 23:04:10 +0200
From: Wim Vandersmissen <[email protected]>
Subject: [Netdot-devel] IPv6 patches
To: [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Hi,
I've created some IPv6 patches:
https://osl.uoregon.edu/redmine/issues/1750 - More performant way of
adding IPv6 dynamic addresses
https://osl.uoregon.edu/redmine/issues/1747 - Option to disable
discovered IPv6 ipblocks
Any comments on those, or a reason to not add those patches to netdot ?
Thanks,
Wim
------------------------------
Message: 6
Date: Mon, 6 May 2013 17:38:48 -0700
From: [email protected]
Subject: [Netdot-devel] [Netdot - Bug #1757] (New) Displaying spanning
tree graphs
To: [email protected], [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8
Issue #1757 has been reported by Andy Linton.
----------------------------------------
Bug #1757: Displaying spanning tree graphs
https://osl.uoregon.edu/redmine/issues/1757
Author: Andy Linton
Status: New
Priority: Normal
Assignee:
Category: DeviceManagement
Target version:
Resolution:
If I look at the spanning tree tab for a device and try to run the [Graph It]
option I get this:
error: Can't locate object method "root_bridgse" via package "STPInstance" at
/usr/local/netdot/lib/Netdot/UI.pm line 2057.
context:
...
2053: my $g = GraphViz->new(%graph_args);
2054: my $start = Device->retrieve($id);
2055: my $stp_inst = STPInstance->search(device=>$id,
number=>$number)->first;
2056: return $g unless defined($stp_inst);
2057: my $start_root = $stp_inst->root_bridgse;
2058: return $g unless defined($start_root);
2059:
2060: my $devicemacs = Device->get_macs_from_all();
2061:
...
code stack: /usr/local/netdot/lib/Netdot/UI.pm:2057
/usr/local/netdot/lib/Netdot/UI.pm:2204
/usr/local/netdot/htdocs/management/device.html:1376
/usr/local/netdot/htdocs/management/autohandler:83
/usr/share/perl5/HTML/Mason/Request.pm:948
/usr/local/netdot/htdocs/masondata/obj/1249759374/management/autohandler.obj:21
/usr/local/netdot/htdocs/autohandler:76
raw error
Changing Line 2057 to:
2057: my $start_root = $stp_inst->root_bridge;
and restarting the web server fixes the problem.
--
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
------------------------------
Message: 7
Date: Tue, 7 May 2013 02:30:59 -0700
From: [email protected]
Subject: [Netdot-devel] [Netdot - Bug #1757] (Feedback) Displaying
spanning tree graphs
To: [email protected], [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8
Issue #1757 has been updated by Phil Regnauld.
Status changed from New to Feedback
Resolution set to duplicate
Andy Linton wrote:
>
> Changing Line 2057 to:
>
> 2057: my $start_root = $stp_inst->root_bridge;
>
> and restarting the web server fixes the problem.
Looks to me like a duplicate of Bug #1696
(https://osl.uoregon.edu/redmine/issues/1696), which is resolved in 1.0.3.
Which version are you running, and did you update since ?
----------------------------------------
Bug #1757: Displaying spanning tree graphs
https://osl.uoregon.edu/redmine/issues/1757#change-3072
Author: Andy Linton
Status: Feedback
Priority: Normal
Assignee:
Category: DeviceManagement
Target version:
Resolution: duplicate
If I look at the spanning tree tab for a device and try to run the [Graph It]
option I get this:
error: Can't locate object method "root_bridgse" via package "STPInstance" at
/usr/local/netdot/lib/Netdot/UI.pm line 2057.
context:
...
2053: my $g = GraphViz->new(%graph_args);
2054: my $start = Device->retrieve($id);
2055: my $stp_inst = STPInstance->search(device=>$id,
number=>$number)->first;
2056: return $g unless defined($stp_inst);
2057: my $start_root = $stp_inst->root_bridgse;
2058: return $g unless defined($start_root);
2059:
2060: my $devicemacs = Device->get_macs_from_all();
2061:
...
code stack: /usr/local/netdot/lib/Netdot/UI.pm:2057
/usr/local/netdot/lib/Netdot/UI.pm:2204
/usr/local/netdot/htdocs/management/device.html:1376
/usr/local/netdot/htdocs/management/autohandler:83
/usr/share/perl5/HTML/Mason/Request.pm:948
/usr/local/netdot/htdocs/masondata/obj/1249759374/management/autohandler.obj:21
/usr/local/netdot/htdocs/autohandler:76
raw error
Changing Line 2057 to:
2057: my $start_root = $stp_inst->root_bridge;
and restarting the web server fixes the problem.
--
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
------------------------------
Message: 8
Date: Tue, 7 May 2013 21:49:41 +1200
From: Andy Linton <[email protected]>
Subject: Re: [Netdot-devel] [Netdot - Bug #1757] (Feedback) Displaying
spanning tree graphs
To: [email protected]
Cc: [email protected]
Message-ID:
<CALS-_Oofgew=Az2NPtqLyWqhwexNviLcP29X+iHRe6Y7NjuW=w...@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
On Tue, May 7, 2013 at 9:30 PM, <[email protected]> wrote:
>
> Looks to me like a duplicate of Bug #1696
> (https://osl.uoregon.edu/redmine/issues/1696), which is resolved in 1.0.3.
> Which version are you running, and did you update since ?
>
Indeed. The particular system is 1.0.2 - time to upgrade!
------------------------------
Message: 9
Date: Tue, 7 May 2013 05:05:35 -0700
From: [email protected]
Subject: [Netdot-devel] [Netdot - Bug #1757] (Resolved) Displaying
spanning tree graphs
To: [email protected], [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8
Issue #1757 has been updated by Phil Regnauld.
Status changed from Feedback to Resolved
----------------------------------------
Bug #1757: Displaying spanning tree graphs
https://osl.uoregon.edu/redmine/issues/1757#change-3073
Author: Andy Linton
Status: Resolved
Priority: Normal
Assignee:
Category: DeviceManagement
Target version:
Resolution: duplicate
If I look at the spanning tree tab for a device and try to run the [Graph It]
option I get this:
error: Can't locate object method "root_bridgse" via package "STPInstance" at
/usr/local/netdot/lib/Netdot/UI.pm line 2057.
context:
...
2053: my $g = GraphViz->new(%graph_args);
2054: my $start = Device->retrieve($id);
2055: my $stp_inst = STPInstance->search(device=>$id,
number=>$number)->first;
2056: return $g unless defined($stp_inst);
2057: my $start_root = $stp_inst->root_bridgse;
2058: return $g unless defined($start_root);
2059:
2060: my $devicemacs = Device->get_macs_from_all();
2061:
...
code stack: /usr/local/netdot/lib/Netdot/UI.pm:2057
/usr/local/netdot/lib/Netdot/UI.pm:2204
/usr/local/netdot/htdocs/management/device.html:1376
/usr/local/netdot/htdocs/management/autohandler:83
/usr/share/perl5/HTML/Mason/Request.pm:948
/usr/local/netdot/htdocs/masondata/obj/1249759374/management/autohandler.obj:21
/usr/local/netdot/htdocs/autohandler:76
raw error
Changing Line 2057 to:
2057: my $start_root = $stp_inst->root_bridge;
and restarting the web server fixes the problem.
--
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 74, Issue 4
*******************************************
