Junos-eznc

Latest version: v2.7.2

Safety actively analyzes 682361 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 9 of 10

1.0.1

Not secure
Bugs fixed:
- VMX personality
- to_json for Python 2.6
- <configuration> tag option in single hierarchy XML
- XML configuration can be loaded as string with format='xml'

New features:
- Reboot At now supported
- Support for IdentityFile from .ssh/config
- Users default keys will now be searched if no key or password is provided.

1.0.0

Not secure
Junos PyEZ Overview

The Junos PyEZ project is an open-source Apache 2.0 library for the Python programming language. The purpose of this "micro-framework" library is to enable the networking professional community to effectively utilize the Junos OS NETCONF and XML APIs.

The Junos PyEZ library can be used on any number of server environments supporting Python 2.6 and 2.7.

At the time of this writing, Junos PyEZ is not distributed on devices running Junos OS.

For feature documentation and community support, refer to the following URLs:
- Project Page hosted on the Juniper Networks TechWiki:
http://techwiki.juniper.net/Automation_Scripting/Junos_PyEZ
- Source code hosted on Github:
https://github.com/Juniper/py-junos-eznc
- Support forum hosted using Google Groups:
https://groups.google.com/forum/#!forum/junos-python-ez

Installing Junos PyEZ

Junos PyEZ can be installed directly from the PyPi repository by typing `pip install junos-eznc` at the system command line.

The "pip" installation process also installs any related dependent Python modules and libraries. Depending on your specific system, you might need to have the prerequisite build tools installed as well.

For the complete set of installation instructions for various platforms, see the Junos PyEZ project documentation at https://techwiki.juniper.net/Automation_Scripting/Junos_PyEZ/Installation.

Recommended Junos Release

Junos PyEZ can be used with any device running Junos OS, because they all support the NETCONF and Junos XML APIs. To take full advantage of the Junos PyEZ features, we recommend using Junos OS Release 11.4 or later release - see "Known Limitations and Restrictions" section for details. For more information about Junos OS releases, refer to the Juniper Networks technical documentation site at https://www.juniper.net/techpubs/en_US/release-independent/junos/information-products/pathway-pages/junos/product/index.html .

Supported Python Releases

The Junos PyEZ library has been tested with Python versions 2.6 and 2.7.
At the time of this writing PyEZ is not supported in Python 3.x environments. This restriction is due to dependencies on other Python modules, such as ncclient, that do not support Python 3.x.

Known Limitations and Restrictions

General
- Junos PyEZ maintains a "timeout" mechanism for each executed command and response pair. The default timeout is 30 seconds. You can override the default by using the Device.timeout property. If a timeout does occur, a timeout exception is raised.
- Some devices running Junos OS might disconnect the NETCONF session due to inactivity. This behavior has been observed on SRX Series Services Gateways. In such cases, an exception is raised upon execution of the next command. The Junos PyEZ library does not reconnect to the device in these inactivity scenarios. However, you can call Device.open() to reconnect.
- Command execution is synchronous and blocking. The underlying NETCONF transport library is the ncclient module. If your application requires asynchronous or nonblocking execution logic, you should investigate other libraries to wrap around the PyEZ framework such as Twisted or Python Threads.
- The `Device.cli()` method is intended to be used with interactive python, and as a means to facilitate the interactive experience as needed. Please do not use this for "screen-scraping" the CLI output for automation purposes.

Version-Specific Limitations

A couple software version-dependent limitations that must be noted:

0.4.0

Not secure
General bug fixes and minor enhancements per community feedback.

0.3.1

Not secure
Various bug fixes
Removed SRX structured resources
Moved examples to dedicated branch
FpcHwTable added
Pkgadd now returns False on error - Handling to be added soon.

0.2.0

Not secure
Framework now supports Python 2.6 and 2.7
Documentation support via Sphinx
Timeout for sw.install
add gather_facts option to device.open()
added auto_probe feature to Device
support for stringification of ConnectError expections


dev_201405014_srx
To mark the repo before we remove the cfg/srx into a separate repository.

0.1.2

Not secure
Increased unit-test coverage to 70% overall.
Fixed fact gathering issues.
Increased exception handling and introduced new project specific exceptions.

Page 9 of 10

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.