Seshu Kumar has been playing vital roles in ONAP right from its incubation. His technical acumen together with his leadership skills have been put to test multiple times in Honolulu release and helped in successful deliver of the the release. He showcased utmost dedication and commitment, working round the clock in resolution of the issues on the runtime flows blocking the gating flows across the releases including the H release. 

As PTL of SO he Architected, designed and coordinated the implementation of  the key improvements to the SO project that helped in making it much closer to a production grade. He has been playing a key role in reviewing and assisting most of the functional aspects of ONAP like the E2E 5G slicing, ETSi, Multitenancy and the CCVPN. Has played key role in improving the self verification process of the SO in H release.

Seshu Co-leads the efforts of the CNF Orchestration implementation in ONAP where he works on preparing & executing the roadmap, designing, developing and verification of the functionality in ONAP. He along with the team works relentlessly in delivering the functionality across releases, In H release helm enrichment were improved further over the Cnf adapter flows. Efforts are put in H release to merge the Native helm and ETSi orchestration flows as a future item and is being worked upon.

As member of the ONAP TSC, contributing to task forces and sub-committees of ONAP, is Liaison for XGVela and constantly working on improving the collaboration of ONAP with other SDOs (3GPP, TMF, ETSi...) and opensource projects (XGVela, EMCO, OKD....).

As an evangelist of ONAP has provided numerous demos of ONAP to new players (operators and vendors) and has been helping them in their internal PoCs.

Swami also seized any opportunity to promote the E2E Network Slicing Blueprint by contributing to the ONAP 5G Blueprint, presenting the ONAP Community at OPS 5G meeting, supporting the ONAP for Enterprise Task Force and LFN 5G Super Blueprint,  building demos, participating to the Openstack Summit, Open Infrastructure Summit, LFN DDF Events, LFN Webinar.

Andreas is very involved in the TSC and also contributes to many projects: Documentation, Integration, OOM and CDS. He is fully focused to operationalize ONAP to be used in production environment. He is also managing with DT team some integration platform to help the improve the integration. Andreas is always volunteer to help and bring support to the comunity.

He has also been very active to setup the Honolulu Maintenance Release and acted in different TSC Task forces to always improve the various processes.

Liam has been working in ONAP since Beijing release. He has contributed heavily into the architecture & development of Policy Framework project, currently serving as PTL of the project. He has contributed to oparent, CLAMP and other projects too. In the past few years, he has served as a mentor for control loop automation domain and has helped many folks in the community to learn and gain knowledge about the domain. He was also a member of the release cadence team that proposed the new way of managing ONAP release train & have more frequent releases.

Recently, he has been working on architecting & developing Tosca based Control Loop Management software which intends to be much more robust, flexible & plug n play with easy integration for any new component. Thereby making all the components (DCAE, Policy, CDS etc.) work together in a loop seamlessly.

He has always been available in the community to provide technical direction, debug an issue, propose new ideas and work together as a team.

Liam has also participated in most of the ONES/DTF conferences. And presented live demos, lightning talks & in-depth tutorial sessions to spread knowledge in the community.

Integration project

WINNER

SO underwent major transformation in the H-release making it closer to being a true production-grade project in ONAP. Some of the key improvements are listed below.

SO is of the most important projects of ONAP with huge changes accounted for every release. It is growing by leaps and bounds as new functional features are added release after release. This brought a huge technical debt that started accumulating. Addressing this was a mammoth task that demanded a huge amount of effort from all the stake holders in H-release. Prior to this, SO has been a single repo on Gerrit as this was a huge code block with a huge impact on debugging, build, time-to-market and overall maintenance. Any changes in SO required the entire code to be built leading to a huge effort and delays in delivery.

We addressed most of these issues based on the lessons learnt from the previous releases and are relentlessly working on bringing about further improvements in the upcoming releases.