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

Compare with Current View Page History

« Previous Version 2 Next »

The page is intended to summarize all the requirements for Guilin Release.

These requirements have been prioritized by the TSC to realistically fit within the Guilin Release Timeline.

The Release Scope should be finalized during the M1 Release Planning milestone on TBD

TSC Prioritization (Ranking)

  • RANK #0  – Special GO - quick wins, fully covered by involved companies
  • RANK #1 – TSC Must Have – Mandatory for the release
  • RANK #2 – Continuity  - Items continued from previous releases
  • RANK #3 – PTL Go – items that PTLs is OK to include since team has bandwidth
  • RANK #4 – NO GO – items not approved for various reasons

Requirements Milestones Summary

See also Documenting Release Requirements in JIRA

Epic Link Fix For Versions (all)
Frankfurt Release Guilin Release Honolulu Release Istanbul Release Jakarta Release Kohn Release London Release Montreal Release New Delhi Release Istanbul Maintenance Release 1 Unscheduled T:
5G / OOF SON Enhancement 3 0 0 0 0 0 0 0 0 0 0 3
5G / ORAN & 3GPP Standards Harmonization 3 0 0 0 0 0 0 0 0 0 0 3
5G OOF SON use case requirements for Guilin release 0 1 0 0 0 0 0 0 0 0 0 1
5G Service Modeling in R8 0 0 15 0 0 0 0 0 0 0 2 17
5G SON use case enhancements for Istanbul release 0 0 0 13 0 0 0 0 0 0 0 13
5G SON use case enhancements for Jakarta release 0 0 0 0 14 0 0 0 0 0 0 14
5G SON use case enhancements for Kohn release 0 0 0 0 0 14 0 0 0 0 0 14
5G SON use case enhancements for London release 0 0 0 0 0 0 14 0 0 0 2 16
5G SON Usecase R8 0 0 16 0 0 0 0 0 0 0 2 18
A1 Adapter Extension & A1 Policy Management 0 1 0 0 0 0 0 0 0 0 0 1
A1 Policy Functions Extension - Istanbul 0 0 0 12 0 0 0 0 0 0 0 12
A1 Policy Functions Extension - Jakarta 0 0 0 0 12 0 0 0 0 0 0 12
A1 Policy Functions Extension - Kohn 0 0 1 1 1 13 0 0 0 1 0 13
A1 Policy Functions Extension - London 0 0 0 0 0 0 13 0 0 0 0 13
Add VSP Compliance and Verification Check feature Phase 2 3 0 0 0 0 0 0 0 0 0 0 3
Akraino Distributed Analytics use case 3 0 0 0 0 0 0 0 0 0 0 3
All Control Loop Policy Models should be TOSCA Compliant 3 0 0 0 0 0 0 0 0 0 0 3
APPC Ansible automation with VNF-C LCM support 3 0 0 0 0 0 0 0 0 0 0 3
Architecture - modelling alignment 7 0 0 0 0 0 0 0 0 0 0 7
ASD onboarding package IM / DM 0 0 0 0 12 0 0 0 0 0 0 12
Bulk PM / PM Data Control Extension 0 1 0 0 0 0 0 0 0 0 0 1
Bulk PM / PM Data Control Improvements 0 0 11 0 0 0 0 0 0 0 0 11
Bulk PM / PM Data Control Improvements 0 0 0 12 0 0 0 0 0 0 0 12
Bulk PM / PM Data Control Improvements 0 0 0 0 13 0 0 0 0 0 0 13
CCVPN-E-LINE Service over OTN NNI 3 0 0 0 0 0 0 0 0 0 0 3
Total Unique Issues: 196 22 248 184 189 107 187 1 1 1 84 1216
Showing 25 of 166 statistics.
Show more

View in Jira

Use Cases 

Release 6 (Guilin) proposed use cases and functional requirements

M1 Scorecard:

  • Green: Use Case will be fully implemented and tested
  • Yellow: Use Case will be partially implemented. It is possible to identify capabilities for this use case that can be tested (phasing approach).
  • Red: Use Case can not be partially delivered, min. requirements can not be met in order to define a testing strategy.

Architecture:

  • Pink - NO  GO
  • Purple - GO
  • Green - Considered OK not requiring architecture review
  • Black - Architecture not yet performed
Use Case

JIRA link (REQ)

One issue per requirement.

Instructions

Owner(s)TSC Ranking

M1

Scorecard

TSC M1 ApprovalLink(s) to HLD/LLD if anyDependency (from/to) another project(s)

T-Shirt Size (star)

Project's Impact: Test Only (TO), Code (C)

Committed (C)/ Partially Committed (P) or not (N) per impacted project


If Partially or not Committed, what are gaps/ project (people/FTEs; HLD/LLD; etc)Integration Lead

Company

Engagement

Notes


























































































(star) T-Shirt Size: Ballpark estimation for assessing the development/testing activities performed by the project team; not the integration team

  • XS - <4 Man/Weeks;
  • S - ~6 Man/Weeks;
  • M - ~8 Man/Weeks;
  • L - ~12 Man/Weeks;
  • XL - > 12 Man/Weeks.

Requirements

M1 Scorecard:

  • Green: The requirement will be fully implemented and tested
  • Yellow:  The requirement will be partially implemented. It is possible to identify capabilities for this functional requirement that can be tested (phasing approach).
  • Red: The requirement can not be partially delivered, min. requirements can not be met in order to define a testing strategy


