NAPALM Release 2.3.1 #697
Merged
NAPALM Release 2.3.1 #697
Conversation
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
On Debian, when installing `cryptography` in a clean environment, it fails with the error:
```bash
Downloading/unpacking chardet==3.0.4 (from -r requirements.txt (line 5))
Downloading/unpacking contextlib2==0.5.5 (from -r requirements.txt (line 6))
Downloading contextlib2-0.5.5-py2.py3-none-any.whl
Downloading/unpacking cryptography==2.1.4 (from -r requirements.txt (line 7))
Running setup.py (path:/tmp/pip-build-hfnqrc/cryptography/setup.py) egg_info for package cryptography
error in cryptography setup command: Invalid environment marker: python_version < '3'
Complete output from command python setup.py egg_info:
error in cryptography setup command: Invalid environment marker: python_version < '3'
```
When upgrading setuptools, cryptography installs without issues.
Similarly, cffi must be upgraded.
* junos fix nhs in get_bgp_config() * junos add test case for nhs in get_bgp_config() * junos fix missing policy in existing test case for nhs * junos fix E712 comparison * fix typo * junos remove nhs key in group level in get_bgp_config() * junos rework nhs in get_bgp_config() by fetching all policies in one go * junos fix test case for nhs get_bgp_config() * junos clean code and add comments in nhs get_bgp_config() * junos nhs remove inactive term in mocked data
As a temporary fix for #579
There's a bug when running against devices which output:
% Invalid input detected at '^' marker.
When running the "show ipv6 interface command"
The current get_interfaces_ip would result in:
{
"Vlan20": {
"ipv4": {
"172.29.50.3": {
"prefix_length": 27
}
}
},
"Vlan41": {
"ipv4": {
"172.29.52.34": {
"prefix_length": 27
},
"192.168.81.34": {
"prefix_length": 24
}
}
},
"^": {
"ipv6": {}
},
"%": {
"ipv6": {}
}
}
* Minor improvement to get_arp processing on NXOS SSH
* don't hide relevant import errors * original name * py2 compliance * now back to py3 compatibility....
get_bgp_neighbors: the key for the first dictionary is "global" not "default" if there are not VRFs
* improved exceptions - added new base exception * fixed pep8 issue * another pep8 issue fixed
* Start sharing common Netmiko code * Adding unit tests for new netmiko argument parsing * Adding NXOS to use netmiko argument processing * IOS-XR and netmiko args processing
* Update get_interfaces_ip to deal with unnumbered interfaces Unnumbered interfaces are listed in `show ip interface`, but have no `prefix` key. Take precautions for this, and inherit the IP of the interface it is borrowing from. Take the same precaution for ipv6. This fixes #630. * Extend tests for show_ip_interface Add an unnumbered interface to the tests.
* Adding VXLAN support: EVPN and control plane flags on mac address + new interface name * Fix #672: get_interfaces() crash with nve interfaces or no IP address * fix missing mgmt0 interface in the get_fact on N9K device * fix wrong description SVI on N9K device * fix some pep error and an EOL issue for a test case
Fixes #689 pip10 compatibility issue
* Apply correct format to code block * Add virtualbox provider flag to vagrant
* Cosmetic cleanup in line with PEP8, whitespace and indentation fixes * Address inconsistency in junos xml rpc calls for lldp interface information. Provide mapping of personality and model to call. Add tests to cover SRX_HIGHEND personality and QFX5110-48S-4C model. * Add two more cases where the RPC call for lldp neighbors interface detail is different to that documented
mirceaulinic
approved these changes
Apr 11, 2018
* Rolling version to 2.3.1 * Fixing linter issues introduced by new version of pylama
1 similar comment
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Depends on PR #696