An approved project has received formal sign-off by the TSC to be a stand-alone ONAP Project. It does not mean that the project is still actively being maintained.
|Project Tech. Lead||Description||TSC Approval|
no active PTL
formerly Jonathan Gathman
|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.||June 29, 2017||v.36|
|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.||June 9, 2017||v.36|
no active PTL
formerly Takamune Cho
|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.||June 9, 2017||v.46|
|This project provides a common set of reusable code that can be used across multiple controllers. The Controller Design Studio (CDS) is part of Common Controller SDK (CCSDK).||June 9, 2017||v.39|
|CI-Man||Incubation||Jessica Wagantall||The CI Management project is dedicated to managing the code resources related to the CI systems. It is intended as a way for the community to collaborate on the design and management of the CI infrastructure where it is possible to do so.||June 8, 2017||N/A|
merged; see POLICY project
formerly 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.||June 8, 2017||v.37|
This project is providing required Command-Line Interface(CLI) as commands to operate ONAP functionalities from Unix or windows shell.
|June 8, 2017||v.20|
|CPS||Incubation||The Configuration Persistence Service is a platform component that is designed to serve as a model-driven data repository for run time data that needs to be persistent.||October 8, 2020|
|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.||June 9, 2017||v.60|
Data Movement as a Platform 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.
|June 23, 2017||v.32|
|Documentation creates and maintains documentation targeted to ONAP user audiences and the tasks they perform.||June 9, 2017||v.41|
no active PTL
formerly Adrian OSullivan
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.
|June 9, 2017||v.48|
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.
|June 9, 2017||v.29|
|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.||June 8, 2017||v.71|
no active PTL
formerly Prudence Au
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.
|June 29, 2017||v.9|
|Modeling||Mature||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.||June 9, 2017||v.66|
|Microservices Bus provide key infrastructure functionalities to support Microservice Architecture including service registration/discovery, service gateway, service load balancer.||June 8, 2017||v.73|
|June 8, 2017||v.87|
no active PTL
formerly Bharath Balasubramanian
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.
|Jan 16, 2018||v.57|
|OOF||Mature||ONAP Optimization Framework 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.||June 23, 2017||v.42|
PTL required (as of 22/03/15)
formerly Sylvain Desbureaux
|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).||June 8, 2017||v.70|
|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.||June 8, 2017||v.46|
|The ONAP Portal is a platform that provides the ability to integrate different ONAP applications into a centralized Portal Core.||June 8, 2017||v.22|
|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.||June 8, 2017||v.48|
|The Software Defined Network Controller project provides a global network controller, built on the Common Controller Framework, which manages, assigns and provisions network resources.||June 9, 2017||v.61|
|The ONAP Service Orchestrator 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.||June 9, 2017||v.59|
Provide overview of the ONAP University training courses for users, developers and any other interested parties of member and non-member companies.
|June 22, 2017||v.9|
|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.||June 8, 2017||v.30|
|The Virtual Function Controller leverages ETSI NFV MANO architecture and information model as a reference, and implements full life cycle management and FCAPS of VNF and NS.||June 8, 2017||v.69|
Virtual Infrastructure Deployment provides a well-structured organization of infrastructure deployment, instantiation and change-management operations used by Operations to derive orchestrations and change-management.
|June 8, 2017||v.12|
no active PTL
former Trevor Lovett
|The VNF Requirements creates and maintains VNF Requirements targeted to VNF Provider and Services Provider and the tasks they perform.||June 9, 2017||v.20|
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
|June 8, 2017||v.61|
|VVP||Incubation||The VNF Validation 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.||June 22, 2017||v.25|