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 - Feature #1869] (New) Support Anycast addresses
([email protected])
2. [Netdot - Feature #1868] (Resolved) Do not automatically
delete IP addresses asociated with devices ([email protected])
3. [Netdot - Feature #1870] (New) Improve zonefile and DHCPD
config file generation ([email protected])
----------------------------------------------------------------------
Message: 1
Date: Thu, 9 Jul 2015 12:27:16 -0700
From: [email protected]
Subject: [Netdot-devel] [Netdot - Feature #1869] (New) Support Anycast
addresses
To: [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8
Issue #1869 has been reported by Carlos Vicente.
----------------------------------------
Feature #1869: Support Anycast addresses
https://osl.uoregon.edu/redmine/issues/1869
Author: Carlos Vicente
Status: New
Priority: Normal
Assignee:
Category: DeviceManagement
Target version:
Resolution:
As it is, Netdot does not understand Anycast. An IP address points to a single
interface.
Create a join table so that the Interface-IP relationship is many-to-many
--
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: Fri, 10 Jul 2015 09:44:37 -0700
From: [email protected]
Subject: [Netdot-devel] [Netdot - Feature #1868] (Resolved) Do not
automatically delete IP addresses asociated with devices
To: [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8
Issue #1868 has been updated by Carlos Vicente.
Status changed from New to Resolved
Resolution set to fixed
----------------------------------------
Feature #1868: Do not automatically delete IP addresses asociated with devices
https://osl.uoregon.edu/redmine/issues/1868#change-3307
Author: Carlos Vicente
Status: Resolved
Priority: High
Assignee: Carlos Vicente
Category:
Target version: 1.0.8
Resolution: fixed
Experience with Netdot has shown that automatically deleting IP addresses
associated with devices is problematic. These addresses are deleted in two ways
today:
* The device is deleted using the UI or the REST interface
* The device gets updated using SNMP or via REST, and the IP is not in the list
of addresses in use
We have observed the following situations:
* Due to SNMP agent bugs, or network connectivity, an SNMP discovery fails to
report all the IP addresses in use by a device.
* An IP address is removed temporarily from a device's interface configuration
* A device is deleted and for whatever reason the user does not desire to
delete all of the device's IP addresses
In all of the above cases, IP addresses had DNS A/AAAA or PTR records which
were deleted, causing outages and frustration.
The proposed solution is to change Netdot's behavior so that these IP addresses
have to be removed explicitly.
--
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: Fri, 10 Jul 2015 11:21:08 -0700
From: [email protected]
Subject: [Netdot-devel] [Netdot - Feature #1870] (New) Improve
zonefile and DHCPD config file generation
To: [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8
Issue #1870 has been reported by Carlos Vicente.
----------------------------------------
Feature #1870: Improve zonefile and DHCPD config file generation
https://osl.uoregon.edu/redmine/issues/1870
Author: Carlos Vicente
Status: New
Priority: High
Assignee: Carlos Vicente
Category: Netdot
Target version: 1.1.0
Resolution:
Currently, these exporter classes use a special table called 'hostaudit' to
determine whether the files need to be exported. This table is updated with a
new entry each time that a related record is updated in the DB. This process
has some important drawbacks:
* The code is complex and ugly
* There are cases when a change is made, and a second operation cancels the
previous change, resulting in two entries in the 'hostaudit' table. Even though
the resulting files are the same, the export happens anyways because there
isn't enough information to determine that the resulting file will be identical
as the previous one (except for the zone serial)
The proposed solution is to:
* Remove the 'hostaudit' table and related code
* Add a 'checksum' field to both the 'zone' table and the 'dhcpscope' table
* Each time an export is requested, the file is generated in memory. A checksum
is calculated on the result and it is compared with the current checksum in the
DB. The file is only printed to disk if the checksums are different.
--
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 100, Issue 2
********************************************
