Users of OpenYuma and yuma123 can easily switch to YumaPro without rewriting SIL code

YumaPro SDK was forked from Yuma, commonly called OpenYuma, in 2011. Since then YumaWorks has vastly increased the reliability, robustness, and performance of YumaPro SDK. We’ve also added an abundance of new features, all while implementing standards compliance. By contrast, Yuma remains largely untouched and lacks professional support.

Upgrading to YumaPro from OpenYuma / yuma123 FAQ

Q: Is it possible to upgrade to YumaPro SDK from Yuma123 or OpenYuma?

A: Yes.  The YumaPro server APIs are a super-set of the original Yuma APIs.

All the "first generation" APIs for SIL code are fully supported.

These include RPC, edit, get, and notification callback functions.

Q: Do I have to rewrite my SIL code for YumaPro?

A: No. The original APIs called "EDIT1" and "GET1" are still 100% supported

You should be able to simply recompile your current code using new makefiles.

Q: Can I use the new "2nd generation" APIs for my YANG modules?

A: Yes. The EDIT2 and GET2 APIs can be applied to new modules

and to new sub-trees within the an old module.

Q: How the yumapro improve the performance compared with the Yuma

for get/edit-config the configuration for large data-sets?

A: The edit validation processing code has been completely rewritten

so that the server can restrict the validation tests to only the affected nodes.

This allows huge time-savings when a small amount of data is changed in

a large configuration (the usual use-case). The XPath code and internal data

structures have been rewritten for high performance with large data-sets.

Q: Is there any way to persist the configuration datastore besides using 

startup-cfg.xml? Can I use my own database instead?

A: Yes, there are several ways to integrate your own persistent

database for the server configuration. The --startup XML file can be

used standalone, together with your database, or it can be replaced

completely by your database.

Q: Is there a way to hook my system into the initialization

and cleanup process without hacking the source code?

A: The new "yp-system" library and APIs allow full integration

to all server initialization and cleanup phases.

Q: Will I need to change my netconfd-pro.conf to all new parameters?

A: No. All original CLI parameters and conf file format are still supported.

There are over 140 new CLI parameters added, but the defaults should

provide stable server behavior. You need to "opt-in" to new features,

but this focus on backward compatibility allows for easy integration

of new YumaPro updates.