[LISPMAP-146] remove configuration knobs from custom.properties Created: 17/Jan/17  Updated: 22/Aug/19

Status: Confirmed
Project: lispflowmapping
Component/s: General
Affects Version/s: Carbon
Fix Version/s: None

Type: Bug Priority: High
Reporter: Robert Varga Assignee: Lori Jakab
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All

Issue Links:
Blocks
blocks ODLPARENT-34 Remove project-specific settings from... Resolved
External issue ID: 7572

 Description   

odlparent's custom.properties contains a bunch of knobs:

  1. LISP Flow Mapping configuration
  2. Enable merging RLOC sets received from different xTR-IDs for the same EID (default: false)
    lisp.mappingMerge = false
  3. Enable the Solicit-Map-Request (SMR) mechanism (default: true)
    lisp.smr = true
  4. Choose policy for Explicit Locator Path (ELP) handling
  5. There are three options:
  6. default: don't add or remove locator records, return mapping as-is
  7. both: keep the ELP, but add the next hop as a standalone non-LCAF locator with a lower priority
  8. replace: remove the ELP, add the next hop as a standalone non-LCAF locator
    lisp.elpPolicy = default

We have better configuration tools, this configuration should use them and live in lispflowmapping project.

Their presence constitutes an inter-project circular dependency.

 Comments   
Comment by Robert Varga [ 22/Aug/19 ]

ljakab any progress on this?

Comment by Lori Jakab [ 22/Aug/19 ]

No progress, I haven't looked at this in a while. Let's target Magnesium with this, and if no progress by then, just remove those properties from odlparent.

Comment by Robert Varga [ 22/Aug/19 ]

Fair enough, those properties will be gone in odlparent-7, i.e. around April 2020.

Comment by Lori Jakab [ 22/Aug/19 ]

Ack.

Generated at Wed Feb 07 20:06:36 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.