This page lists all projects that have been approved by TSC to be a part of the ONAP Platform.
| Project Name | Approved Date | Project Tech. Lead | Description | State |
|---|---|---|---|---|
| A & AI | June 9, 2017 | James Forsyth | 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 |
| Application Authorization Framework | June 29, 2017 | The goal of the project is to provide consistent authentication, authorization and security to various ONAP components. AAF organizes software authorizations so that applications, tools and services can match the access needed to perform job functions. AAF is designed to cover Fine-Grained Authorization, meaning that the Authorizations provided are able to use an Application's detailed authorizations, such as whether a user may be on a particular page, or has access to a particular Pub-Sub topic controlled within the App. This is a critical function for Cloud environments, as Services need to be able to be installed and running in a very short time, and should not be encumbered with local configurations of Users, Permissions and Passwords. The sister framework CADI ( Code Access Data Identity ) allows Java Applications to utilize Identity Authentication methods as plugins. Certificate Manager delivers X509 certificates in support of 2 way x509 TLS. | Approved V.36 | |
| APPC | June 9, 2017 | The Application Controller (APPC) performs functions to manage the lifecycle of VNFs and their components providing model driven configuration, abstracts cloud/VNF interfaces for repeatable actions, uses vendor agnostic mechanisms (NETCONF, Chef via Chef Server and Ansible) and enables automation. | Approved V.46 | |
| CLAMP | June 8, 2017 | 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 | |
| Common Controller SDK | June 9, 2017 | This project provides a common set of reusable code that can be used across multiple controllers. | Approved v.39 | |
| DCAE | June 9, 2017 | DCAE is the umbrella name for a number of components collectively fulfilling the role of Data Collection, Analytics, and Events generation for ONAP. The architecture of DCAE targets flexible, plug-able, micros-service oriented, model based component deployment and service composition. DCAE also support multi-site collection and analytics operations which are essential for large ONAP deployments. | Approved V.60 | |
| DMaaP | June 23, 2017 | Ramprasad Koya | DMaaP is a premier platform for high performing and cost effective data movement services that transports and processes data from any source to any target with the format, quality, security, and concurrency required to serve the business and customer needs. | Approved v.32 |
| Documentation | June 9, 2017 | Documentation creates and maintains documentation targeted to ONAP user audiences and the tasks they perform. | Approved v.41 | |
| External API Framework | June 9, 2017 | The External API Framework project describes and defines the APIs between ONAP and External Systems, including ONAP interfaces targeted on BSS/OSS, peering, B2B, etc. | Approved v.48 | |
| Holmes | June 9, 2017 | Holmes project provides alarm correlation and analysis for Telecom cloud infrastructure and services, including hosts, vims, VNFs and NSs. Holmes aims to find the real reason which causes the failure or degradation of services by digging into the ocean of events collected from different levels of the Telecom cloud. | Approved v.29 | |
| 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 |
| Logging Enhancements Project | June 29, 2017 | ONAP consists of many components and containers, and consequently writes to many logfiles. The volume of logger output may be enormous, especially when debugging. Large, disparate logfiles are difficult to monitor and analyze, and tracing requests across many files, file systems and containers is untenable without tooling. The problem of decentralized logger output is addressed by analytics pipelines such as Elastic Stack. Elastic Stack consumes logs, indexes their contents in Elasticsearch, and makes them accessible, queryable and navigable via a sophisticated UI, Kibana Discover. This elevates the importance of standardization and machine-readability. Logfiles can remain browseable, but output can be simplified. | Approved V.9 | |
| Microservices Bus | June 8, 2017 | Microservices Bus provide key infrastructure functionalities to support Microservice Architecture including service registration/discovery, service gateway, service load balancer. | Approved v.73 | |
| Modeling | June 9, 2017 | The unified model-driven approach uses models as sources of data for generating processes/codes and following workflows (not code development as source) – this way, the system can be more flexible and future proof, easy to update and use for cross-platform solutions since the “only” thing needed is Model update and manipulation through Engine. | Approved v.66 | |
| Multi VIM/Cloud | June 8, 2017 | 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 | |
| Music | Jan 16, 2018 | Bharath Balasubramanian | To achieve 5 9s of availability on 3 9s or lower software and infrastructure in a cost-effective manner, ONAP components need to work in a reliable, active-active manner across multiple sites (platform-maturity resiliency level 3). A fundamental aspect of this is state management across geo-distributed sites in a reliable, scalable, highly available and efficient manner. This is an important and challenging problem because of three fundamental reasons:
In this project, we identify common state management concerns across ONAP components and provide a multi-site state coordination/management service (MUSIC) with a rich suite of recipes that each ONAP component can simply configure and use for their state-management needs. | Approved V51 |
| ONAP CLI | June 8, 2017 | This project is providing required Command-Line Interface(CLI) as commands to operate ONAP functionalities from Unix or windows shell. | Approved v.20 | |
| ONAP Operations Manager | June 8, 2017 | 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 | |
| ONAP Optimization Framework | June 23, 2017 | Sarat Puthenpura | This project currently provides the following two core platform optimization services, which are built to be service independent, policy driven, and extensible along with an optimization framework to enhance these or creating new services. | Approved v.42 |
| ONAP University | June 22, 2017 | Nermin Mohamed | Provide overview of the ONAP University training courses for users, developers and any other interested parties of member and non-member companies. | Approved v.9 |
| ONAP Usecase UI Project Proposal | June 8, 2017 | 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 | |
| Policy Framework Project Proposal | June 8, 2017 | 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 | |
| Portal Platform Project Proposal | June 8, 2017 | The ONAP Portal is a platform that provides the ability to integrate different ONAP applications into a centralized Portal Core. | Approved v.22 | |
| SDN-C | June 9, 2017 | 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 | |
| Service Design & Creation | June 8, 2017 | 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 | |
| Service Orchestrator | June 9, 2017 | 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 | |
| VF-C: Virtual Function Controller | June 8, 2017 | 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 | |
| VID project | June 8, 2017 | 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 | |
| VNF SDK | June 8, 2017 | 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 | |
| VNF Requirements | June 9, 2017 | The VNF Requirements creates and maintains VNF Requirements targeted to VNF Provider and Services Provider and the tasks they perform. | Approved v.20 | |
| VNF Validation (VVP) | June 22, 2017 | The project is to develop a validation program to provide assurance of VNF interoperability with ONAP. Obtaining a validation shall be a self-service activity and should be against a reference release of ONAP for use by the VNF provider & any other validation authority. | Approved v.25 | |
| ONAP Benchmark | Dec 13, 2017 | Contact: Chen Yan Approved as Integration Subproject |
| Approved v21 |
30 Projects approved