napalm-srlinux 2.0.0__tar.gz

napalm_srlinux-2.0.0/AUTHORS

@@ -0,0 +1,7 @@
+Jonathon Lundstrom <jonathon.lundstrom@nokia.com>
+Mohammad Zamman <mohammad.f.zamman@nokia.com>
+Jose Valente <jose.valente@nokia.com>
+Syed Shekupillai <syed.shekupillai@nokia.com>
+Ashna Shah <ashna.shah@nokia.com>
+Wim Henderickx <wim.henderickx@nokia.com>
+Jeroen van Bemmel <jeroen.van_bemmel@nokia.com>

napalm_srlinux-2.0.0/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "{}"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright {yyyy} {name of copyright owner}
+
+   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.

napalm_srlinux-2.0.0/PKG-INFO

@@ -0,0 +1,153 @@
+Metadata-Version: 2.4
+Name: napalm-srlinux
+Version: 2.0.0
+Summary: NAPALM driver for Nokia SR Linux (JSON-RPC)
+Author-email: Jose Valente <jose.valente@nokia.com>, Jeroen van Bemmel <jeroen.van_bemmel@nokia.com>
+License: Apache-2.0
+Project-URL: Homepage, https://github.com/napalm-automation-community/napalm-srlinux
+Project-URL: Bug Tracker, https://github.com/napalm-automation-community/napalm-srlinux/issues
+Classifier: Topic :: System :: Networking
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Natural Language :: English
+Classifier: Operating System :: POSIX :: Linux
+Classifier: Operating System :: MacOS
+Requires-Python: >=3.10
+Description-Content-Type: text/markdown
+License-File: LICENSE
+License-File: AUTHORS
+Requires-Dist: napalm<6,>=5.0.0
+Requires-Dist: httpx>=0.27.0
+Dynamic: license-file
+
+# napalm-srlinux
+
+Community [NAPALM](https://napalm.readthedocs.io) driver for the [Nokia SR Linux](https://learn.srlinux.dev) network OS, built on the **JSON-RPC** management interface; the only runtime dependencies are `napalm` and `httpx`.
+
+**Documentation: https://napalm-automation-community.github.io/napalm-srlinux/**
+
+## Installation
+
+```bash
+pip install napalm-srlinux
+```
+
+Requires Python ≥ 3.10 and napalm ≥ 5.
+
+On the SR Linux node the JSON-RPC server must be enabled (it is by default in [containerlab](https://containerlab.dev) labs):
+
+```
+set / system json-rpc-server admin-state enable
+set / system json-rpc-server network-instance mgmt http admin-state enable
+set / system json-rpc-server network-instance mgmt https admin-state enable
+set / system json-rpc-server network-instance mgmt https tls-profile <profile>
+```
+
+## Quick start
+
+```python
+from napalm import get_network_driver
+
+driver = get_network_driver("srlinux")
+optional_args = {
+    # pick one of the TLS modes below:
+    "insecure": True,        # plain http on port 80 — labs only
+    # "skip_verify": True,   # https, certificate not verified
+    # "tls_ca": "ca.pem",    # https, verified against this CA
+}
+with driver("192.0.2.1", "admin", "NokiaSrl1!", optional_args=optional_args) as device:
+    print(device.get_facts())
+```
+
+A runnable example against a containerlab node is in [examples/example.py](examples/example.py).
+
+## Optional arguments
+
+| argument | default | description |
+|---|---|---|
+| `jsonrpc_port` | `443` (or `80` with `insecure`) | TCP port of the JSON-RPC server |
+| `insecure` | `False` | use plain http instead of https |
+| `skip_verify` | `False` | https without certificate verification |
+| `tls_ca` | `""` | CA bundle used to verify the server certificate |
+| `tls_cert_path` / `tls_key_path` | `""` | client certificate and key (both required for mTLS) |
+| `tls_key_password` | `""` | passphrase of the client key |
+| `running_format` | `"json"` | `get_config()` running-config format: `json` or `cli` (`info flat`) |
+| `commit_save` | `False` | when set, commits use `commit save` / `save startup` so the config persists |
+
+## Supported methods
+
+All standard NAPALM getters that have an SR Linux equivalent are implemented:
+`get_facts`, `get_interfaces`, `get_interfaces_counters`*, `get_interfaces_ip`*, `get_arp_table`, `get_ipv6_neighbors_table`, `get_bgp_neighbors`, `get_bgp_neighbors_detail`, `get_bgp_config`, `get_environment`, `get_lldp_neighbors`, `get_lldp_neighbors_detail`, `get_network_instances`, `get_users`, `get_snmp_information`, `get_config`, `get_ntp_servers`, `get_ntp_stats`, `get_optics`, `get_mac_address_table`, `get_route_to`, `get_vlans`**, `is_alive`, `ping`, `traceroute`, `cli` (`text` and `json` encodings), plus the full candidate-config workflow (`load_merge_candidate`, `load_replace_candidate`, `compare_config`, `commit_config` — including commit-confirm via `revert_in` —, `confirm_commit`, `has_pending_commit`, `discard_config`, `rollback`).
+
+\* keyed by subinterface name (e.g. `ethernet-1/1.0`), since IP/counter state lives on subinterfaces in SR Linux.
+
+\** SR Linux has no global VLAN table; `get_vlans` reports the single-tagged encapsulations of bridged subinterfaces attached to mac-vrf network instances, named after the mac-vrf. Untagged subinterfaces and `vlan-id any` are not reported.
+
+Not supported by SR Linux (raise `NotImplementedError`): `get_probes_config/results`, `get_firewall_policies`, `get_ntp_peers`, `get_route_to(longer=True)`.
+
+### Candidate-config semantics
+
+The JSON-RPC interface has no persistent candidate datastore across requests — a `set` request against the candidate datastore is transactional and commits on success. The NAPALM candidate workflow is therefore emulated client-side:
+
+- `load_merge_candidate()` / `load_replace_candidate()` store the intended change **in the driver** and (for JSON configs) validate it on the device via the `validate` method. Accepted formats: native SR Linux JSON, a gNMI-style envelope (`updates`/`replaces`/`deletes`), or SR Linux CLI commands.
+- `compare_config()` uses the JSON-RPC `diff` method (JSON configs) or a throwaway named candidate on the device (CLI configs).
+- `commit_config()` first creates a named checkpoint (`NAPALM-<session>-<n>`, unique per driver instance) as the rollback anchor, then applies everything in one transactional request.
+- `discard_config()` only clears the client-side state; it never touches the device.
+- `rollback()` restores the checkpoint created by the last `commit_config()`. Checkpoints contain the **entire** configuration tree — any change made after the checkpoint is reverted too.
+- `get_config(retrieve="candidate")` returns `""` — the candidate only exists client-side.
+
+#### Commit confirm
+
+`commit_config(revert_in=<seconds>)` starts a confirmed commit: the change is applied, but the device reverts it automatically unless it is confirmed in time (JSON configs use the JSON-RPC `confirm-timeout` parameter, available since SR Linux 23.3.2; CLI configs use `commit confirmed timeout <seconds>`).
+
+- `has_pending_commit()` reports whether a confirmed commit is awaiting confirmation — device-side state, visible to every session.
+- `confirm_commit()` accepts the pending commit and cancels the revert timer. With `commit_save`, the `save startup` is deferred until this point, so the startup config never holds a change that may still auto-revert.
+- `rollback()` called while a confirm is pending rejects it immediately (`confirmed-reject`) instead of loading a checkpoint.
+- `commit_config()` refuses to run while another confirmed commit is pending.
+
+Because the candidate is client-side, no lock is held on the device; concurrent clients are not blocked (and not protected) against each other.
+
+## Migrating from 1.x
+
+- The driver name changed: `get_network_driver("srlinux")` instead of `"srl"`; the package is `napalm_srlinux` (was `napalm_srl`).
+- gNMI is gone — the optional arguments `gnmi_port`, `target_name`, `encoding`, `tls_cert`, and `tls_key` no longer exist. Client certificates are configured with `tls_cert_path`/`tls_key_path`.
+- `get_interfaces()` speeds are now correctly reported in Mbit/s (e.g. `1G` → `1000.0`).
+- `get_users()` returns the standard `sshkeys` key (was `ssh-keys`).
+- BGP/interface uptimes are no longer truncated to less than a day.
+
+## Development
+
+The project is managed with [uv](https://docs.astral.sh/uv/):
+
+```bash
+uv sync                  # create the venv and install all dependencies
+uv run pytest test/unit  # unit tests (mocked JSON-RPC fixtures)
+uv run ruff check napalm_srlinux test tools examples
+```
+
+### Testing against a real node
+
+```bash
+make deploy-clab-ci      # single-node containerlab topology
+make run-tests           # runs all test/ci scripts against it
+make destroy-clab-ci
+```
+
+### Re-recording the unit-test fixtures
+
+The mocked-data fixtures under `test/unit/mocked_data/` are verbatim JSON-RPC responses recorded from a real two-node lab (BGP, LLDP, ARP, mac-vrf, NTP, ...):
+
+```bash
+make deploy-clab-record  # two-node recording topology
+make record-fixtures     # configure the lab + record all fixtures
+make destroy-clab-record
+```
+
+Review the resulting `git diff` before committing re-recorded fixtures.
+
+## License
+
+Apache 2.0 — see [LICENSE](LICENSE).

napalm_srlinux-2.0.0/README.md

@@ -0,0 +1,128 @@
+# napalm-srlinux
+
+Community [NAPALM](https://napalm.readthedocs.io) driver for the [Nokia SR Linux](https://learn.srlinux.dev) network OS, built on the **JSON-RPC** management interface; the only runtime dependencies are `napalm` and `httpx`.
+
+**Documentation: https://napalm-automation-community.github.io/napalm-srlinux/**
+
+## Installation
+
+```bash
+pip install napalm-srlinux
+```
+
+Requires Python ≥ 3.10 and napalm ≥ 5.
+
+On the SR Linux node the JSON-RPC server must be enabled (it is by default in [containerlab](https://containerlab.dev) labs):
+
+```
+set / system json-rpc-server admin-state enable
+set / system json-rpc-server network-instance mgmt http admin-state enable
+set / system json-rpc-server network-instance mgmt https admin-state enable
+set / system json-rpc-server network-instance mgmt https tls-profile <profile>
+```
+
+## Quick start
+
+```python
+from napalm import get_network_driver
+
+driver = get_network_driver("srlinux")
+optional_args = {
+    # pick one of the TLS modes below:
+    "insecure": True,        # plain http on port 80 — labs only
+    # "skip_verify": True,   # https, certificate not verified
+    # "tls_ca": "ca.pem",    # https, verified against this CA
+}
+with driver("192.0.2.1", "admin", "NokiaSrl1!", optional_args=optional_args) as device:
+    print(device.get_facts())
+```
+
+A runnable example against a containerlab node is in [examples/example.py](examples/example.py).
+
+## Optional arguments
+
+| argument | default | description |
+|---|---|---|
+| `jsonrpc_port` | `443` (or `80` with `insecure`) | TCP port of the JSON-RPC server |
+| `insecure` | `False` | use plain http instead of https |
+| `skip_verify` | `False` | https without certificate verification |
+| `tls_ca` | `""` | CA bundle used to verify the server certificate |
+| `tls_cert_path` / `tls_key_path` | `""` | client certificate and key (both required for mTLS) |
+| `tls_key_password` | `""` | passphrase of the client key |
+| `running_format` | `"json"` | `get_config()` running-config format: `json` or `cli` (`info flat`) |
+| `commit_save` | `False` | when set, commits use `commit save` / `save startup` so the config persists |
+
+## Supported methods
+
+All standard NAPALM getters that have an SR Linux equivalent are implemented:
+`get_facts`, `get_interfaces`, `get_interfaces_counters`*, `get_interfaces_ip`*, `get_arp_table`, `get_ipv6_neighbors_table`, `get_bgp_neighbors`, `get_bgp_neighbors_detail`, `get_bgp_config`, `get_environment`, `get_lldp_neighbors`, `get_lldp_neighbors_detail`, `get_network_instances`, `get_users`, `get_snmp_information`, `get_config`, `get_ntp_servers`, `get_ntp_stats`, `get_optics`, `get_mac_address_table`, `get_route_to`, `get_vlans`**, `is_alive`, `ping`, `traceroute`, `cli` (`text` and `json` encodings), plus the full candidate-config workflow (`load_merge_candidate`, `load_replace_candidate`, `compare_config`, `commit_config` — including commit-confirm via `revert_in` —, `confirm_commit`, `has_pending_commit`, `discard_config`, `rollback`).
+
+\* keyed by subinterface name (e.g. `ethernet-1/1.0`), since IP/counter state lives on subinterfaces in SR Linux.
+
+\** SR Linux has no global VLAN table; `get_vlans` reports the single-tagged encapsulations of bridged subinterfaces attached to mac-vrf network instances, named after the mac-vrf. Untagged subinterfaces and `vlan-id any` are not reported.
+
+Not supported by SR Linux (raise `NotImplementedError`): `get_probes_config/results`, `get_firewall_policies`, `get_ntp_peers`, `get_route_to(longer=True)`.
+
+### Candidate-config semantics
+
+The JSON-RPC interface has no persistent candidate datastore across requests — a `set` request against the candidate datastore is transactional and commits on success. The NAPALM candidate workflow is therefore emulated client-side:
+
+- `load_merge_candidate()` / `load_replace_candidate()` store the intended change **in the driver** and (for JSON configs) validate it on the device via the `validate` method. Accepted formats: native SR Linux JSON, a gNMI-style envelope (`updates`/`replaces`/`deletes`), or SR Linux CLI commands.
+- `compare_config()` uses the JSON-RPC `diff` method (JSON configs) or a throwaway named candidate on the device (CLI configs).
+- `commit_config()` first creates a named checkpoint (`NAPALM-<session>-<n>`, unique per driver instance) as the rollback anchor, then applies everything in one transactional request.
+- `discard_config()` only clears the client-side state; it never touches the device.
+- `rollback()` restores the checkpoint created by the last `commit_config()`. Checkpoints contain the **entire** configuration tree — any change made after the checkpoint is reverted too.
+- `get_config(retrieve="candidate")` returns `""` — the candidate only exists client-side.
+
+#### Commit confirm
+
+`commit_config(revert_in=<seconds>)` starts a confirmed commit: the change is applied, but the device reverts it automatically unless it is confirmed in time (JSON configs use the JSON-RPC `confirm-timeout` parameter, available since SR Linux 23.3.2; CLI configs use `commit confirmed timeout <seconds>`).
+
+- `has_pending_commit()` reports whether a confirmed commit is awaiting confirmation — device-side state, visible to every session.
+- `confirm_commit()` accepts the pending commit and cancels the revert timer. With `commit_save`, the `save startup` is deferred until this point, so the startup config never holds a change that may still auto-revert.
+- `rollback()` called while a confirm is pending rejects it immediately (`confirmed-reject`) instead of loading a checkpoint.
+- `commit_config()` refuses to run while another confirmed commit is pending.
+
+Because the candidate is client-side, no lock is held on the device; concurrent clients are not blocked (and not protected) against each other.
+
+## Migrating from 1.x
+
+- The driver name changed: `get_network_driver("srlinux")` instead of `"srl"`; the package is `napalm_srlinux` (was `napalm_srl`).
+- gNMI is gone — the optional arguments `gnmi_port`, `target_name`, `encoding`, `tls_cert`, and `tls_key` no longer exist. Client certificates are configured with `tls_cert_path`/`tls_key_path`.
+- `get_interfaces()` speeds are now correctly reported in Mbit/s (e.g. `1G` → `1000.0`).
+- `get_users()` returns the standard `sshkeys` key (was `ssh-keys`).
+- BGP/interface uptimes are no longer truncated to less than a day.
+
+## Development
+
+The project is managed with [uv](https://docs.astral.sh/uv/):
+
+```bash
+uv sync                  # create the venv and install all dependencies
+uv run pytest test/unit  # unit tests (mocked JSON-RPC fixtures)
+uv run ruff check napalm_srlinux test tools examples
+```
+
+### Testing against a real node
+
+```bash
+make deploy-clab-ci      # single-node containerlab topology
+make run-tests           # runs all test/ci scripts against it
+make destroy-clab-ci
+```
+
+### Re-recording the unit-test fixtures
+
+The mocked-data fixtures under `test/unit/mocked_data/` are verbatim JSON-RPC responses recorded from a real two-node lab (BGP, LLDP, ARP, mac-vrf, NTP, ...):
+
+```bash
+make deploy-clab-record  # two-node recording topology
+make record-fixtures     # configure the lab + record all fixtures
+make destroy-clab-record
+```
+
+Review the resulting `git diff` before committing re-recorded fixtures.
+
+## License
+
+Apache 2.0 — see [LICENSE](LICENSE).

napalm_srlinux-2.0.0/napalm_srlinux/__init__.py

@@ -0,0 +1,19 @@
+# Copyright 2024 Nokia. All rights reserved.
+#
+# The contents of this file are 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.
+
+"""napalm-srlinux package."""
+
+from napalm_srlinux.srlinux import NokiaSRLinuxDriver
+
+__all__ = ("NokiaSRLinuxDriver",)