Architecture:

  • Pink - NO  GO
  • Purple - GO
  • Green- Considered OK not requiring architecture review
  • Black - Architecture not yet performed
Requirement

JIRA link (REQ)

One issue per requirement.

Instructions

OwnerTSC RankingM1 ScorecardTSC M1 ApprovalLink(s) to HLD/LLD if anyDependency (from/to) another project(s)T-Shirt Size (XS, S, M, L, XL) (star)Project's Impact: Test Only (TO), Code (C), Documentation Only (DO)Committed (C)/Partially Committed (P) or not (N) per Impacted projectsIf Partially or not Committed, what are gaps/ project (people/FTEs; HLD/LLD; etc)Integration LeadCompany EngagementNotes












Marco Platania

Michael Hwang (MOD)

AT&T

Ericsson














Marco Platania

AT&T

Ericsson














Marco Platania

AT&T

Wipro

DCAE: Commitment based on Wipro












Project Pairwise Testing

Gervais-Martial Ngueko

Pamela Dragosh


AT&T

Ericsson














Abdelmuhaimen Seaudi

AT&T

Bell Canada

Ericsson 

Huawei

Orange














Morgan Richomme

Bell Canada,

AT&T,

Orange














Pamela Dragosh

AT&T, Intel












*Note: Not sure integration lead is needed for modeling

Borislav Glozman

Swaminathan Seetharaman

LIN MENG

CMCC

Amdocs

AT&T

Wiprc

Huawei














Reshmasree c 

AT&T

Wipro

IBM

RAN-Simulator will be submitted as part of Demo VNFs repository














Sandeep Shah

Nokia

AT&T

Will be a new component, presented at Architecture S/C.












N/A

Ericsson

Nokia














Eric Moore

Ericsson

Huawei














André Schmid

Ericsson












N/AEricsson

Main goals:

  • Support use of CDS for LCM actions
  • Improved PNF LCM support












Enbo Wang


Huawei














Enbo WangHuawei












Sandeep Shah (A1, O1)

AT&T

Nokia

Ericsson

DCAE: Impact for adopting new VES domain; Committed based on Nokia support.












N/A

AT&T

Nokia

Ericsson

Orange

No development.

Activity driven by Nokia and Ericsson is Use Case development.

The UCs and modeling are done in synch.













 user-3784d        EricssonDCAE: Committed based on Ericsson support












Krzysztof Kuzmicki

NokiaDCAE: Committed based on Nokia support












Damian Nowak

AT&T

Ericsson

Nokia

DCAE: No code impact on VES reg yaml updates












yaoguang wangHuawei












N/A (No integration or testing impact)

Nokia

AT&T

Modeling work only












Krzysztof Kuzmicki

NokiaDCAE: SDK Dmaap lib refactor; committed based on Nokia support












Mariusz SobuckiEricsson












Krzysztof Kuzmicki

Nokia

Ericsson

Integration will only be for VNF-SDK work, there is not full E2E POB/OB integration in R6.












N/A, producing a model file only, not a use case

AT&T

Ericsson

Huawei

Orange















AT&T












Marco Platania

AT&T

Nokia/Shanghai

Nokia/Poland

Tech Mahindra

Orange














@Lukasz Rajewski

Orange

AT&T














@Lukasz Rajewski

Orange

AT&T














Dominik Mizyn (for OJSI tickets)

AT&T

Samsung

IBM














Sireesh Chintamani (Overall Integration Lead)

Sunder Tattavarada  (for Angular upgrade)

Dominik Mizyn (for Springboot upgrade on "portal" repo)

Leimeng Shi (for reporting feature)

AT&T

Samsung

IBM














Andrew Fenner

Ericsson

Verizon

CMCC

Samsung

Nokia

Intel






























China Mobile,

Tencent,

Huawei

Merged with E2E Network Slicing use case












Swaminathan Seetharaman

Chuanyu Chen

Zhang Min

Wipro, 

AT&T,

Amdocs,

China Mobile, Huawei, Tencent,

ZTE

DCAE: Review pending; cannot be committed for Guilin as of 10/23


For EXT-API and Runtime DB, to check with the respective PTLs for possible resource commitments, accordingly will take a final call (not blocking for Guilin though)




























vFirewall:  

EdgeXFoundry

Akraino ICN Distributed Analytics




Intel

Aarna

Tech Mahindra














Lukasz Rajewski

Konrad Bańka

Samuli Silvius

Eric Multanen

Orange

Samsung

Intel














Marcus Williams

Intel














Manjunath Ranganathaiah


 Intel












Prabhu BalanVodafone












James Guistwite

Vodafone

iconectiv





































































































































































































































(star) T-Shirt Size: Ballpark estimation for assessing the development/testing activities performed by the project team; not the integration team

  • XS - <4 Man/Weeks;
  • S - ~6 Man/Weeks;
  • M - ~8 Man/Weeks;
  • L - ~12 Man/Weeks;
  • XL - > 12 Man/Weeks.

POC / Experimentation

POC definition

TypeRequirementOwnerLink(s) to HLD/LLD if anyDependency (from/to) another project(s)T-Shirt Size (XS, S, M, L, XL) (star)Project's Impact: Test Only (TO), Code (C)Company EngagementNotesM4 Status










(star)T-Shirt Size: Ballpark estimation for assessing the development/testing activities performed by the project team; not the integration team

  • XS - <4 Man/Weeks;
  • S - ~6 Man/Weeks;
  • M - ~8 Man/Weeks;
  • L - ~12 Man/Weeks;
  • XL - > 12 Man/Weeks.


  • No labels