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. Adding less common DNS records (Andy Linton)
2. [SCM] Netdot branch netdot-1.0 updated.
netdot-1.0.4-62-g2dfeab5 ([email protected])
3. [SCM] Netdot branch netdot-1.0 updated.
netdot-1.0.4-63-gb8b0538 ([email protected])
4. [SCM] Netdot branch netdot-1.0 updated.
netdot-1.0.4-64-g92f5160 ([email protected])
----------------------------------------------------------------------
Message: 1
Date: Thu, 2 May 2013 10:54:55 +1200
From: Andy Linton <[email protected]>
Subject: [Netdot-devel] Adding less common DNS records
To: [email protected]
Message-ID:
<CALS-_OpdUesikDeoypJ9aa_Aqv5f6BykMvkXeFgz2=hgd_z...@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Currently I have a KEY resource record in the zone citylink.co.nz. I
want to use netdot to manage this zone but I don't see a way to record
the KEY record and then have it exported.
Should there be a way to allow the addition of this and other valid RR
types e.g.
http://en.wikipedia.org/wiki/List_of_DNS_record_types
Here's the record:
$ dig any banks.citylink.co.nz
; <<>> DiG 9.3.4-P1.2 <<>> any banks.citylink.co.nz
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 64508
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 2, ADDITIONAL: 2
;; QUESTION SECTION:
;banks.citylink.co.nz. IN ANY
;; ANSWER SECTION:
banks.citylink.co.nz. 600 IN A 202.8.44.8
banks.citylink.co.nz. 600 IN KEY 16896 4 1
AQPO01hiXVq7ezqFtLqMFyRYI1L9nMm2WX0JJmj+H/pARhZGiD9B7H8q
xZSRTJ+XiByUuoB2Gc6qsiQ1PXO5SJRpJ1sbmCX4PXaoe3eNmdRAlxEC
EieCLs6OZWnQrJNYx2PSnKmTw+TG1seWBBtmlgkfEjWtdrj9VIxCXOtZ p7KYfw==
;; AUTHORITY SECTION:
citylink.co.nz. 600 IN NS dns2.citylink.co.nz.
citylink.co.nz. 600 IN NS dns1.citylink.co.nz.
;; ADDITIONAL SECTION:
dns1.citylink.co.nz. 600 IN A 202.8.44.153
dns2.citylink.co.nz. 600 IN A 202.8.47.6
;; Query time: 0 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Thu May 2 10:49:56 2013
;; MSG SIZE rcvd: 270
------------------------------
Message: 2
Date: Thu, 2 May 2013 07:14:27 -0700
From: [email protected]
Subject: [Netdot-devel] [SCM] Netdot branch netdot-1.0 updated.
netdot-1.0.4-62-g2dfeab5
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, netdot-1.0 has been updated
via 2dfeab5c261f5104dce72b092a895924eba6b627 (commit)
from 0d4a8b1246c89aeb7c023a98a398790db0ae4eff (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 -----------------------------------------------------------------
commit 2dfeab5c261f5104dce72b092a895924eba6b627
Author: Carlos Vicente <[email protected]>
Date: Thu May 2 10:14:11 2013 -0400
Avoid error when listing bgp peerings with no entity
diff --git a/lib/Netdot/Model/Device.pm b/lib/Netdot/Model/Device.pm
index 5a03670..9d951c3 100644
--- a/lib/Netdot/Model/Device.pm
+++ b/lib/Netdot/Model/Device.pm
@@ -3567,7 +3567,7 @@ sub bgppeers_by_id {
sub bgppeers_by_entity {
my ( $self, $peers, $sort ) = @_;
- $self->isa_object_method('bgppeers_by_id');
+ $self->isa_object_method('bgppeers_by_entity');
$sort ||= "name";
unless ( $sort =~ /^name|asnumber|asname$/o ){
@@ -3576,7 +3576,7 @@ sub bgppeers_by_entity {
my $sortsub = ($sort eq "asnumber") ?
sub{$a->entity->$sort <=> $b->entity->$sort} :
sub{$a->entity->$sort cmp $b->entity->$sort};
- my @peers = sort $sortsub @$peers;
+ my @peers = sort $sortsub grep { defined $_->entity } @$peers;
return unless scalar @peers;
return \@peers;
@@ -3624,9 +3624,9 @@ sub get_bgp_peers {
@peers = grep { $_->asnumber eq $argv{as} } $self->bgppeers;
}elsif ( $argv{type} ){
if ( $argv{type} eq "internal" ){
- @peers = grep { $_->entity->asnumber == $self->bgplocalas }
$self->bgppeers;
+ @peers = grep { defined $_->entity && $_->entity->asnumber ==
$self->bgplocalas } $self->bgppeers;
}elsif ( $argv{type} eq "external" ){
- @peers = grep { $_->entity->asnumber != $self->bgplocalas }
$self->bgppeers;
+ @peers = grep { defined $_->entity && $_->entity->asnumber !=
$self->bgplocalas } $self->bgppeers;
}elsif ( $argv{type} eq "all" ){
@peers = $self->bgppeers();
}else{
-----------------------------------------------------------------------
Summary of changes:
lib/Netdot/Model/Device.pm | 8 ++++----
1 files changed, 4 insertions(+), 4 deletions(-)
hooks/post-receive
--
Netdot
------------------------------
Message: 3
Date: Thu, 2 May 2013 07:25:16 -0700
From: [email protected]
Subject: [Netdot-devel] [SCM] Netdot branch netdot-1.0 updated.
netdot-1.0.4-63-gb8b0538
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, netdot-1.0 has been updated
via b8b053839e99fb022617a4ec74ef310a5ab0edb6 (commit)
from 2dfeab5c261f5104dce72b092a895924eba6b627 (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 -----------------------------------------------------------------
commit b8b053839e99fb022617a4ec74ef310a5ab0edb6
Author: Carlos Vicente <[email protected]>
Date: Thu May 2 10:25:07 2013 -0400
Ensure that asname and orgname are set in Device::_get_as_info()
diff --git a/lib/Netdot/Model/Device.pm b/lib/Netdot/Model/Device.pm
index 9d951c3..c8ddb28 100644
--- a/lib/Netdot/Model/Device.pm
+++ b/lib/Netdot/Model/Device.pm
@@ -5128,6 +5128,8 @@ sub _get_as_info{
$results{orgname} = $descr;
$logger->debug(sub{"Device::_get_as_info:: $server: Found orgname:
$descr"});
}
+ $results{orgname} ||= $asn;
+ $results{asname} ||= $results{orgname};
return \%results if %results;
return;
}
-----------------------------------------------------------------------
Summary of changes:
lib/Netdot/Model/Device.pm | 2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
hooks/post-receive
--
Netdot
------------------------------
Message: 4
Date: Thu, 2 May 2013 07:46:56 -0700
From: [email protected]
Subject: [Netdot-devel] [SCM] Netdot branch netdot-1.0 updated.
netdot-1.0.4-64-g92f5160
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, netdot-1.0 has been updated
via 92f5160f12dfcaec085cf506e47e476cf81a4e13 (commit)
from b8b053839e99fb022617a4ec74ef310a5ab0edb6 (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 -----------------------------------------------------------------
commit 92f5160f12dfcaec085cf506e47e476cf81a4e13
Author: Carlos Vicente <[email protected]>
Date: Thu May 2 10:46:43 2013 -0400
Small correction
diff --git a/lib/Netdot/Model/Device.pm b/lib/Netdot/Model/Device.pm
index c8ddb28..4c0cc81 100644
--- a/lib/Netdot/Model/Device.pm
+++ b/lib/Netdot/Model/Device.pm
@@ -2625,6 +2625,7 @@ sub update_bgp_peering {
}else{
$logger->warn( sprintf("%s: Missing peer info. Cannot associate peering
%s with an entity",
$host, $peer->{address}) );
+ $entity = Entity->search(name=>"Unknown")->first;
}
# Create a hash with the peering's info for update or insert
-----------------------------------------------------------------------
Summary of changes:
lib/Netdot/Model/Device.pm | 1 +
1 files changed, 1 insertions(+), 0 deletions(-)
hooks/post-receive
--
Netdot
------------------------------
_______________________________________________
Netdot-devel mailing list
[email protected]
https://osl.uoregon.edu/mailman/listinfo/netdot-devel
End of Netdot-devel Digest, Vol 74, Issue 2
*******************************************
