Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 9 Next »

Overview

Target Release NameJakarta
Project Lifecycle StateMature
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 Istanbul is "consolidation". We are improving the non-functional aspects of the project by improving performance, resilience and maintenance. We are also consolidating the Policy/CLAMP project merges.

Requirements

There is one formal requirement on the Policy Framework project in Jakarta

REQ-994 - Getting issue details... STATUS

Minimum Viable Product

Describe the MVP for this release.

Functionalities

List the functionalities that this release is committing to deliver by providing a link to JIRA Epics and Stories. In the JIRA Priority field, specify the priority (either High, Medium, Low). The priority will be used in case de-scoping is required. Don't assign High priority to all functionalities.

Epics



KeySummaryTCreatedUpdatedDueAssigneeReporterPStatusResolution
SANDBOX-252 Finalized Code Submission EpicJun 23, 2021Jun 23, 2021Aug 26, 2021UnassignedDavid McBrideMedium Open Unresolved
SANDBOX-251 Finalized Code Submission EpicJun 23, 2021Jun 23, 2021Aug 26, 2021UnassignedDavid McBrideMedium Open Unresolved
SANDBOX-241 EP: Patients accessing ZOOM EpicMar 15, 2020Mar 16, 2020
UnassignedHind KhalifaMedium Open Unresolved
SANDBOX-186 filtering men shoes EpicMar 11, 2020Mar 18, 2020
Munira AhmedMunira AhmedMedium Open Unresolved
SANDBOX-178 EP: Treatment of Coronavirus EpicMar 11, 2020Mar 11, 2020
UnassignedSummer GamalMedium Open Unresolved
SANDBOX-177 EP: Coronavirus Prevention EpicMar 11, 2020Mar 16, 2020
UnassignedSummer GamalMedium Open Unresolved
SANDBOX-130 TeamSnap Account EpicMar 10, 2020Mar 10, 2020
UnassignedSARRA FALFOULMedium Open Unresolved
SANDBOX-127 Cards payments EpicMar 10, 2020Mar 10, 2020
Unassignedtayseer AbdelMedium Open Unresolved
SANDBOX-126 EP: FB profile images EpicMar 10, 2020Mar 15, 2020
UnassignedMuhaned MohamedHigh Open Unresolved
SANDBOX-125 EP: FEDEX EpicMar 10, 2020Mar 10, 2020
UnassignedSummer GamalMedium Open Unresolved
SANDBOX-124 Coronavirus EpicMar 09, 2020Mar 10, 2020
UnassignedSohrab KazmiHighest Open Unresolved
SANDBOX-123 EP: Carpet Cleanning EpicMar 09, 2020Mar 10, 2020
Wael GorashiWael GorashiMedium Open Unresolved
SANDBOX-122 Uploading a post to my IG profile EpicMar 09, 2020Mar 10, 2020
UnassignedSHAALINI CHANDRASEKARANMedium Open Unresolved
SANDBOX-121 Remote_Chaka Pissa EpicMar 09, 2020Mar 10, 2020
UnassignedDafalla HamadMedium Open Unresolved
SANDBOX-120 INSTA-Sizing EpicMar 09, 2020Mar 10, 2020
UnassignedMunira AhmedMedium Open Unresolved
SANDBOX-119 (filtering women's shoes) EpicMar 09, 2020Mar 11, 2020
Unassignedhelen zahiMedium Open Unresolved
SANDBOX-118 zolo EpicMar 09, 2020Mar 11, 2020
UnassignedSabri MusaMedium Open Unresolved
SANDBOX-116 Test Epic ZZ EpicMar 09, 2020Mar 11, 2020
UnassignedZoheb ZaidiMedium Open Unresolved
SANDBOX-114 Test Epic 3/9 EpicMar 09, 2020Mar 09, 2020
UnassignedZoheb ZaidiHigh Open Unresolved


19 issues Refresh



Stories



KeySummaryTCreatedUpdatedDueAssigneeReporterPStatusResolution
SANDBOX-243 zoom team:Creating an account on ZOOM app StoryMar 16, 2020Mar 16, 2020
UnassignedHind KhalifaMedium Open Unresolved
SANDBOX-242 zoom team :download zoom app for patients StoryMar 16, 2020Mar 16, 2020
Hind KhalifaHind KhalifaMedium Open Unresolved
SANDBOX-240 Mens Shoes- fashion StoryMar 11, 2020Mar 11, 2020
UnassignedSARRA FALFOULMedium Open Unresolved
SANDBOX-210 Diva1 - shoe model- flat shoe StoryMar 11, 2020Mar 17, 2020
Unassignedtayseer AbdelMedium Open Unresolved
SANDBOX-206 Diva1 - shoe model- walking StoryMar 11, 2020Mar 17, 2020
Unassignedhelen zahiMedium Open Unresolved
SANDBOX-205 Diva1- Men shoes- dress up shoes StoryMar 11, 2020Mar 17, 2020
UnassignedMunira AhmedMedium Open Unresolved
SANDBOX-204 Diva1 - Men's Shoes: Trainers StoryMar 11, 2020Mar 16, 2020
Dafalla HamadDafalla HamadMedium Delivered Unresolved
SANDBOX-200 Diva1 - shoe model- boots StoryMar 11, 2020Mar 17, 2020
UnassignedZoheb ZaidiMedium Open Unresolved
SANDBOX-196 Diva1 - shoe model- high heel shoes StoryMar 11, 2020Mar 17, 2020
UnassignedZoheb ZaidiMedium Open Unresolved
SANDBOX-195 US: 2 Coronavirus Prevention Team- Treating the virus StoryMar 11, 2020Mar 17, 2020
Summer GamalSummer GamalMedium Closed Done
SANDBOX-194 Diva1 - Men's Shoes-Types of shoes StoryMar 11, 2020Mar 17, 2020
UnassignedDafalla HamadMedium Open Unresolved
SANDBOX-193 US: 2 Coronavirus Prevention Team- Treating the virus StoryMar 11, 2020Mar 17, 2020
UnassignedSummer GamalMedium Open Unresolved
SANDBOX-192 US: 2 Coronavirus Prevention Team- Treating the virus StoryMar 11, 2020Mar 17, 2020
UnassignedSummer GamalMedium Open Unresolved
SANDBOX-191 US: Coronavirus Prevention Team- Treating the virus StoryMar 11, 2020Mar 17, 2020
UnassignedSummer GamalMedium Open Unresolved
SANDBOX-190 US: Coronavirus Prevention Team- Treating the virus StoryMar 11, 2020Mar 17, 2020
UnassignedSummer GamalMedium Open Unresolved
SANDBOX-189 US: 2 Coronavirus Prevention Team- Treating the virus StoryMar 11, 2020Mar 17, 2020
UnassignedSummer GamalMedium Open Unresolved
SANDBOX-188 Diva1 - shoe model- tennis shoes StoryMar 11, 2020Mar 17, 2020
Unassignedtayseer AbdelMedium Open Unresolved
SANDBOX-187 US: 2 Coronavirus Prevention Team- Treating the virus StoryMar 11, 2020Mar 17, 2020
UnassignedSummer GamalMedium Open Unresolved
SANDBOX-185 US: 2 Coronavirus Prevention Team- Treating the virus StoryMar 11, 2020Mar 17, 2020
UnassignedSummer GamalMedium In Progress Unresolved
SANDBOX-183 US: Coronavirus Prevention Team- How to Prevent the virus StoryMar 11, 2020Mar 17, 2020
UnassignedSummer GamalMedium Open Unresolved


Showing 20 out of 44 issues Refresh




Longer term roadmap

Indicate at a high level the longer term roadmap. This is to put things into the big perspective.

Release Deliverables

Indicate the outcome (Executable, Source Code, Library, API description, Tool, Documentation, Release Note, etc) of this release.

To fill outTo fill out

Sub-Components

List all sub-components part of this release.
Activities related to sub-components must be in sync with the overall release.

Sub-components are repositories and are consolidated in a single centralized place. Edit the Release Components name for your project in the centralized page.

Architecture

High level architecture diagram

At that stage within the Release, the team is expected to provide more Architecture details describing how the functional modules are interacting.

Indicate where your project fit within the ONAP Architecture diagram.

Block and sequence diagrams showing relation within the project as well as relation with external components are expected.

Anyone reading this section should have a good understanding of all the interacting modules.

Platform Maturity

Please fill out the centralized wiki page: Frankfurt Release Platform Maturity


  • API Incoming Dependencies

List the API this project is expecting from other projects.
Prior to Release Planning review, Team Leads must agreed on the date by which the API will be fully defined. The API Delivery date must not be later than the release API Freeze date.

Prior to the delivery date, it is a good practice to organize an API review with the API consumers.

To fill outHigh level description of the APIDate for which the API is reviewed and agreedTo fill outLink toward the detailed API description
  • API Outgoing Dependencies

API this project is delivering to other projects.

To fill outHigh level description of the APIDate for which the API is reviewed and agreedTo fill outLink toward the detailed API description
  • Third Party Products Dependencies

Third Party Products mean products that are mandatory to provide services for your components. Development of new functionality in third party product may or not be expected.
List the Third Party Products (OpenStack, ODL, RabbitMQ, ElasticSearch,Crystal Reports, ...).

To fill outTo fill outTo fill out

In case there are specific dependencies  (Centos 7 vs Ubuntu 16. Etc.) list them as well.

  • Testing and Integration Plans

Provide a description of the testing activities (unit test, functional test, automation,...) that will be performed by the team within the scope of this release.

Describe the plan to integrate and test the release deliverables within the overall ONAP system.
Confirm that resources have been allocated to perform such activities.

  • Gaps

This section is used to document a limitation on a functionality or platform support. We are currently aware of this limitation and it will be delivered in a future Release.
List identified release gaps (if any), and its impact.

To fill outTo fill out
  • Known Defects and Issues

Please refer to Frankfurt Defect Status


  • Risks

List the risks identified for this release along with the plan to prevent the risk to occur (mitigation) and the plan of action in the case the risk would materialized (contingency).

Please update any risk on the centralized wiki page - Frankfurt Risks

  • Resources

Fill out the Resources Committed to the Release centralized page.

  • Release Milestone

The milestones are defined at the Release Level and all the supporting project agreed to comply with these dates.

  • Team Internal Milestone

This section is optional and may be used to document internal milestones within a project team or multiple project teams. For instance, in the case the team has made agreement with other team to deliver some artifacts on a certain date that are not in the release milestone, it is erecommended to provide these agreements and dates in this section.

It is not expected to have a detailed project plan.

To fill outTo fill outTo fill out
  • Documentation, Training

Please update the following centralized wiki: Frankfurt Documentation

That includes

  • Team contributions to the specific document related to he project (Config guide, installation guide...).
  • Team contributions to the overall Release Documentation and training asset
  • High level list of documentation, training and tutorials necessary to understand the release capabilities, configuration and operation.
  • Documentation includes items such as:
    • Installation instructions
    • Configuration instructions
    • Developer guide
    • End User guide
    • Admin guide
    • ...

Note

The Documentation project will provide the Documentation Tool Chain to edit, configure, store and publish all Documentation asset.


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.













Information for the Jakarta Development

Architecture Subcommittee Review

The Architecture Subcommittee review was held on the 25th of January 2021, see  ONAPARC-725 - Getting issue details... STATUS and  POLICY-3853 - Getting issue details... STATUS .

Slides presented to ARCHCOM

The Architecture Subcommittee approved the Policy Framework Jakarta development as presented.

Actions:

  1. Prepare a wiki page describing the impact of removal of Cloudify support in policy-clamp, advising Control Loop owners of what actions they need to carry out.
  2. Inform all projects and Control Loop (use case) owners of removal of Cloudify support and refer them to the wiki page.


  • No labels