Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
The igp graph processor functions similar to the linkstate-edge processor, with an ultimate goal of creating a pair of graph/edge-collections, one for the entire IPv4 link state topology and one for the entire IPv6 link state topology. The processor first copies all ls_nodes into a new ls_node_extended collection. It then de-duplicates ISIS level-1-2 entries (BGP-LS creates both a level-1 and a level-2 entry for the same individual router). After de-duplication the processor mines ls_prefix and ls_srv6_sid datasets and attaches relevant SR/SRv6 SIDs to nodes in ls_node_extended. Finally the processor performs data correlation creating graphDB edge entries for nodes, links, and ls_prefixes.
The processor also registers "IGP Domains" in a new data collection. This will become useful for interconnecting multiple BGP-connected domains in the graph when a new BGP Processor is added
Type of Change
Checklist