This page lists all projects that have been approved to be a part of the ONAP Platform
| Project Name | Approved Date | Project Team Lead | Description | State |
|---|---|---|---|---|
| CLAMP | June 8, 2017 | Gervais-Martial NGUEKO Gervais-Martial Ngueko | CLAMP is a platform for designing and managing control loops. It is used to design a closed loop, configure it with specific parameters for a particular network service, then deploying and undeploying it. Once deployed, the user can also update the loop with new parameters during runtime, as well as suspending and restarting it. | Approved v.37 |
| VF-C: Virtual Function Controller | June 8, 2017 | Lingli Deng Lingli Deng | VF-C leverages ETSI NFV MANO architecture and information model as a reference, and implements full life cycle management and FCAPS of VNF and NS. | Approved v.69 |
| ONAP Operations Manager | June 8, 2017 | Jun Nicolas Hu Jun Hu | This proposal introduces the ONAP Platform OOM (ONAP Operations Manager) to efficiently Deploy, Manage, Operate the ONAP platform and its components (e.g. MSO, DCAE, SDC, etc.) and infrastructure (VMs, Containers). | Approved v.70 |
| VNF SDK | June 8, 2017 | Chris Donley Chris Donley | VNF onboarding is a challenge across the industry because of the lack of a standard format for VNFs. This project will build an ecosystem for ONAP compatible VNFs by developing tools for vendor CI/CD toolchains and developing validation and testing tools | Approved v.61 |
| Multi VIM/Cloud | June 8, 2017 | Danny Lin danny lin | Multi-VIM/Cloud project aims to enable ONAP to deploy and run on multiple infrastructure environments, for example, OpenStack and its different distributions (e.g. vanilla OpenStack, Wind River, etc...), public and private clouds (e.g. VMware, Azure), and micro services containers, etc. | Approved v.87 |
| Service Design & Creation | June 8, 2017 | Michael Lando Michael Lando | Service Design Creation provides a well-structured organization of visual design & testing tools, templates and catalogs to model and create resources, and services. The output of the SDC is a set of models which drives the orchestration. | Approved v.48 |
| VID project | June 8, 2017 | Hemli Amichai Amichai Hemli | Provides a well-structured organization of infrastructure deployment, instantiation and change-management operations used by Operations to derive orchestrations and change-management. | Approved v.12 |
| Microservices Bus | June 8, 2017 | Huabing Zhao HuabingZhao | Microservices Bus provide key infrastructure functionalities to support Microservice Architecture including service registration/discovery, service gateway, service load balancer. | Approved v.73 |
| ONAP CLI | June 8, 2017 | Kanagaraj Manickam user-67d6f | This project is providing required Command-Line Interface(CLI) as commands to operate ONAP functionalities from Unix or windows shell. | Approved v.20 |
| ONAP Usecase UI Project Proposal | June 8, 2017 | Tao Shen Tao Shen | The ONAP Usecase UI project is the ONAP subsystem that provides Graphical User Interface (GUI) for operators and end-users from the point of view of use cases. | Approved v.30 |
| Portal Platform Project Proposal | June 8, 2017 | Manoop Talasila Manoop Talasila | The ONAP Portal is a platform that provides the ability to integrate different ONAP applications into a centralized Portal Core. | Approved v.22 |
| Policy Framework Project Proposal | June 8, 2017 | Pamela Dragosh Pamela Dragosh | The Policy subsystem of ONAP maintains, distributes, and operates on the set of rules that underlie ONAP’s control, orchestration, and management functions. Policy provides a centralized environment for the creation and management of easily-updatable conditional rules. | Approved v.46 |
| Integration | June 8, 2017 | Helen Chen | Integration is responsible for ONAP cross-project system integration, CI/CD, and all related end-to-end release use cases testing with VNFs necessary for the successful delivery and industry adaption of the ONAP project as a whole. | Approved V.71 |
| Service Orchestrator | June 9, 2017 | DeWayne Filppi DeWayne Filppi | The SO provides the highest level of service orchestration in the ONAP architecture. SO is implemented via BPMN flows that operate on Models distributed from SDC that describe the Services and associated VNFs and other Resource components. | Approved v.59 |
| Common Controller SDK | June 9, 2017 | Dan Timoney Dan Timoney | This project provides a common set of reusable code that can be used across multiple controllers. | Approved v.39 |
| SDN-C | June 9, 2017 | Dan Timoney Dan Timoney | The SDN-C project provides a global network controller, built on the Common Controller Framework, which manages, assigns and provisions network resources. | Approved v.61 |
| Documentation | June 9, 2017 | Rich Bennett Rich Bennett | Documentation creates and maintains documentation targeted to ONAP user audiences and the tasks they perform. | Approved v.41 |
| External API Framework | June 9, 2017 | Andy Mayer Andy Mayer | The External API Registration project describes and defines the APIs between ONAP and External Systems, including ONAP interfaces targeted on BSS/OSS, peering, B2B, etc. | Approved v.48 |
| VNF Requirements | June 9, 2017 | Steven Wright Steven Wright | The VNF Requirements creates and maintains VNF Requirements targeted to VNF Provider and Services Provider and the tasks they perform. | Approved v.20 |
| A & AI | June 9, 2017 | Manisha Aggarwal | Active and Available Inventory (AAI) is the ONAP subsystem that provides real-time views of Resources and Services and their relationships. AAI not only forms a registry of active, available, and assigned assets, it also maintains up-to-date views of the multidimensional relationships among these assets, including their relevance to different components of ONAP. | Approved v.36 |
| APPC | June 9, 2017 | Scott Seabolt | Scott Seabolt | Approved V.46 |
18 Projects approved