Child Pages
| Child pages (Children Display) |
|---|
Contents
| Table of Contents |
|---|
Overview
| Target Release Name | Montreal |
| Project Lifecycle State | Mature |
| Participating Company | AT&T, Bell Canada, Ericsson |
Scope
What is this release trying to address?
The Policy Framework is a mature project. The theme of the work in Montreal is "consolidation". We are improving the non-functional aspects of the project by improving performance, resilience and maintenance.
Requirements
There are no formal requirements on the Policy Framework project in Montreal.
Minimum Viable Product
The Policy Framework will be maintained as a minimum viable product on the master branch for the entirety of this project.
Functionalities
The project has the following epics:
| Jira Legacy | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Longer term roadmap
As the Policy Framework is a mature project, we will continue to evolve and enhance the framework. The medium to long term focus is on scalability and resilience.
Release Deliverables
See Policy Framework Project: Component Versions and Policy R10 Jakarta Independent Versioning And Release Process Plan.
Sub-Components
See Policy Framework Project: Component Versions.
Architecture
High level architecture diagram
See the Policy Framework Architecture page in the ONAP documentation.
Architecture Subcommittee Review
No architectural changes are proposed to the Policy Framework in the Montreal release so no architecture review is required.
Platform Maturity
See Montreal Release Platform Maturity.
API Incoming Dependencies
No change expected.
API Outgoing Dependencies
No change expected.
Third Party Products Dependencies
No change expected.
Testing and Integration Plans
Testing will follow the processes and plans for the ONAP Montreal release.
Gaps
No gaps identified at present.
Release Milestone
The milestones are defined at the Release Level and all the supporting project agreed to comply with these dates.
Other Information
Vendor Neutral
If this project is coming from an existing proprietary codebase, ensure that all proprietary trademarks, logos, product names, etc. have been removed. All ONAP deliverables must comply with this rule and be agnostic of any proprietary symbols.
Free and Open Source Software
FOSS activities are critical to the delivery of the whole ONAP initiative. The information may not be fully available at Release Planning, however to avoid late refactoring, it is critical to accomplish this task as early as possible.
List all third party Free and Open Source Software used within the release and provide License type (BSD, MIT, Apache, GNU GPL,... ).
In the case non Apache License are found inform immediately the TSC and the Release Manager and document your reasoning on why you believe we can use a non Apache version 2 license.
Each project must edit its project table available at Project FOSS.
Charter Compliance
The project team comply with the ONAP Charter.