The list below summarizes the projects that had a project proposal approved for Amsterdam Release and wish to participate into Beijing Release. These projects DO NOT need to submit a new project proposal.
At M1 Release Planning milestone, Jan 18, 2018, the TSC will review all project planning materials and provide its disposition. It is expected that all projects intending to participate into Beijing submit their Project Planning Materials no later than Jan 8, 2018.
That will provide time for everyone to:
- understand each project scope
- review dependencies
- review all M1 materials
- ask openly question
- smooth the TSC approval process
Calendar for Beijing Release.
For those who intend to propose a new project, use the ONAP Project Proposal Template and post it in the Proposed Project list.
New project proposal for Beijing are available here. These new projects will be reviewed by TSC during Santa Clara F2F the week of Dec 11-13.
| Project Name | Intention submission Date | Project Tech. Lead | Description | |
|---|---|---|---|---|
| 1 | A & AI | Oct 25, 2017 | 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. | |
| 2 | Application Authorization Framework | Nov 5, 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. | |
| 3 | APPC | Nov 4, 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. | |
| 4 | CLAMP | Oct 30, 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. | |
| 5 | Common Controller SDK | Oct 13, 2017 | This project provides a common set of reusable code that can be used across multiple controllers. | |
| 6 | DCAE | Nov 4, 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. | |
| 7 | DMaaP | Nov 5, 2017 | 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. | |
| 8 | Documentation | Nov 4, 2017 | Documentation creates and maintains documentation targeted to ONAP user audiences and the tasks they perform. | |
| 9 | External API Framework | Nov 7, 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. | |
| 10 | Holmes | Oct 26, 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. | |
| 11 | Integration | Oct 25, 2017 | 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. | |
| 12 | Logging Enhancements Project | Oct 30, 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. | |
| 13 | Microservices Bus | Oct 26, 2017 | Microservices Bus provide key infrastructure functionalities to support Microservice Architecture including service registration/discovery, service gateway, service load balancer. | |
| 14 | Modeling | Oct 26, 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. | |
| 15 | Multi VIM/Cloud | Oct 26, 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. | |
| 16 | ONAP CLI | Oct 26, 2017 | This project is providing required Command-Line Interface(CLI) as commands to operate ONAP functionalities from Unix or windows shell. | |
| 17 | ONAP Operations Manager | Oct 26, 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). | |
| 18 | ONAP Optimization Framework | Nov 6, 2017 | The goal of this project is to meet ONAP's need for core platform optimization services like VNF placement, Change Management scheduling, etc. In the Beijing release (R2), we plan to deliver the Homing and Allocation Service (HAS), a policy driven service placement and resource allocation service that enables optimal placement of services and VNFs on a multi-site, multi-VIM infrastructure. We envision the set of optimization requirements to grow over time as the ONAP platform needs arise, and OOF will help handle this effectively, with minimal or little new code development for on-boarding new services. | |
| 19 | ONAP Usecase UI Project Proposal | Oct 26, 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. | |
| 20 | Policy Framework Project Proposal | Oct 26, 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. | |
| 21 | Portal Platform Project Proposal | Oct 26, 2017 | The ONAP Portal is a platform that provides the ability to integrate different ONAP applications into a centralized Portal Core. | |
| 22 | SDN-C | Oct 13, 2017 | The SDN-C project provides a global network controller, built on the Common Controller Framework, which manages, assigns and provisions network resources. | |
| 23 | Service Design & Creation | Oct 28, 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. | |
| 24 | Service Orchestrator | Oct 25, 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. | |
| 25 | VF-C: Virtual Function Controller | Oct 26, 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. | |
| 26 | VID project | Oct 29, 2017 | Provides a well-structured organization of infrastructure deployment, instantiation and change-management operations used by Operations to derive orchestrations and change-management. | |
| 27 | VNF SDK | Nov 20, 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 | |
| 28 | VNF Requirements | Nov 6, 2017 | The VNF Requirements creates and maintains VNF Requirements targeted to VNF Provider and Services Provider and the tasks they perform. | |
| 29 | VNF Validation (VVP) | Oct 31, 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. |