Recognizing the contributions of your peers to the success in delivering ONAP Honolulu
...
Nominations open through 17:00 pacific on
TSC Voting Closes 17:00 pacific on
...
Top Achievement Award
Nominated and chosen by the community- Presented Presented to the individual who has demonstrated unparalleled dedication in the formation and prosperity of ONAP, whose exemplar behavior and actions play a pivotal role in the successful and timely delivery of the ONAP release and growth of a thriving global community, and and fosters an atmosphere of equal cooperation between member companies, individuals, and geographies.
...
Citizenship Award
Nominated and chosen by the community- Presented to the individual who provided the most assistance to others outside of their own project, in the form of education, guidance, code reviews, debugging, bug fixes or similar support, whose behavior also help to impart a culture equal cooperation between member companies, individuals and geographies
...
S3P Improvements
Nominated and chosen by the community- Presented to the Project which made the most significant progress improving their S3P requirements (stability, security, scalability and performance) serving as a model for other projects to follow in this area.
| Nominated Candidate | Reason for Nomination | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| DCAE Project | DCAE project had major rearchitecture initiative started in Honolulu release to migrate DCAE microservices deployments from Cloudify to Helm. This was driven based on community requests to align all ONAP component deployment through helm and under OOM. In H release, we delivered migration of subset of DCAE services (ves/prh/tcagen2/hv-ves) to helm, maintaining complete backward compatibility with Cloudify based deployment and S3P goals. The work done in H release provided a base for Istanbul to add new features through common svc template (under OOM) and migration of rest of DCAE components to helm. As the solution was completly backward compatible - operator/user have choice to instantiate DCAE either via helm or cloudify or both. In addition to transformation initative, several components including Cloudify-Manager, Bootstrap, Plugins, PolicyHandler were upgraded to Python3 in Honolulu part of S3P (security) improvements. | ||||||||||||
| Integration project | The first automated stability tests have been included in Weekly CI in honolulu. It consists in 2 long duration tests, 1 dealing with onboarding (stressing mainly the SDC) and 1 with an instantiation (involving SO, SDNC, AAI and SDC). Unlike the previous stability tests, which were running only 1 test continuously it was possible to initiate reasonable load on the system (5 // onboarding during 24h and 10 // instantiation during 24) and to detect issues on cassandra and mariadb-galera. Some optimization have been suggested, work is still in progress but thanks to these tests it is possible to get a first real feedback on the system under load. These tests were possible thanks to an light overlay development on top of the smoke tests developed by the integration team based on onapsdk. kudos to Natacha Chéreau an intern who help the integration project to finalize this framework and integrated the tool in CI. See stability chapter in https://docs.onap.org/projects/onap-integration/en/latest/integration-s3p.html#integration-s3p) | ||||||||||||
| Service Orchestrator Project | 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. | ||||||||||||
| CPS Project | The CPS project team, led by Toine Siebelink , was a brand new ONAP project. Although Honolulu was its first release, the project team has been able to meet all the non functional requirements that were developed by the other projects over the past 7 releases i.e. CII Badging, operational deployment, platform maturity, license issues, CSIT, test coverage, pair-wise testing, security vulnerabilities, Python 3.8, etc. | ||||||||||||
...