PyNSO
Overview
A Python client library for Cisco NSO (previously tail-f)
Installation
To install use pip:
$ pip install pynso
Or clone the repo:
$ git clone https://github.com/DimensionDataCBUSydney/pynso.git $ python setup.py install
Usage
from pprint import pprint
from pynso.client import NSOClient
from pynso.datastores import DatastoreType
# Setup a client
client = NSOClient('10.123.92.12', 'admin', 'admin')
# Get information about the API
print('Getting API version number')
pprint(client.info()['version'])
# Get the information about the running datastore
print('Getting the contents of the running datastore')
pprint(client.get_datastore(DatastoreType.RUNNING))1 maintainer
Metadata
1 maintainer
Release files for pynso 1.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| pynso-1.2.0.zip | 10.3 kB | Without provenance | Details |
Release files / pynso-1.2.0.zip
| Download URL | pynso-1.2.0.zip |
|---|---|
| Size | 10.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
dc2d1e022b9cc7e7afa7c2448be7d9b3655839dea87eaec498452520033d65c6
|
|
BLAKE2b-256 checksum How to use checksums |
e68b2d6232846080c8f69a65eed62f677a58c041ad74afe4279fa2008f674617
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for pynso 1.2.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
