Table of Contents
- Overview
- Backward Compatibility
- Docker
- System Requirements
- Core Installation
- Generate YDK Components
- Notes
- Running Unit Tests
- Documentation and Support
- Release Notes
The YANG Development Kit (YDK) is a software development tool, which provides API for building applications based on YANG models. The YDK allows generate YANG model API and provides services to apply generated API over various communication protocols. Currently implemented protocols are: Netconf, Restconf, OpenDaylight and gNMI. YDK provides CRUD and protocol specific services over above protocols. YDK also provides codec services to translate API models to/from XML and JSON encoded strings.
The YDK is a multi-language software. Currently supported languages are Python, Go, and C++.
Other tools and libraries are used to deliver YDK functionality:
- YANG model analysis and code generation is implemented using APIs from the pyang library
- Documentation is generated using Sphinx
- Runtime YANG model analysis is done using libyang
- C++ to python bindings are created using pybind11
- C++ uses catch and spdlog for tests and logging respectively
The output of ydk-gen is either a core package, that defines main services and providers,
or add-on service package like gNMI Service, or a module bundle, consisting of programming language APIs derived from YANG models.
Each module bundle is generated using a bundle profile and the ydk-gen tool.
Developers can either use pre-packaged generated bundles (e.g. ydk-py),
or define their own bundle, consisting of a set of YANG models, using a bundle profile
(e.g. ietf_0_1_5.json).
This gives the developer an ability to customize scope of their bundle based on their requirements.
The YDK-0.8.6 core is backward compatible with all previously generated model bundles starting from release of YDK-0.7.3. However the YDK-0.8.6 generates different code and model API comparing to YDK-0.8.4. The YDK-0.8.6 generated code is not compatible with YDK-0.7.2 and earlier bundle packages due to changes in modeling and handling of YList objects.
NOTE. Starting from release 0.8.6 the YDK does not support Python2 interpreter as it was deprecated.
A docker image is automatically built with the latest ydk-gen commit. This docker can be used to run ydk-gen without installing anything natively on your platform.
To use the docker image, install docker on your system and run the below command. See the docker documentation for more details.
docker run -it ydksolutions/ydk-gen
The YDK is currently supported on the following platforms including native installations, virtual machines, and docker images:
- Linux Ubuntu Xenial (16.04 LTS), Bionic (18.04 LTS), and Focal (20.04 LTS)
- Linux CentOS/RHEL versions 7 and 8
- MacOS up to 11.6.2 (Big Sur)
On Windows 10 the Linux virtual machine can run using Windows Subsystem for Linux (WSL); check this for virtual machine installation procedure. The YDK has been tested in such environment on Ubuntu Bionic (18.04 LTS) and Focal (20.04 LTS) images obtained from Microsoft Store.
On supported platforms the YDK can be installed using installation script.
On other platforms the YDK should be installed manually from source.
For both the methods the user must install git package prior to the installation procedure.
All YDK core components are based on C and C++ code. These components compiled using default compilers for the supported platform.
Corresponding binaries, libraries, and header files are installed in default locations,
which are /usr/local/bin, /usr/local/lib, and /usr/local/include.
The user must have sudo access in order to install YDK core components to these locations.
For YDK installation it is recommended to use script install_ydk.sh from ydk-gen git repository.
The script detects platform OS, installs all the dependencies and builds complete set of YDK components for specified language.
The YDK extensively uses Python scripts for building its components and model API packages (bundles).
By default the YDK uses Python system installation.
In order to isolate YDK Python environment from system installation, the script can build Python3 virtual environment.
If built, the user must manually activate virtual environment when generating model bundles and/or running YDK based application.
By default the Python virtual environment is installed under $HOME/venv directory.
For different location the PYTHON_VENV environment variable should be set to that location.
Here is simple example of core YDK installation for Python programming language:
git clone https://github.com/ygorelik/ydk-gen.git
cd ydk-gen
export YDKGEN_HOME=`pwd` # optional
export PYTHON_VENV=$HOME/ydk_vne # optional
./install_ydk.sh --core
The script also allows to install individual components like dependencies, core, and service packages for specified programming language or for all supported languages. Full set of script capabilities could be viewed like this:
./install_ydk.sh --help
usage: install_ydk [ {--cpp|--py|--go|--all} ] [-c] [-s gnmi] [-h] [-n] [-v]
Options and arguments:
--cpp install YDK for C++ programming language
--go install YDK for Go programming language
--py|--python install YDK for Python programming language (default)
--all install YDK for all supported programming languages
-v|--venv create python virtual environment
-c|--core install YDK core packages
-s|--service gnmi install gNMI service package
-n|--no-deps skip installation of dependencies
-h|--help print this help message and exit
Environment variables:
YDKGEN_HOME specifies location of ydk-gen git repository;
if not set, $HOME/ydk-gen is assumed
PYTHON_VENV specifies location of python virtual environment;
if not set, /home/ygorelik/venv is assumed
GOROOT specifies installation directory of go software;
if not set, /usr/local/go is assumed
GOPATH specifies location of go source directory;
if not set, $HOME/go is assumed
C_INCLUDE_PATH location of C include files;
if not set, /usr/local/include is assumed
CPLUS_INCLUDE_PATH location of C++ include files;
if not set, /usr/local/include is assumed
CMAKE_LIBRARY_PATH Location of Python shared libraries;
if not set, default system library location is assumed
If user environment is different from the default one (different Python installation or different location of libraries) then building from source method should be used.
In some OS configurations during YDK package installation the cmake fails to find C/C++ headers for previously installed YDK libraries. In this case the header files location must be specified explicitly (in below commands the default location is shown):
export C_INCLUDE_PATH=/usr/local/include
export CPLUS_INCLUDE_PATH=/usr/local/include
When non-standard Python installation is used or there are multiple installations of Python on the platform, the PATH and CMAKE_LIBRARY_PATH environment variables must be set accordingly in order for the installation scripts to pick up correct Python binaries and shared libraries.
If user platform is supported one, it is recommended to use ydk-gen/install_ydk.sh script.
The script will also install Python virtual environment in default or specified location, when '--venv' is specified.
# Clone ydk-gen from GitHub
git clone https://github.com/ygorelik/ydk-gen.git
cd ydk-gen
# Define optional environment variables and install dependencies
export YDKGEN_HOME=`pwd`
export PYTHON_VENV=$HOME/ydk_venv
./install_ydk.sh -v # also builds Python virtual environment
For unsupported platforms it is recommended to follow logic of ydk-gen/test/dependencies-* scripts.
# If created, activate Python virtual environment
source $PYTHON_VENV/bin/activate
# Generate and install YDK core library
./generate.py -is --core --cpp
# For Python programming language add
./generate.py -i --core --py
# For Go programming language add
./generate.py -i --core --go
In order to enable YDK support for gNMI protocol, which is optional, the user need install third party software and YDK gNMI service package.
Here is simple example how gNMI service package for Python could be added:
cd ydk-gen
./install_ydk.sh --py --service gnmi -v
There is an open issue with gRPC on Centos/RHEL, which requires an extra step before running any YDK gNMI application.
See this issue on GRPC GitHub for details.
As a workaround, the YDK based application runtime environment must include setting of LD_LIBRARY_PATH variable:
PROTO=$HOME # Default location defined during installation
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$PROTO/grpc/libs/opt:$PROTO/protobuf-3.5.0/src/.libs:/usr/local/lib:/usr/local/lib64
All the YDK components/packages can be generated by using Python script generate.py. To get all of its options run:
cd ydk-gen
./generate.py --help
usage: generate.py [-h] [-l] [--core] [--service SERVICE] [--bundle BUNDLE]
[--adhoc-bundle-name ADHOC_BUNDLE_NAME]
[--adhoc-bundle ADHOC_BUNDLE [ADHOC_BUNDLE ...]]
[--generate-meta] [--generate-doc] [--generate-tests]
[--output-directory OUTPUT_DIRECTORY] [--cached-output-dir]
[-p] [-c] [-g] [-v] [-o]
Generate YDK artifacts:
optional arguments:
-h, --help show this help message and exit
-l, --libydk Generate libydk core package
--core Generate and/or install core library
--service SERVICE Location of service profile JSON file
--bundle BUNDLE Location of bundle profile JSON file
--adhoc-bundle-name ADHOC_BUNDLE_NAME
Name of the adhoc bundle
--adhoc-bundle ADHOC_BUNDLE [ADHOC_BUNDLE ...]
Generate an SDK from a specified list of files
--generate-meta Generate meta-data for Python bundle
--generate-doc Generate documentation
--generate-tests Generate tests
--output-directory OUTPUT_DIRECTORY
The output directory where the sdk will get created.
--cached-output-dir The output directory specified with --output-directory
includes a cache of previously generated gen-
api/<language> files under a directory called 'cache'.
To be used to generate docs for --core
-p, --python Generate Python SDK
-c, --cpp Generate C++ SDK
-g, --go Generate Go SDK
-v, --verbose Verbose mode
-o, --one-class-per-module
Generate separate modules for each python class
corresponding to YANG containers or lists.
The below steps specify how to use generate.py to generate YDK core, model bundle, and service packages.
In all the examples the script is executed from ydk-gen directory.
It is assumed that Python virtual environment is activated.
All the packages are available for Python, Go and C++ in corresponding github repositories:
ydk-py, ydk-go
and ydk-cpp.
The script create_ydk_sdk_for_github.sh can be used to generate the ydk-py,
ydk-cpp and ydk-go repositories after having generated all the bundles and core packages using generate.py.
The first step in using ydk-gen is either using one of the already built bundle profiles or constructing your own bundle profile, consisting of the YANG models you are interested to include into the bundle:
Construct a bundle profile file, such as ietf_0_1_5.json
and specify its dependencies.
A sample bundle profile file is described below. The file is in a JSON format. The profile must define the "name",
"version" and "description" of the bundle, and then the "core_version", which refers to
the version of the ydk core package that you want to use with this bundle.
The "name" of the bundle will form part of the installation path of the bundle.
All other attributes, like "author" and "copyright", are optional and will not affect the bundle generation.
{
"name":"cisco-ios-xr",
"version": "6.5.3",
"core_version": "0.8.6",
"author": "Cisco",
"copyright": "Cisco",
"description": "Cisco IOS-XR Native Models From Git",
The "models" section of the profile describes sources of YANG models. It could contain combination of elements:
"dir"- list of relative directory paths containing YANG files"file"- list of relative YANG file paths"git"- git repository, where YANG files are located
The sample below shows the use of git sources only. Other examples can be found in profiles directory README.md.
Each "git" source must specify "url" - git repository URL, and "commits" list. The specified URL must allow the repository
to be cloned without user intervention. Each element in "commits" list can specify:
"commitid"- optional specification of a commit ID in string format. If not specified the HEAD revision is assumed. The further specified directories and files will be copied from the context of this commit."dir"- optional list of relative directory paths within the git repository. All*.yangfiles in specified directory and any sub-directories will be pulled into the generated bundle."file"- optional list of relative*.yangfile paths within the git repository.
Only directory examples are shown in this example.
"models": {
"git": [
{
"url": "https://github.com/YangModels/yang.git",
"commits": [
{
"dir": [
"vendor/cisco/xr/653"
]
}
]
},
{
"url": "https://github.com/YangModels/yang.git",
"commits": [
{
"commitid": "f6b4e2d59d4eedf31ae8b2fa3119468e4c38259c",
"dir": [
"experimental/openconfig/bgp",
"experimental/openconfig/policy"
]
}
]
}
]
},
Generate model bundle using a bundle profile and install it.
Python virtual environment must be activated prior to these procedures
./generate.py --python --bundle profiles/bundles/<name-of-profile>.json -i
Check Python packages installed:
pip list | grep ydk
ydk (0.8.6)
ydk-models-<name-of-bundle> (0.5.1)
...
export $GOPATH=/your-go-path-installation-directory # default location is ~/go
./generate.py --go --bundle profiles/bundles/<name-of-profile>.json -i
./generate.py --cpp --bundle profiles/bundles/<name-of-profile>.json -is
Now, you can start creating apps based on the models in your bundle.
Assuming you have generated a python bundle, the models will be available for importing in your app under
ydk.models.<name-of-your-bundle>.
For examples, see ydk-py-samples and
C++ samples.
Also refer to the documentation for python,
Go and
C++.
In order to generate YDK core and bundles documentation, the --generate-doc option of generate.py script is used,
while generating core package. Therefore the user should generate all the bundles without the --generate-doc
option prior to the documentation generation.
For example, the below sequence of commands will generate the documentation for the three python bundles and the python core
(for C++, use --cpp; for Go, use --go).
./generate.py --python --bundle profiles/bundles/ietf_0_1_1.json
./generate.py --python --bundle profiles/bundles/openconfig_0_1_1.json
./generate.py --python --bundle profiles/bundles/cisco_ios_xr_6_1_1.json
./generate.py --python --core --generate-doc
Note. The documentation generation for bundles can take few hours due to their size. If you have previously
generated documentation using the --cached-output-dir --output-directory <dir> option,
the add-on documentation generation time can be reduced. Adding cisco-ios-xr documentation as an example:
mkdir gen-api/cache
mv gen-api/python gen-api/cache
./generate.py --python --bundle profiles/bundles/cisco_ios_xr_6_6_3.json
./generate.py --python --core --generate-doc --output-directory gen-api --cached-output-dir
When YANG models available on the hard drive, there is capability to generate small model bundles, which include just few models. It is called an "adhoc" bundle. Such a bundle generated without profile directly from command line. Here is simple example:
./generate.py -i --adhoc-bundle-name test --adhoc-bundle \
/opt/git-repos/clean-yang/vendor/cisco/xr/621/Cisco-IOS-XR-ipv4-bgp-oper*.yang \
/opt/git-repos/clean-yang/vendor/cisco/xr/621/Cisco-IOS-XR-types.yang
/opt/git-repos/clean-yang/vendor/cisco/xr/621/Cisco-IOS-XR-ipv4-bgp-datatypes.yang
This will generate a bundle that contains files specified in the --adhoc-bundle option and
create Python package ydk-models-test-0.1.0.tar.gz, which has dependency on the base IETF bundle.
Note that all dependencies for the bundle must be listed. It is expected that this option will be typically used
for generating point model bundles for specific testing. The --verbose option is automatically enabled to quickly
and easily let the user see if dependencies have been satisfied.
Starting from release 0.8.5 YDK supports only Python3 version. At least Python 3.5 along with corresponding pip3 utility must be installed on your system. It is also required for Python installation to include corresponding shared library. As example:
- python3.6m - /usr/lib/x86_64-linux-gnu/libpython3.6m.so
It is recommended to follow Core Installation procedure to ensure presence of shared Python libraries.
NOTE. Due to GitHub issue #1050 YDK is not supported with Python 3.9.x.
In some OS configurations during YDK package installation the cmake fails to find C/C++ headers for installed YDK libraries.
In this case the header location must be specified explicitly:
export C_INCLUDE_PATH=/usr/local/include
export CPLUS_INCLUDE_PATH=/usr/local/include
gen-api - generated code and packages for core and bundles
- python (Python SDK)
- go (Go SDK)
- cpp (C++ SDK)
3d_party - suplemental code for third party software
profiles - profile files used during generation
sdk - sdk core and stubs for python, go and cpp
test - dependencies and unit test shell scripts
yang - some YANG models used for testing
ydkgen - python code to extend generate.py script
create_ydk_sdk_for_github.sh - convenience script to generate language specific repositories
generate_bundles.sh - convinience script to generate core and bundle packages for deployment
generate.py - script used to generate SDK for YANG models
install_ydk.sh - YDK core components installation script
requirements.txt- python dependencies used during installation
README.md - installation and usage notes
Sometimes, developers using ydk-gen may run across errors when generating a YDK bundle using generate.py with some yang models.
If there are issues with the profile file being used, such JSON formatting errors will be evident.
Other times, when the problem is not so evident, it is recommended to try running the script with the
[--verbose|-v] flag, which may reveal syntax problems with the YANG models being used. For example:
./generate.py --python --bundle profiles/bundles/ietf_0_1_1.json --verbose
Also, it may be a good idea to obtain a local copy of the YANG models and compile them using pyang to ensure
the validity of the models and completeness of the model package:
cd /path/to/yang/models
pyang *.yang
After installing C++ core packages and activating Python virtual environment:
-
Install bundle package
cd ydk-gen ./generate.py -i --core ./generate.py -i --bundle profiles/test/ydktest-cpp.json -
Start confd
source $HOME/confd/confdrc cd ydk-gen/sdk/cpp/core/tests/confd/ydktest make all make start -
Run unit tests
cd ydk-gen/sdk/python python test/test_sanity_types.py python test/test_sanity_levels.py python test/test_sanity_filters.py
-
Install the core and bundle packages
cd ydk-gen ./generate.py -is --core --cpp ./generate.py -is --bundle profiles/test/ydktest-cpp.json --cpp -
Run the core unit tests
cd ydk-gen/gen-api/cpp/ydk/build ./test/ydk_core_test -
Start confd
source $HOME/confd/confdrc cd ydk-gen/sdk/cpp/core/tests/confd/ydktest make all make start -
Build and run bundle unit tests
cd ydk-gen/sdk/cpp/tests mkdir -p build && cd build cmake .. && make ./ydk_bundle_test
Please refer here.
- Read the online YDK documentation (release 0.8.3) for details on how to use the YDK and API for specific models
- Check GitHub Pages for the latest YDK release documentation
- Find hundreds of sample apps in the ydk-py-samples repository
- Join the YDK community to connect with YDK users and developers
The current YDK release version is 0.8.6.
YDK-Gen is licensed under the Apache 2.0 License.