Changes between Version 4 and Version 5 of WikiStart


Ignore:
Timestamp:
11/17/11 17:43:37 (13 years ago)
Author:
Kris Deugau
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • WikiStart

    v4 v5  
    77On trying to make sense of the existing tool's database structure, and how it handled netblocks (basically, it didn't;  it allocated ranges of IP addresses which were free to begin and end places other than CIDR boundaries), I started replacing data structures and code to get the stored data consistent enough to export to [http://www.rwhois.net rWHOIS].  That basic need was met before using source control, and is represented by r4 - almost a complete replacement of the original code.
    88
    9 Code has since developed to support most of the needs of a medium-sized ISP.  As of writing, code up to SVN revision r396 (/branches/stable) has been in live production use.
     9Code has since developed to support most of the needs of a medium-sized ISP.  Aside from a handful of peripheral company-specific changes not yet supported as configuration options, /branches/stable has been in live production use on an ongoing basis.
     10
     11=== Releases ===
     12
     13==== Stable version, v2.7 ====
     14[https://secure.deepnet.cx/releases/ipdb/ipdb-2.7.tar.gz Tarball][[br]]
     15[https://secure.deepnet.cx/svn/ipdb/tags/2.7 SVN tag][[br]]
     16[https://secure.deepnet.cx/svn/ipdb/branches/stable SVN latest patch]
     17
     18==== Development ====
     19
     20The Subversion tree root is https://secure.deepnet.cx/svn/ipdb.  A few large features have had branches created to isolate known-broken checkpoint checkins from other development work, but most other work is done directly on /trunk.  Bugfixes are sometimes initially committed to /branches/stable, then merged back to /trunk.
    1021
    1122=== (Mis)Features: ===
    1223
    13 As of v2.6:
    14 
    15 - mostly supports IPv6, although a few segments still assume v4 addresses.
    16 - internal data structures emulate the general routing configuration of most networks, although
    17   it does not directly represent or emulate deep routing chains.
    18 - "maxiumum contiguous free space" allocation alogorithm;  if a /29 and /26 are allocated from a /24, then allocation of a /27 will happen from the free space between the /29 and /26.  Planned enhancement:  Reserve space for expanding a block (#24).
     24- Stable branch supports IPv6, although there may still be a few lurking bugs, and there are "recommended practices" for v6 allocations that are not implemented.  See #24, among others.
     25- Internal data structures emulate the general routing configuration of most networks, although it does not directly represent or emulate deep routing chains.
     26- "Maxiumum contiguous free space" allocation alogorithm;  if a /29 and /26 are allocated from a /24, then allocation of a /27 will happen from the free space between the /29 and /26.  Planned enhancement:  Reserve space for expanding a block (#24).
    1927
    2028  This also relies on NOC staff using the IPDB allocation interface to request address space for customers, rather than looking at what's free on the router and using something handy...  as well as relying on NOC staff to enter whatever arbitrary changes they've made.  Planned enhancement:  Module to walk router configs (either live or backup copies) and compare with allocations as listed (#25).
    21 - hook to support checks against an external system for customer IDs
     29- Hook to support checks against an external system for customer IDs
    2230- rWHOIS export with either organization name/address or customer data as contact for published netblocks.  This can be toggled on a per-allocation basis.  Note that you still need to submit SWIP templates (if you're getting address space from ARIN) if you wish to delegate rDNS nameserver authority on /24 and larger blocks.
    23 - preliminary support for email notifications to arbitrary destinations on any action.  Currently, static IP assignments, netblock assignments, deallocations, and updates to blocks with the SWIP flag set will generate notices.
     31- Preliminary support for email notifications to arbitrary destinations on any action.  Currently, static IP assignments, netblock assignments, deallocations, and updates to blocks with the SWIP flag set will generate notices.
    2432
    2533=== Notes on SVN history ===