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. Change to OUI format (Brian Candler)
   2. [SCM] Netdot branch netdot-1.0 updated.
      netdot-1.0.4-77-g8e6d9eb ([email protected])
   3. [SCM] Netdot branch master updated.       netdot-1.0.4-77-g8e6d9eb
      ([email protected])
   4. [Netdot - Feature #1759] (Resolved) Updating DNS SOA
      externally ([email protected])
   5. [Netdot - Feature #1756] Migration to Pg ([email protected])


----------------------------------------------------------------------

Message: 1
Date: Wed, 12 Jun 2013 15:47:43 +0200
From: Brian Candler <[email protected]>
Subject: [Netdot-devel] Change to OUI format
To: [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

The downloaded oui.txt appears to have gained two spaces at the front of 
each line, and is no longer parsed properly.

Patch: (tested with netdot-1.0.2 but the code in netdot-1.0.4 appears to 
be the same)

--- lib/DBUTIL.pm~    2012-10-08 13:27:16.000000000 +0000
+++ lib/DBUTIL.pm    2013-06-12 13:41:15.535220214 +0000
@@ -506,7 +506,7 @@
      open (OUI, "<:encoding(iso-8859-1)","$oui_file") or die "Can't 
open $oui_file: $!\n";
      while (my $line = <OUI>){
          chomp $line;
-        if ($line =~ /^([0-9A-F]{6})\s+\(base 16\)\s+(.*)\s*$/i){
+        if ($line =~ /^\s*([0-9A-F]{6})\s+\(base 16\)\s+(.*)\s*$/i){
              $oui{$1} = $2;
          }
      }

(I would have raised this as a ticket on redmine, except my username 
doesn't appear to have privileges to create a new ticket)

Regards,

Brian.



------------------------------

Message: 2
Date: Wed, 12 Jun 2013 06:54:56 -0700
From: [email protected]
Subject: [Netdot-devel] [SCM] Netdot branch netdot-1.0 updated.
        netdot-1.0.4-77-g8e6d9eb
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  8e6d9eb5470d74dd38033429009b9804a5fadeb0 (commit)
      from  cd4e6c76446830c3479b78e9521788f8e560f071 (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 8e6d9eb5470d74dd38033429009b9804a5fadeb0
Author: Carlos Vicente <[email protected]>
Date:   Fri May 31 11:02:59 2013 -0400

    Deal with extra space in recent OUI.txt file

diff --git a/lib/DBUTIL.pm b/lib/DBUTIL.pm
index 55999b0..898f14f 100644
--- a/lib/DBUTIL.pm
+++ b/lib/DBUTIL.pm
@@ -506,7 +506,7 @@ sub insert_oui{
     open (OUI, "<:encoding(iso-8859-1)","$oui_file") or die "Can't open 
$oui_file: $!\n";
     while (my $line = <OUI>){
         chomp $line;
-        if ($line =~ /^([0-9A-F]{6})\s+\(base 16\)\s+(.*)\s*$/i){
+        if ($line =~ /^\s*([0-9A-F]{6})\s+\(base 16\)\s+(.*)\s*$/i){
             $oui{$1} = $2;
         }
     }

-----------------------------------------------------------------------

Summary of changes:
 lib/DBUTIL.pm |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)


hooks/post-receive
-- 
Netdot


------------------------------

Message: 3
Date: Wed, 12 Jun 2013 06:56:23 -0700
From: [email protected]
Subject: [Netdot-devel] [SCM] Netdot branch master updated.
        netdot-1.0.4-77-g8e6d9eb
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  8e6d9eb5470d74dd38033429009b9804a5fadeb0 (commit)
       via  cd4e6c76446830c3479b78e9521788f8e560f071 (commit)
      from  aa53227d6bcdc4a34208d6dedd2d90163a0e82bb (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:
 htdocs/management/mac.html |    4 ++--
 lib/DBUTIL.pm              |    2 +-
 2 files changed, 3 insertions(+), 3 deletions(-)


hooks/post-receive
-- 
Netdot


------------------------------

Message: 4
Date: Wed, 12 Jun 2013 08:56:08 -0700
From: [email protected]
Subject: [Netdot-devel] [Netdot - Feature #1759] (Resolved) Updating
        DNS SOA externally
To: [email protected], [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8


Issue #1759 has been updated by Carlos Vicente.

Status changed from New to Resolved
Resolution set to worksforme


----------------------------------------
Feature #1759: Updating DNS SOA externally
https://osl.uoregon.edu/redmine/issues/1759#change-3086

Author: Andy Linton
Status: Resolved
Priority: Normal
Assignee: 
Category: 
Target version: 
Resolution: worksforme


I've got a zone I'm managing with Netdot. When changes are made to the zone I 
can either export the new file manually or wait until a cron job does its 
magic. Then I need an external process to reload that file's data into my 
nameserver software (NSD). I'm also DNSSEC signing the zone.

My external process takes care of adding any extra info I need for DNSSEC and 
the actual signing before I reload. All this works fine but when it comes time 
for the DNSSEC key rollover I believe I have an issue. I can create new keys 
and sign the zone with them but that means the zone has changed and so the SOA 
serial needs updated to reflect that. The choices seem to be:

# I can update the serial externally but then it will be out of sync with the 
Netdot version.
# I can log into Netdot and force a change of the serial, export and then 
re-sign the zone.
# Trigger an update of the SOA serial in Netdot using some external mechanism, 
re-export and then re-sign the zone.

It's not clear how I do option 3) which is my preferred option!



-- 
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: Wed, 12 Jun 2013 08:56: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 Carlos Vicente.

Assignee set to Anton Berezin


----------------------------------------
Feature #1756: Migration to Pg
https://osl.uoregon.edu/redmine/issues/1756#change-3087

Author: Carlos Vicente
Status: New
Priority: Normal
Assignee: Anton Berezin
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


------------------------------

_______________________________________________
Netdot-devel mailing list
[email protected]
https://osl.uoregon.edu/mailman/listinfo/netdot-devel


End of Netdot-devel Digest, Vol 75, Issue 6
*******************************************

Reply via email to