Note: If your intension is to just start using ORCA, you need not to get into ORCA Network Library details, instead consider installing ORCA Backend and ORCA UI directly.
ORCA Network Library is an open source python package to facilitate CRUD operations on SONiC devices using gNMI interface. orca_nw_lib maintains a graph database with the realtime device configurations and network topology. ORCA Network Library can be used to develop the orchestration solutions, NMS applications, network data analytics. ORCA Backend and ORCA UI are the application developed using APIs and Neo4j DB of ORCA Network Library.
- ORCA Network Library
Latest release of ORCA Network Library can be simply installed using pip as follows :
pip install orca_nw_lib
After installing the orca_nw_lib package, orca_nw_lib can be used like any other python package in your application. But before using orca_nw_lib, it is required to install Neo4j and do some basic configurations.
orca_nw_lib uses neo4j to store the network topology. To install neo4j easiest is to run Neo4j Docker image in container with the following command :
docker run \
--name testneo4j \
-p7474:7474 -p7687:7687 \
-d \
-v $HOME/neo4j/data:/data \
-v $HOME/neo4j/logs:/logs \
-v $HOME/neo4j/import:/var/lib/neo4j/import \
-v $HOME/neo4j/plugins:/plugins \
--env NEO4J_AUTH=neo4j/password \
neo4j:latest
Then open https://localhost:7474 with credentials neo4j/password to browse the database.
There are Following 2 configuration files for orca_nw_lib-
File contains all required parameters required to perform device and Neo4j DB operations. Also all the config properties defined in the file can be overridden by setting the environment variables with same name.
In majority of the cases only setting "discover_networks" property is enough i.e.export discover_networks="10.10.229.50"
File contains the standard logging configuration for ORCA Network Library.
By default above config files from the codebase are used, which is enough for most of the cases. Optionally user can use custom config files by setting the config files path in the environment variables ORCA_NW_LIB_CONFIG_FILE and ORCA_NW_LIB_LOGGING_CONFIG_FILE.
Optionally if user want to build and install orca_nw_lib from source, ORCA Network Library uses poetry to build the orca_nw_lib package. As a pre-requisite poetry must be installed in this case. Poetry can be easily installed using the following command :
pip install poetry
To build and install orca_nw_lib use the following commands :
git clone https://github.com/STORDIS/orca_nw_lib.git
cd orca_nw_lib
poetry build
pip install dist/orca_nw_lib-****.whl
Once installed the orca_nw_lib package, orca_nw_lib can be used like any other python package in your application.
For normal usage following APIs in python modules in the package orca_nw_lib are useful -
utils.py - load_orca_config() function must be called before using any APIs of orca_nw_lib.
discovery.py - discover_all() function can be used to discover complete topology as per the network defined in orca.yml
bgp.py - BGP CRUD operations
device.py - Get device system info.
interface.py - Interfaces CRUD operations.
lldp.py - Read LLDP relation, useful while doing discovery.
mclag.py - MCLAG CRUD operations.
port_chnl.py - Port Channel CRUD operations.
portgroup.py - Read port group information.
vlan.py - VLAN CRUD operations.
There are modules having suffixes _db and _gnmi, they contain operations to be performed in db or on device using gNMI respectively.
e.g. interface.py have general operation on interfaces and users can achieve normal interface configurations by using functions present in interface.py, on the other hand interface_db.py has function to perform CRUD operations in graph DB and interface_gnmi.py has function to configure interfaces on device.
Test cases are a good starting point to know the usage of APIs in orca_nbw_lib.
Exception objects raised by APIs in the modules above can be caught to know the API status. Exception object has all necessary details about the error.
Any configuration done on the device via orca_nw_lib APIs automatically keeps the DB in sync with the realtime network state by triggering the discovery method for the network component although gNMI subscriptions would have been the best way to achieve this, but due lack of support for gNMI subscription for all openconfig models in SONiC currently only pull mechanism can be used to keep graph DB in sync with realtime network state.
NOTE : For changes done on the device out side of orca_nw_lib i.e. changes done directly on the device, Best way to keep graph DB in sync with realtime network state is to trigger full discovery at a pre-defined interval.
Tests are not only used for regular software testing but are a good example to know the usage of APIs in orca_nw_lib. When starting to use orca_nw_lib referring to tests can be a good starting point. Test cases are located under test directory. To execute tests a topology of 3 switches (1-spine, 2-leaves) is required. Prior to execute tests, leaves should be connected to spine and respective interfaces should be enabled, so that by providing one of the switch IP in orca.yml whole topology gets discovered.
For performing tests creating a topology in GNS3 can be a good starting point.
-
To execute tests
pytest orca_nw_lib/test/test_network.py -
To execute single test cases
pytest orca_nw_lib/test/test_network.py -k test_remove_port_chnl_members -
To print console messages from code
pytest orca_nw_lib/test/test_interface.py -k test_remove_port_chnl_members -s
orca_nw_lib releases are hosted at PyPI- https://pypi.org/project/orca_nw_lib/#history , To create a new release, increase the release number in pyproject.toml.
- Broadcom Enterprise SONiC (Latest tested on >=4.0.5)
You can contribute to the project by opening an issue or sending a pull request.