Topology Connect
Topology Connect its a plugin (called a Platform Engine) for the Topology Modular Framework that allows to connect to and interact with an existing physical topology using SSH or Telnet.
This is particularly useful to perform tests on small, hardwired, already-built topologies inside a lab.
The main use case is to specify IPs of the devices using a Attribute Injection File (AIF) or by specifying the IPs to connect to in the topology description file itself (SZN file).
Documentation
Changelog
1.0.0
Changes
Allow platform to receive options, so it is compatible with the new Topology 1.10.0 “options” feature. [David Diaz]
0.4.0
Changes
Updated the base CommonConnectNode to support the Services API introduced in Topology Modular Framework 1.8.
Removed the hostname attribute in the base ConnectNode so it doesn’t clash with topology_docker hostname attribute. Same name, but different purpose. To connect to a node specify the fqdn attribute in the SZN or using attribute injection.
0.3.0
Fixes
Fixed issue #4 where the SshMixin created an attribute name collision with parent classes.
Changes
Removed placeholder documentation as the new Topology Modular Framework website will hold all documentation for the project and official plugins.
0.2.0
First beta version.
License
Copyright (C) 2015-2016 Hewlett Packard Enterprise Development LP
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing,
software distributed under the License is distributed on an
"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
KIND, either express or implied. See the License for the
specific language governing permissions and limitations
under the License.
1 maintainer
Metadata
1 maintainer
Release files for topology-connect 1.0.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 | |
|---|---|---|---|---|
| topology_connect-1.0.0.tar.gz | 10.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| topology_connect-1.0.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 24.8 kB
Release files / topology_connect-1.0.0.tar.gz
| Download URL | topology_connect-1.0.0.tar.gz |
|---|---|
| Size | 10.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
94a4426a1a719f72d0344c01191587eb1f8ef93083ea1d9117ff53be77e0b975
|
|
BLAKE2b-256 checksum How to use checksums |
1ebf6c6f02be03b0fd721e9e67692a2f46483f4da64c1741201d4c5796b6f598
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.13.0 pkginfo/1.5.0.1 requests/2.22.0 setuptools/41.6.0 requests-toolbelt/0.9.1 tqdm/4.32.2 CPython/3.6.9
|
Release files / topology_connect-1.0.0-py3-none-any.whl
| Download URL | topology_connect-1.0.0-py3-none-any.whl |
|---|---|
| Size | 14.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d053b4c1cac9b22d6581db260a531026dc8b067901ac524f421da84bc633176f
|
|
BLAKE2b-256 checksum How to use checksums |
919def6b999957f608bb4f81103d4d6e4d585a3b19f1591df269e228c0b04eab
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.13.0 pkginfo/1.5.0.1 requests/2.22.0 setuptools/41.6.0 requests-toolbelt/0.9.1 tqdm/4.32.2 CPython/3.6.9
|
Security for topology-connect 1.0.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.
