0.10.0

This release is breaking backward compatibility.

The optional argument config_lock defaults to False now (i.e. after initializing the connection with the network device, it will not attempt to acquire the config DB.). NAPALM will request config lock only when required, just before trying to load the configuration. To release (unlock), one needs to discard config or commit.

Although it was a bug, the outer key of the dictionary returned by get_bgp_neighbors_detail becomes global (previously it returned the name of the routing table, i.e. inet.0, inet6.0, or inetflow.0). For more info, consult napalm-automation/napalm-base#227.

get_bgp_neighbors_detail didn't return down BGP neighbors. This was fixed in #149

Due to a bug in junos-eznc, our method get_ntp_stats was affected. For this reasons, we're now requiring junos-eznc >= 2.1.3. See #152 and #159. Make sure to remove any previous installation of junos-eznc (there were some issues with fetching the facts during init).

get_bgp_neighbors used to return empty structure for down neighbors. This was addressed in #155 and additionally, this brings some optimizations which should speed up the run time.

Some devices return * as MAC address when querying the address table. This triggered a bug in our MAC address normalization (#141), solved in #142 thanks to @stiltzkin10.

Enhancements:

• load_merge_candidate or load_replace_candidate are able to autodetect the config formats supported by Junos (text, json or xml), thanks to @zachmoody who submitted this pull request: #151
• More optional arguments:
  • key_file: #145 thanks to @stiltzkin10
  • timeout: #147 @zachmoody
  • ssh_config_file
• napalm-junos is now ready to receive the napalm-yang blessings: #140