forked from networktocode/ntc-templates
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge branch 'ntc_update' into 'master'
Support unknown protocol in arista_eos_show_interfaces_description (networktocode#1540) See merge request bsh-developers/ntc-templates!48
- Loading branch information
Showing
126 changed files
with
8,492 additions
and
1,226 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,44 @@ | ||
# Goals | ||
|
||
- The table below becomes an evolving reference of common capture group names | ||
- Normalize common capture groups across templates (including cross-vendor) | ||
|
||
# Reasoning | ||
|
||
Normalized capture group names enable more predictable structured data across templates where similar data exists. | ||
|
||
Example: Imagine the extra programming logic needed to consume structured data when capture groups could have two or more names across several templates or several vendors! Yikes! This is why we seek to normalize. | ||
|
||
# Considerations | ||
|
||
- Some capture groups are a single value and others are lists of values despite containing similar data as one another | ||
- Example: single IP address vs list of IP addresses | ||
- Normalizing and using standard capture group names will take time, persistence, and patience from the community | ||
- Other than new templates, these normalization changes modify the expected template output and are considered "breaking changes" to be included in version releases | ||
|
||
# Common Capture Groups | ||
|
||
| Capture Group | Usage Description | | ||
|--------------------|:------------------| | ||
| `BIA` | use this if the template already has MAC_ADDRESS in use for the active MAC address | | ||
| `DESCRIPTION` | often used for port or interface descriptions | | ||
| `GATEWAY` | gateway address for a subnet | | ||
| `INTERFACE` | full word instead of IFACE, INTF, INTFC, etc | | ||
| `IP_ADDRESS` | for a single IP address, often IPv4 | | ||
| `IP_ADDRESSES` | for lists of IPv4 addresses, but in the case of some templates there may be a mix of IP protocol versions | | ||
| `IP_HELPER` | for lists DHCP IP helper addresses | | ||
| `IP_VERSION` | Internet Protocol (IP) version in the case of multiple versions appearing in output (use where necessary) | | ||
| `IPV6_ADDRESS` | for a single IPv6 address | | ||
| `IPV6_ADDRESSES` | for lists of IPv6 addresses | | ||
| `IPV6_GATEWAY` | for IPv6 gateway address | | ||
| `LOCAL_IP_ADDRESS` | local IP address in the case of First Hop Redundancy Protocols (FHRP) | ||
| `MAC_ADDRESS` | instead of MAC or MACADDR | | ||
| `MGMT_IP_ADDRESS` | instead of MGMT_IP or MGMT_ADDRESS or MANAGEMENT_IP or REMOTE_MANAGEMENT_ADDRESS | | ||
| `NEIGHBOR_ID` | for router IDs remote to the system being parsed | | ||
| `NETMASK` | for IPv4 dotted quad masks | | ||
| `NETWORK` | for network numbers or subnet address (without the mask or prefix/slash notation); in place of ROUTE | | ||
| `PREFIX_LENGTH` | instead of PREFIX or CIDR for the numbers of a slash notation or CIDR mask | | ||
| `PROTOCOL` | instead of PROTO | | ||
| `ROUTER_ID` | for local router IDs (local to the device being parsed) | | ||
| `VLAN_ID` | instead of VLAN or TAG | | ||
| `VLAN_NAME` | VLAN name or description | |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,8 +1,5 @@ | ||
mkdocs==1.3.1 | ||
# Material for MkDocs theme | ||
mkdocs-material==8.3.9 | ||
# Render custom markdown for version added/changed/remove notes | ||
mkdocs==1.5.2 | ||
mkdocs-material==9.1.15 | ||
mkdocs-version-annotations==1.0.0 | ||
# Automatic documentation from sources, for MkDocs | ||
mkdocstrings==0.19 | ||
mkdocstrings-python==0.7.1 | ||
mkdocstrings-python==1.5.2 | ||
mkdocstrings==0.22.0 |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,34 @@ | ||
Value Required VLAN_ID (\d+) | ||
Value VLAN_NAME (\S+) | ||
Value STATUS (\S+) | ||
Value REASON (\S+) | ||
Value TYPE (\S+) | ||
Value List INTERFACES ([^,]+) | ||
|
||
Start | ||
^--- | ||
^VLAN\s+Name\s+Status -> VLANS | ||
^. -> Error | ||
|
||
VLANS | ||
^--- | ||
^\d+ -> Continue.Record | ||
# Lines starting with VLAN ID | ||
^${VLAN_ID}\s+${VLAN_NAME}\s+${STATUS}\s+${REASON}\s+${TYPE}\s*$$ | ||
^${VLAN_ID}\s+${VLAN_NAME}\s+${STATUS}\s+${REASON}\s+${TYPE}\s+${INTERFACES},* -> Continue | ||
^\d+\s+(?:\S+\s+){4}(?:[^,]+,){1}${INTERFACES},* -> Continue | ||
^\d+\s+(?:\S+\s+){4}(?:[^,]+,){2}${INTERFACES},* -> Continue | ||
^\d+\s+(?:\S+\s+){4}(?:[^,]+,){3}${INTERFACES},* -> Continue | ||
^\d+\s+(?:\S+\s+){4}(?:[^,]+,){4}${INTERFACES},* -> Continue | ||
^\d+\s+(?:\S+\s+){4}(?:[^,]+,){5}${INTERFACES},* -> Continue | ||
# Lines starting with multiple spaces | ||
^\s{6,}${INTERFACES},* -> Continue | ||
^\s{6,}(?:[^,]+,){1}${INTERFACES},* -> Continue | ||
^\s{6,}(?:[^,]+,){2}${INTERFACES},* -> Continue | ||
^\s{6,}(?:[^,]+,){3}${INTERFACES},* -> Continue | ||
^\s{6,}(?:[^,]+,){4}${INTERFACES},* -> Continue | ||
^\s{6,}(?:[^,]+,){5}${INTERFACES},* -> Continue | ||
# Dropping lines | ||
^\d+\s+\S+\s+\S+\s+\S+\s+\S+\s* | ||
^\s{6,} | ||
^.+ -> Error |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.