...
Nominated Candidate | Reason for Nomination |
---|---|
Jack is working hard on DCAE for a lot of years. His work in OOM made him a committer also on this project. Being retired, Jack is working only for the good of ONAP and it's dedication is really a plus for the whole ONAP project Jack contribution has been instrumental in moving DCAE to new architecture under OOM/helm for Istanbul release. Jack has been supporting ONAP as committer/contributor for several ONAP project - DCAE, CCSDK since inception, recently approved as OOM committer based his continued good track record. Jack is serving ONAP post retirement (from AT&T since mid-2020) as an independent contributor - his efforts and dedication for ONAP is extremely commendable. | |
...
Nominated Candidate | Reason for Nomination |
---|---|
DCAE Project | The DCAE project continue to evolve their platform maturity requirements release after release. They reached up to 96% Silver Level - CII Badging as part of their Istanbul release - Istanbul Release Platform MaturityIn addition, the DCAE project made 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 Istanbul release, all Key Security updates for Istanbul
Architecture Alignment - Major progress made toward DCAE architecture tranformation to remove Cloudify/Consul dependencies; this simplies the architecture and deployment of DCAE MS. All DCAE microservices migration to helm was completed in Istanbul release. Since Honolulu, 13 additional mS MS has been delivered added for Helm deployment support and (with parallel support under Cloudify/blueprint (legacy) retained for regression/backward compatibility: - K8S Secret/Environment mapping - Consul loader for application config distribution The DCAE project also removed Consul Dependency for DCAE components (DCAEGEN2-2630) Under cloudify deployments, Consul is used as central configuration store for all applications. With migration to Helm, the consul dependency is being removed by switching config management through K8S Configmap. This allows application to be deployed standalone in multi/edge cloud without any dependency on central platform components. As the solution was completly backward compatible - operator/user have choice to instantiate DCAE either via helm or cloudify or both. |
Anchor | ||||
---|---|---|---|---|
|
ONAP Demonstration Award(s)
...