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 Git repository branch netdot-1.0     updated.
      netdot-1.0.1-RC3-85-g688e4d8 (Apache)
   2. [Netdot - Feature #1632] Rework parallel polling  logic to
      improve performance ([email protected])
   3. [Netdot - Feature #1632] (In Progress) Rework     parallel
      polling logic to improve performance ([email protected])
   4. [Netdot - Feature #1669] Display circuit ID on the        backbone
      cable strand page ([email protected])
   5. [Netdot - Feature #1669] (Resolved) Display circuit       ID on the
      backbone cable strand page ([email protected])


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

Message: 1
Date: Wed, 1 Aug 2012 12:21:13 -0700
From: Apache <[email protected]>
Subject: [Netdot-devel] [SCM] Netdot Git repository branch netdot-1.0
        updated. netdot-1.0.1-RC3-85-g688e4d8
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 Git repository".

The branch, netdot-1.0 has been updated
       via  688e4d8bc95ce3ed24a3b93b863987eaaaf908cf (commit)
      from  0dcfec40b232855715088f9d2d3503c7e9dcffb7 (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 688e4d8bc95ce3ed24a3b93b863987eaaaf908cf
Author: Carlos Vicente <[email protected]>
Date:   Wed Aug 1 15:21:02 2012 -0400

    Allow multiple edit on result set from DNS record search

diff --git a/htdocs/management/host_tasks.html 
b/htdocs/management/host_tasks.html
index a8ecaaa..db8f8fa 100644
--- a/htdocs/management/host_tasks.html
+++ b/htdocs/management/host_tasks.html
@@ -218,7 +218,7 @@ if ( $action eq "search" && $submit ){
            print "Query <em>$search</em> returned: ".scalar(@list)." matches";
            print "</div>";
            print '<div class="containerbody">';
-           $m->comp('/generic/sortresults.mhtml', object=>\@list, withedit=>0);
+           $m->comp('/generic/sortresults.mhtml', object=>\@list, withedit=>1);
            print "</div>\n</div>";
        }
     } else {

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

Summary of changes:
 htdocs/management/host_tasks.html |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)


hooks/post-receive
-- 
Netdot Git repository


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

Message: 2
Date: Wed, 1 Aug 2012 12:51:07 -0700
From: [email protected]
Subject: [Netdot-devel] [Netdot - Feature #1632] Rework parallel
        polling logic to improve performance
To: [email protected], [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8


Issue #1632 has been updated by Carlos Vicente.

Assignee changed from Carlos Vicente to Anton Berezin


----------------------------------------
Feature #1632: Rework parallel polling logic to improve performance
https://osl.uoregon.edu/redmine/issues/1632

Author: Carlos Vicente
Status: New
Priority: High
Assignee: Anton Berezin
Category: DeviceManagement
Target version: 1.0
Resolution: 


Today Netdot forks processes to query each device via SNMP/SSH and update its 
information in the DB. Right now, with 1500+ devices and a fast machine, Netdot 
can hardly finish updating all devices, including their full details and 
ARP/forwarding tables. A couple of ideas for improving this:

a) Use Unix sockets to allow the children processes to communicate the SNMP 
values back to the parent, and have the parent update the DB in one go. This 
would reduce DB contention, which may also improve speed.
b) Reduce the number of reads/writes to the DB in Device.pm. E.g., get all the 
device info with one complex DB query (with joins), instead of using 
Class::DBI's accessors each time an object is needed. Similarly for writes.
c) Study the possibility of ditching Net::IPTrie and using Net::Patricia 
instead for keeping the IP hierarchy up to date


-- 
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: Wed, 1 Aug 2012 12:53:14 -0700
From: [email protected]
Subject: [Netdot-devel] [Netdot - Feature #1632] (In Progress) Rework
        parallel polling logic to improve performance
To: [email protected], [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8


Issue #1632 has been updated by Carlos Vicente.

Status changed from New to In Progress

For item a) we have discussed the possibility to use asynchronous SNMP queries. 
More about that later.

----------------------------------------
Feature #1632: Rework parallel polling logic to improve performance
https://osl.uoregon.edu/redmine/issues/1632

Author: Carlos Vicente
Status: In Progress
Priority: High
Assignee: Anton Berezin
Category: DeviceManagement
Target version: 1.0
Resolution: 


Today Netdot forks processes to query each device via SNMP/SSH and update its 
information in the DB. Right now, with 1500+ devices and a fast machine, Netdot 
can hardly finish updating all devices, including their full details and 
ARP/forwarding tables. A couple of ideas for improving this:

a) Use Unix sockets to allow the children processes to communicate the SNMP 
values back to the parent, and have the parent update the DB in one go. This 
would reduce DB contention, which may also improve speed.
b) Reduce the number of reads/writes to the DB in Device.pm. E.g., get all the 
device info with one complex DB query (with joins), instead of using 
Class::DBI's accessors each time an object is needed. Similarly for writes.
c) Study the possibility of ditching Net::IPTrie and using Net::Patricia 
instead for keeping the IP hierarchy up to date


-- 
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: Wed, 1 Aug 2012 13:37:55 -0700
From: [email protected]
Subject: [Netdot-devel] [Netdot - Feature #1669] Display circuit ID on
        the     backbone cable strand page
To: [email protected], [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8


Issue #1669 has been updated by Alastair Sheppard.


I've downloaded the change from git, looks lovely. Thanks
----------------------------------------
Feature #1669: Display circuit ID on the backbone cable strand page
https://osl.uoregon.edu/redmine/issues/1669

Author: Alastair Sheppard
Status: New
Priority: Normal
Assignee: 
Category: CablePlant
Target version: 1.0.1
Resolution: 


On the backbone cable page, in the cable strands section would it be possible 
to show the Circuit name as one of the columns? It would give a quick view of 
what each strand is connected to at each end (provided one named their circuit 
properly in such a way).

Cheers Alastair


-- 
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: Thu, 2 Aug 2012 10:02:23 -0700
From: [email protected]
Subject: [Netdot-devel] [Netdot - Feature #1669] (Resolved) Display
        circuit ID on the backbone cable strand page
To: [email protected], [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8


Issue #1669 has been updated by Carlos Vicente.

Status changed from New to Resolved
Assignee set to Carlos Vicente
Resolution set to fixed


----------------------------------------
Feature #1669: Display circuit ID on the backbone cable strand page
https://osl.uoregon.edu/redmine/issues/1669

Author: Alastair Sheppard
Status: Resolved
Priority: Normal
Assignee: Carlos Vicente
Category: CablePlant
Target version: 1.0.1
Resolution: fixed


On the backbone cable page, in the cable strands section would it be possible 
to show the Circuit name as one of the columns? It would give a quick view of 
what each strand is connected to at each end (provided one named their circuit 
properly in such a way).

Cheers Alastair


-- 
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 65, Issue 2
*******************************************

Reply via email to