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 netdot-1.0 updated.
netdot-1.0.1-79-g15d7d49 ([email protected])
2. [Netdot - Bug #1693] (Resolved) population of default_data
fails due to incorrect path ([email protected])
3. [Netdot - Feature #1649] Auto DNS on device hostnames
([email protected])
4. [Netdot - Feature #1636] IPv6 subnetting ([email protected])
5. [Netdot - Feature #1600] Multi-level hierarchical access
rights ([email protected])
6. [Netdot - Feature #1604] Dimensions for a site
([email protected])
7. [Netdot - Bug #1606] IPv6 Tree View "double bindings"
([email protected])
8. [Netdot - Bug #1607] Do not allow existence of RRs with only
an MX record pointing to itself ([email protected])
9. [Netdot - Feature #1609] Suggestion - assume host address if
no CIDR mask specified ([email protected])
10. [Netdot - Bug #1611] User should be given option to delete
recursively when deleting multiple IP blocks ([email protected])
----------------------------------------------------------------------
Message: 1
Date: Sun, 7 Oct 2012 18:37:28 -0700
From: [email protected]
Subject: [Netdot-devel] [SCM] Netdot branch netdot-1.0 updated.
netdot-1.0.1-79-g15d7d49
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 15d7d49480c36632d18c904e159ba2f515f455d8 (commit)
via c2596e976d483d98684d46698e3596ac3c5abf38 (commit)
from 21dec52f14242ffcacc245ae7e236d1eddd986ba (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 15d7d49480c36632d18c904e159ba2f515f455d8
Author: Carlos Vicente <[email protected]>
Date: Sun Oct 7 21:36:38 2012 -0400
Fix for Bug #1693 (population of default_data fails due to incorrect path)
diff --git a/lib/DBUTIL.pm b/lib/DBUTIL.pm
index 77d60d6..55999b0 100644
--- a/lib/DBUTIL.pm
+++ b/lib/DBUTIL.pm
@@ -456,7 +456,7 @@ CREATE USER $CONFIG{DB_NETDOT_USER} WITH PASSWORD
'$CONFIG{DB_NETDOT_PASS}' NOCR
sub insert_default_data{
my @data;
- my $file = "$CONFIG{CONFIG_DIR}/$CONFIG{DEFAULT_DATA}";
+ my $file = $CONFIG{DEFAULT_DATA};
if ( -f $file) {
print "Inserting default data\n";
open (DEFAULT, "<$file") or die "Can't open $file: $!";
commit c2596e976d483d98684d46698e3596ac3c5abf38
Author: Carlos Vicente <[email protected]>
Date: Sun Oct 7 21:36:07 2012 -0400
Corrections to upgrade script. Updated upgrade instructions
diff --git a/doc/UPGRADE b/doc/UPGRADE
index 6f01cea..994ef25 100644
--- a/doc/UPGRADE
+++ b/doc/UPGRADE
@@ -1,64 +1,53 @@
- == Instructions for Upgrading Netdot 0.9.10 to 1.0.x ==
+ == Instructions for Upgrading Netdot 1.0.1 to 1.0.2 ==
1. You will need to update the database schema in addition to the application.
IMPORTANT: MAKE SURE YOU MAKE A BACKUP COPY OF YOUR DATABASE BEFORE UPGRADING
-This new version of Netdot fixes a number of lax database constraints.
-This means that table columns were previously defined in such a way that
-their values could be undefined (NULL) or zero when they should not.
-In additiion, the new version adds UNIQUE constraints to some fields.
-
-It is very likely that applying these constraints to your current schema now
-will fail because there are cases where columns were set to "NULL" or zero,
-or cases where there are duplicate values. This means that you may end up
-with an inconsistent schema, hence the importance of having a backup copy
-of your database.
+This new version of Netdot fixes an incorrect UNIQUE constraint in the device
+table. It is possible that your database contains two or more devices using
the
+same name (RR). This means that the addition of the unique index to the device
+table may fail.
After making a backup copy of your database, please execute the following
command:
- make upgrade
+ # make upgrade
This will call a script that updates your current database to the schema
required
-by the version you are upgrading to. This may take a long time, depending on
the
-size of your database.
+by the version you are upgrading to.
Any errors found while applying these schema changes will be written to a file
called "error.log". You will need to inspect this file and make sure to correct
any problems before continuing. You may have to restore your database from
backup,
fix the data and start over.
-2. Run 'make testdeps' to make sure that you satisfy the new dependencies
-
-3. At this point you can do a 'make install'
+2. Check for new requirements:
-4. Be aware that Netdot does not include MIB files in the mibs/ directory any
more.
-This helps make Netdot more tolerant of changes in the aSNMP libraries
(SNMP::Info).
-You will need to download the latest version of the 'netdisco-mibs' package,
available
-here:
+ # make testdeps
- http://sourceforge.net/projects/netdisco/files/netdisco-mibs/
+You will notice that Netdot version 1.0.2 requires a specific version of the
+Net::Patricia Perl module. The module has been patched to satisfy our
requirements,
+but at the time of this writing, the patch has not been applied to the public
version.
+Therefore, we have included a patched version of the module. Netdot can
install it
+for you by doing:
-By default, Netdot expects each vendor directory in the following path:
+ # make installdeps
- /usr/share/netdisco/mibs
+* Side Note:
-So, for example, you can do something like:
+There is a bug ticket open for Net::Patricia:
- cd /tmp
- wget http://path-to-latest/netdisco-mibs.tar.gz
- mkdir -p /usr/share/netdisco/
- cd /usr/share/netdisco
- tar xzvf /tmp/netisco-mibs.tar.gz
- mv netdisco-mibs mibs
+ https://rt.cpan.org/Public/Bug/Display.html?id=79480
-5. Adjust your Site.conf file to reflect some changes:
+It would be helpful if you could write the author of the module asking that
the patch
+be applied.
-* Modify SNMP_MIBS_PATH and SNMP_MIBS_DIRS to match the actual path where
- you installed the mibs
+3. At this point you can do a
+ # make install
+4. Restart Apache
diff --git a/upgrade/Makefile b/upgrade/Makefile
index 544f996..c95a706 100644
--- a/upgrade/Makefile
+++ b/upgrade/Makefile
@@ -18,7 +18,7 @@ all: db tasks
db:
@echo
@echo "Upgrading schema and data..."
- $(PERL) updatedb 2>>error.log
+ $(PERL) updatedb 2>error.log
tasks:
@echo
diff --git a/upgrade/updatedb b/upgrade/updatedb
index edb6f5d..695b7e8 100644
--- a/upgrade/updatedb
+++ b/upgrade/updatedb
@@ -41,6 +41,10 @@ if ( $schema_version eq '1.0.1' ){
# Requires renaming existing indexes to be consistent with newly
generated
# schema in this version
push @statements,
+
+ 'ALTER TABLE device DROP foreign key fk_used_by;',
+ 'ALTER TABLE device DROP foreign key fk_owner_1;',
+
'ALTER TABLE device DROP INDEX `Device2`;',
'ALTER TABLE device DROP INDEX `Device3`;',
'ALTER TABLE device DROP INDEX `Device4`;',
@@ -48,7 +52,7 @@ if ( $schema_version eq '1.0.1' ){
'ALTER TABLE device DROP INDEX `Device6`;',
'ALTER TABLE device DROP INDEX `Device7`;',
'ALTER TABLE device DROP INDEX `Device8`;',
-
+
'ALTER TABLE device ADD UNIQUE INDEX `device2` (`name`);',
'ALTER TABLE device ADD INDEX `Device3` (`used_by`);',
@@ -58,7 +62,10 @@ if ( $schema_version eq '1.0.1' ){
'ALTER TABLE device ADD INDEX `Device7` (`down_from`);',
'ALTER TABLE device ADD INDEX `Device8` (`down_until`);',
'ALTER TABLE device ADD INDEX `Device9` (`extension`);',
-
+
+ 'ALTER TABLE device ADD CONSTRAINT `fk_owner_1` FOREIGN KEY (`owner`)
REFERENCES `entity` (`id`);',
+ 'ALTER TABLE device ADD CONSTRAINT `fk_used_by` FOREIGN KEY (`used_by`)
REFERENCES `entity` (`id`);',
+
"UPDATE schemainfo SET version='1.0.2' WHERE id=1;",
"DELETE FROM datacache;";
-----------------------------------------------------------------------
Summary of changes:
doc/UPGRADE | 57 +++++++++++++++++++++--------------------------------
lib/DBUTIL.pm | 2 +-
upgrade/Makefile | 2 +-
upgrade/updatedb | 11 ++++++++-
4 files changed, 34 insertions(+), 38 deletions(-)
hooks/post-receive
--
Netdot
------------------------------
Message: 2
Date: Sun, 7 Oct 2012 18:40:25 -0700
From: [email protected]
Subject: [Netdot-devel] [Netdot - Bug #1693] (Resolved) population of
default_data fails due to incorrect path
To: [email protected], [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8
Issue #1693 has been updated by Carlos Vicente.
Status changed from New to Resolved
Assignee set to Carlos Vicente
Resolution set to fixed
Thank you.
----------------------------------------
Bug #1693: population of default_data fails due to incorrect path
https://osl.uoregon.edu/redmine/issues/1693#change-2971
Author: Nick Hilliard
Status: Resolved
Priority: High
Assignee: Carlos Vicente
Category: Netdot
Target version: 1.0.2
Resolution: fixed
$CONFIG{DEFAULT_DATA} is defined in lib/DBUTIL.pm as follows:
> $CONFIG{DEFAULT_DATA} = "$CONFIG{CONFIG_DIR}/default_data";
However insert_default_data() initialises $file as:
> my $file = "$CONFIG{CONFIG_DIR}/$CONFIG{DEFAULT_DATA}";
So you end up with two path entries in the filename. This works ok if $rel_dir
is used, but breaks when you use absolute paths. This causes initial
installation failure.
--
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, 8 Oct 2012 00:06:05 -0700
From: [email protected]
Subject: [Netdot-devel] [Netdot - Feature #1649] Auto DNS on device
hostnames
To: [email protected], [email protected]
Cc: [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8
Issue #1649 has been updated by Fahmi Setiawan.
http://alkian.blogspot.com/2012/10/suarasepakbolacom-tempatnya-prediksi-bola-terakurat.html
http://alkian.blogspot.com/2012/10/fungsi-backlink-dalam-seo.html
----------------------------------------
Feature #1649: Auto DNS on device hostnames
https://osl.uoregon.edu/redmine/issues/1649#change-2972
Author: moe kraus
Status: New
Priority: Normal
Assignee:
Category: DNS
Target version:
Resolution:
Dear Team,
the ability to use SNMP information for changing DNS records dynamically does
only apply on interface records.
It would be nice if this would also works with the record of the device name.
Are there some caveats with changing the primary rr?
Kind regards,
Moe
--
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, 8 Oct 2012 00:06:35 -0700
From: [email protected]
Subject: [Netdot-devel] [Netdot - Feature #1636] IPv6 subnetting
To: [email protected], [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8
Issue #1636 has been updated by Fahmi Setiawan.
http://alkian.blogspot.com/2012/10/suarasepakbolacom-tempatnya-prediksi-bola-terakurat.html
http://alkian.blogspot.com/2012/10/fungsi-backlink-dalam-seo.html
----------------------------------------
Feature #1636: IPv6 subnetting
https://osl.uoregon.edu/redmine/issues/1636#change-2973
Author: Torunn Nikolaisen
Status: New
Priority: Normal
Assignee:
Category:
Target version:
Resolution:
Hi!
I recently started testing netdot for documenting our IPv6-block. I like it so
far and I'm looking forward to trying out the other functions besides the
IPAM. I like where you're going with rancid, cacti, nagios integration etc.
A challenge I've run into is that we need to subnet large blocks into many
sub-blocks. For example: 2001:db8:8000::/34 must be subnetted into 1024 /44
blocks. It's rather tedious to manually input 1024 nets using the Web-UI. I
upgraded to the latest git-master to get the "Add multiple blocks (from
partitions in container.mhtml)" function in ip.html and the ipv6.html file. But
from what I can see it only works for IPv4 for now? Is similar functionality
for IPv6 far off? Is there some known workaround for IPv6 for now?
Thanks for the great work you're sharing with us!
Kind regards,
Torunn Nikolaisen
--
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, 8 Oct 2012 00:07:15 -0700
From: [email protected]
Subject: [Netdot-devel] [Netdot - Feature #1600] Multi-level
hierarchical access rights
To: [email protected], [email protected],
[email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8
Issue #1600 has been updated by Fahmi Setiawan.
http://alkian.blogspot.com/2012/10/suarasepakbolacom-tempatnya-prediksi-bola-terakurat.html
http://alkian.blogspot.com/2012/10/fungsi-backlink-dalam-seo.html
----------------------------------------
Feature #1600: Multi-level hierarchical access rights
https://osl.uoregon.edu/redmine/issues/1600#change-2974
Author: Attila Heidrich
Status: Resolved
Priority: High
Assignee: Carlos Vicente
Category: IPManagement
Target version: 1.0
Resolution: fixed
It would be very nice to have the possibility to assing the rights for a given
ipblock, that it would be valid for all their children as well.
Like assigning view/edit rights for 10.10.0.0/16 should also mean, that if
10.10.10.0/24 exists, or happens to be created, the given user/group also have
the rights to manage this one the same way.
--
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: 6
Date: Mon, 8 Oct 2012 00:07:51 -0700
From: [email protected]
Subject: [Netdot-devel] [Netdot - Feature #1604] Dimensions for a site
To: [email protected], [email protected],
[email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8
Issue #1604 has been updated by Fahmi Setiawan.
http://alkian.blogspot.com/2012/10/suarasepakbolacom-tempatnya-prediksi-bola-terakurat.html
http://alkian.blogspot.com/2012/10/fungsi-backlink-dalam-seo.html
----------------------------------------
Feature #1604: Dimensions for a site
https://osl.uoregon.edu/redmine/issues/1604#change-2975
Author: Jos? Dom?nguez
Status: Resolved
Priority: Normal
Assignee: Carlos Vicente
Category: Netdot
Target version: 1.0
Resolution: fixed
It would be nice if we could have some column to represent the dimensions of a
building. gross square footage (gsf) would work. I guess this could be in the
comments field too but it might be useful to have that data. In any case, I
think I can live with having it in the comments field.
--
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: Mon, 8 Oct 2012 00:16:00 -0700
From: [email protected]
Subject: [Netdot-devel] [Netdot - Bug #1606] IPv6 Tree View "double
bindings"
To: [email protected], [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8
Issue #1606 has been updated by Fahmi Setiawan.
http://alkian.blogspot.com/2012/10/suarasepakbolacom-tempatnya-prediksi-bola-terakurat.html
http://alkian.blogspot.com/2012/10/fungsi-backlink-dalam-seo.html
----------------------------------------
Bug #1606: IPv6 Tree View "double bindings"
https://osl.uoregon.edu/redmine/issues/1606#change-2976
Author: Henrik Lans
Status: Resolved
Priority: High
Assignee: Joe Pletcher
Category:
Target version: 1.0
Resolution:
I've found a bug with IPv6 Tree View rendering, where sometimes a changed IPv6
subnet gets "double bindings" to its parent.
Try the following:
- Create a new IPv6 prefix, for example 2001:DB8::/32.
- Create a /127 prefix in that network, for example 2001:DB8::2/127.
- Edit the prefix and change it to 2001:DB8::/127.
- Click the /32 prefix and choose Tree View and you should now see TWO lines
connecting the /32 to the /127.
This seems to occur when you change the network address, and sometimes too the
subnet mask; sometimes only on the SECOND modification. I have not verified if
this also happens for IPv4 prefixes. It seems to be only cosmetic, the List
View is correct; but there seems to be something in the database not updating
100% correctly. The only fix I've found is to delete the /127 altogether and
add it again. For a /127, this is not so much work, but for a larger network
with hundreds of hosts, I imagine it'd be tedious...
--
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: Mon, 8 Oct 2012 00:16:22 -0700
From: [email protected]
Subject: [Netdot-devel] [Netdot - Bug #1607] Do not allow existence of
RRs with only an MX record pointing to itself
To: [email protected], [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8
Issue #1607 has been updated by Fahmi Setiawan.
http://alkian.blogspot.com/2012/10/suarasepakbolacom-tempatnya-prediksi-bola-terakurat.html
http://alkian.blogspot.com/2012/10/fungsi-backlink-dalam-seo.html
----------------------------------------
Bug #1607: Do not allow existence of RRs with only an MX record pointing to
itself
https://osl.uoregon.edu/redmine/issues/1607#change-2977
Author: Carlos Vicente
Status: Resolved
Priority: Normal
Assignee: Carlos Vicente
Category: DNS
Target version: 1.0
Resolution: fixed
--
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: 9
Date: Mon, 8 Oct 2012 00:16:38 -0700
From: [email protected]
Subject: [Netdot-devel] [Netdot - Feature #1609] Suggestion - assume
host address if no CIDR mask specified
To: [email protected], [email protected],
[email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8
Issue #1609 has been updated by Fahmi Setiawan.
http://alkian.blogspot.com/2012/10/suarasepakbolacom-tempatnya-prediksi-bola-terakurat.html
http://alkian.blogspot.com/2012/10/fungsi-backlink-dalam-seo.html
----------------------------------------
Feature #1609: Suggestion - assume host address if no CIDR mask specified
https://osl.uoregon.edu/redmine/issues/1609#change-2978
Author: Henrik Lans
Status: Resolved
Priority: Low
Assignee: Carlos Vicente
Category: IPManagement
Target version: 0.9.11
Resolution: fixed
I'd like to suggest a change when adding new IP blocks using
/netdot/management/address_tasks.html?view=new - when entering an IP address
without specifying a CIDR mask, I'd like the system to assume a /32 mask for
IPv4 or a /128 mask for IPv6 addresses. This would save having to type the
mask when entering a large number of static address assignments in one sitting.
--
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: 10
Date: Mon, 8 Oct 2012 00:16:58 -0700
From: [email protected]
Subject: [Netdot-devel] [Netdot - Bug #1611] User should be given
option to delete recursively when deleting multiple IP blocks
To: [email protected], [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8
Issue #1611 has been updated by Fahmi Setiawan.
http://alkian.blogspot.com/2012/10/suarasepakbolacom-tempatnya-prediksi-bola-terakurat.html
http://alkian.blogspot.com/2012/10/fungsi-backlink-dalam-seo.html
----------------------------------------
Bug #1611: User should be given option to delete recursively when deleting
multiple IP blocks
https://osl.uoregon.edu/redmine/issues/1611#change-2979
Author: Carlos Vicente
Status: New
Priority: Normal
Assignee:
Category: UserInterface
Target version: 0.9.11
Resolution:
--
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 67, Issue 7
*******************************************
