Migrate to Apache Pekko
Description
blocks
Activity
Ivan Hraško August 1, 2024 at 11:07 AMEdited
We need migration guide:
installed ODL with akka
update to ODL with pekko
The migration from ODL using akka to OLD using pekko should mean just updating the configuration. See https://pekko.apache.org/docs/pekko/current/project/migration-guides.html.
the data persisted with previous version are compatible to new version without problems since pekko 1.0.3
since we have bumped to pekko 1.0.3 we can run akka and pekko clusters together
See also:
https://cwiki.apache.org/confluence/display/PEKKO/Pekko+Akka+Compatibility
https://pekko.apache.org/docs/pekko/current/release-notes/index.html
Ivan Hraško July 31, 2024 at 10:53 AMEdited
We have replaced akka with pekko in repackaged-akka package and renamed it to repackaged-pekko. We aim to not touch other package names, class names, etc.
The default ports and configuration for pekko is different than for akka - this has been reflected in akka.conf renamed to pekko.conf.
Downstream projects willing to adopt need to deal with:
repackaged-akka package changed to repackaged-pekko
we are no more using akka.conf but pekko.conf
they need to adapt their own configurations (aplication.conf, etc.) as well
change dependencies and imports
Projects which need to be adapted includes:
netconf - NETCONF-1341
jsonrpc - JSONRPC-60
daexim - DAEXIM-19
ovsdb - just one usage in not-up-to-date postman collection (ignored)
transport PCE - TRNSPRTPCE-806
test - INTTEST-145
builder - RELENG-163
docs - DOCS-153
distribution - INTDIST-118
Apache Pekko is a fork of Akka codebase before it switched to Business Software License and thus became lagging 3+ years behind.
While we want to move away for Akka, it seems prudent to switch to Pekko to whatever support we can get from there. If the worst comes to pass, we can always switch back.
The compatibility impact of this move needs to be evaluated and the migration path there (and possibly back) needs to be documented.