Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Priority

M1

Scorecard

TSC M1 ApprovalUse CaseOwnerProjects or functional requirements impacted for DublinLink(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 projectIf Partially or not Committed, then what are the gaps per impacted project (people/FTEs; HLD/LLD; etc)

Company

Engagement

NotesM4 Status

1-regression

3-enhancements

HPA Testing confirmed by INTELYvFW

Policy/(APPC)

HPA

vFirewall Use Case Upgrade
XS

All: Test Only except Policy

APPC(TO)

Policy: Committed


Policy: Committed

AT&T

1HPA HPA Testing confirmed by INTELYvDNSIntegration TeamHPA


All: Test OnlyN/A - part of regression testsN/A - part of regression tests


1Not part of Dublin scope - no regression testNA

Integration Team

HPA


All: Test OnlyN/A - part of regression testsN/A - part of regression tests


1Not part of Dublin scope - no regression testNA
Integration Team



All: Test OnlyN/A - part of regression testsN/A - part of regression tests


1

HPA Testing confirmed by INTEL 

YvCPE (Heat)Integration TeamHPA


All: Test OnlyN/A - part of regression testsN/A - part of regression tests


2

#Action

Davide/Lin to review and provide final feedback

Y Yes with Condition: Need final inputs from Davide/LinCCVPN Use Case (Dublin)   High priority:1, SD-WAN Multi-site to Multi-site service creation; 2, Service change: add or delete a site;3, close loop intelligent surveillance

SDC, SO, SDN-C,OOF,ExternalAPI, UUI, ESR,Modeling,MultiVIM/Cloud, VFC, Modeling, DCAE, Policy, Holmes,

Consistent ID of a cloud region

CCVPN Use Case (Dublin)
AAI: M

AAI: TO

DCAE: TO

ExtAPI: TO

Multi-VIM: Test support

Holmes: C

SDC: Partially committed based on Chinamobile/ZTE/Vodafone contribution

SO: Committed based on the contributions from CMCC, ZTE and VDF for the main flows

SDN-C/CCSDK : Committed based on contributions from Huawei and ZTE

VF-C: Committed

Modeling: Committed

Usecase-UI: Committed

Holmes: Committed based on Huawei and ZTE contribution

Multi-VIM/Cloud: Committed based on VMware contribution

Policy: Committed base on Huawei contribution

ExtAPI: Committed as long as a serviceOrder is created, either for service creation or modification with full service characteristics and values. ExtAPI can not read service characteristic and service state from AAI which does not expose those informations.

SDC: not enough resources

Dev/Test provided by Chinamobile, Vodafone, Huawei,

ZTE, WindRiver, VMWare, Intel, Lenovo, ChinaTelecom, Fujitsu



25G Use Case (Dublin)Y

5G: PNF

Pre-onboarding

Onboarding

SDC, VNFSDK, VNFRqmt (Docs)5G - PNF Pre-Onboarding & OnboardingBBS

SDC: C

VNFSDK: C

SDC: Committed based on Nokia/Ericsson contribution

VNFSDK: Committed


AT&T, Huawei, Ericsson, NokiaPNF POB/OB U/C is now in development, requirements and architecture stage with high corporate commitment.
25G Use Case (Dublin)Y5G: Bulk PMDCAE, DMaaP, VNFRqmt5G - Bulk PM (Casablanca carry-over items)5G: PM Dictionary

DCAE: C

DMaaP: C


DCAE: Committed based on Ericsson contribution

DMaaP: Committed


AT&T, Ericsson, NokiaBulk PM is in development with high corporate commitment.
25G Use Case (Dublin)Y5G: Config w/ NetConfOskar MalmSDC, (VID), SO, SDNC, CCSDK, VNFRQTS5G - Configuration with NETCONF

5G: PNF PnP

e2e automation


SDC: C

(VID)

SO: C

SDNC: C

CCSDK: C

SDNC: NETCONF/TLS support in controller committed from Ericsson

Additional development (SDC, SO, CCSDK) for PNF configuration UC is coordinated with CDS / e2e automation. See separate row for details.

PNF configuration testing: Ericsson

SO: (not a separate initiative uses E2E automation) assign/config building block


AT&T, EricssonNetConf is in development with high corporate commitment
25G Use Case (Dublin)Y5G: FM Meta PM DictionarySDC, VNFRqmt, VES Specification (Done)5G - FM Meta Data / 5G - PM Dictionary

5G: Bulk PM

5G: PNF OB


SDC: CSDC: Commit
AT&T, Ericsson, NokiaFMPM Dictionary is in development with high corporate commitment
25G Use Case (Dublin)Y Yes with Condition: Need to confirm testing resource to Yang Xu and what the Integration Team will be able to test5G: OOF & PCISDC, APP-C, DCAE, OOF, Policy, VNFRqmt5G - OOF and PCI (Casablanca carry-over items)

5G: PNF OB

Control Loop U/C


SDC: C

SDN-C: C

DCAE: C

OOF: C

Policy: C

SDC: NEED REVIEW

SDN-C: Commit

DCAE: Committed based on Wipro contribution

OOF: Commit

Policy: Committed based on Wipro contribution


AT&T, Wipro, Tech Mahindra

OOF/PCI Enhancements is in development with high corporate commitment

Dublin Release Requirements I added policy because my understanding from Dublin Release Requirements there are additions for 5G - OOF and PCI


25G Use Case (Dublin)Y Yes with Condition: Need to confirm testing resource to Yang Xu and what the Integration Team will be able to test5G: PNF Plug and Play & PNF Re-registrationBenjamin CheungSDC, Portal, VID, SO, A&AI, SDN-C, DCAE5G - PNF Plug and Play (Casablanca carry-over items)BBS

SDC: C

Port: C

VID: C

SO: C

A&AI: C

SDN-C: C

DCAE: C

AAF: C

Portal: Commit

VID: Reviewing

SO: Committed based on the contributions from Nokia (confirmed)

A&AI: Commit

CCSDK/SDN-C : Committed to Tosca ingest changes

DCAE: Committed based on the contributions from Nokia

AAF: Commit

AAI: assuming schema/model changes only contributed by community. Also depends on AAI modelling SME availability (Jan 30 James Forsyth has ok'ed A&AI commitment)

PORTAL: Targets only the top menu integration required for 5G use case functions from VID and SDC/AAI

VID: No enhancements dev

AT&T, Huawei, Ericsson, NokiaPNF PNP Enhancements is in development with high corporate commitment
25G Use Case (Dublin)Y5G: Network SlicingBorislav GlozmanSDC, Modeling Sub-committee5G - Slicing

SDC: C

Model: TO

SDC: Commit

Model: Commit


AT&T, Amdocs, EricssonNetwork Slicing has only modeling work that is being done in R4.
0
#action (Chaker): Add a risk concerning dependenecy with 5G Use Cases: Dublin RisksBBSDavid Perez CaparrosDCAE, ExternalAPI, Modeling, SDNC, SOBBS Broadband Service Use Case (Dublin)PRH - 5G Use Case

AAI:
(using 5G use case PNF discovery and re-registration: TO

DCAE: C

ExtAPI: C

SDC: TO

SO (using 5G use case PNF discovery and re-registration): TO

Policy: TO

CLAMP: TO

SDNC: C

Modeling: design


DCAE: Committed based on contribution from Huawei, TechM and Nokia

ExternalAPI: Committed

SO: 5G PNF Committed based on the contributions from Nokia /Huawei

SDNC: Committed based on contributions from BBS team

Modeling: contributions from Swisscom/Huawei/Nokia


AAI: assuming schema/model changes only contributed by community. Also depends on AAI modelling SME availability


Nokia, Swisscom, Huawei,
TechM



...

PriorityM1 ScorecardTSC M1 ApprovalFunctional RequirementOwnerProject ImpactedLink(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)Committed (C)/Partially Committed (P) or not (N) per Impacted projectsIf Partially or not Committed, then what are the gaps per impacted project (people/FTEs; HLD/LLD; etc)Company EngagementNotesM4 Status
2
Y Yes with Condition: Need to confirm testing resource to Yang Xu and what the Integration Team will be able to test

#Action - Bin/Yang to sync-up

Consistent ID of a Cloud Region (Dublin)Bin YangSDNC & APPC , VID, SO, UUI, VFC, OOFConsistent ID of a Cloud Region (Dublin)

APPC(TO, code already exists),

SDN-C: test support only

SO: Support testing effort, changes are likely in.

VFC:Committed

UUI:Committed

VID: Committed based on ATT resources


AT&T

China Mobile



2HPA Testing confirmed by INTEL

Y

Continuation of HPA (Dublin)Alexander VulVNFSDK, SDC, SO, VF-C, OOF, AAI, Policy, Multi-CloudContinuation of HPA (Dublin)SDC - Jira bugs open, OL001 compatibility requirements addressed.

AAI: TO

SO: Code Hardening, Expansion of use-case support, testing


AAI: assuming schema/model changes only contributed by community. Also depends on AAI modelling SME availability

Intel

ARM(???)

Development t resources from ARM are required to test HPA support on ARM hardware
2
YScaling Use Case (Dublin)Scott BlandfordMain focus on DCAE/CLAMP & PolicyScaling Use Case (Dublin)

DCAE: TO

CLAMP: Committed (Based on TechM resource commitment)

Policy: Committed (Based on TechM Resource Commitment)





0Testing confirmed by INTEL

Y

K8S based Cloud Region SupportMulti-Cloud, AAI, SDC, SOK8S based Cloud Region Support

AAI: TO

SDC & SO: Committed based on Intel/VMWare contribution

AAI: Partially committed

AAI: assuming schema/model changes only contributed by community. Also depends on AAI modelling SME availability

Intel, VMWare

3

POC for Dublin under Multi-Cloud umbrella

Testing confirmed by INTEL


Y

#action for Srini/Marco/Yang - identify another repo than demo

Distributed Analytics as a Service (Dublin Summary) - Edge Automation

Multi-Cloud, Demo


Distributed Analytics as a Service (Dublin Summary) - Edge Automation


MultiVIM/Cloud: partially committed based on VMware's contribution
VMware, Intel

2

SO Only

Testing confirmed by CM Team (AT&T)

Y with Condition: Limited to SO Scope

#action - Ajay/Seshu/Ryan to meet and provide low level requirements

Change Management Dublin Extensions - Flexible designer/orchestratorSO, VIDChange Management Dublin Extensions

SO (C),

VID (C)

SO: Committed (AT&T)

VID: pending final decision from Nokia (stretch goal)


AT&T

Nokia




2

Testing confirmed by AT&TYChange Management Dublin Extensions - Traffic Migration
APPC, OOFChange Management Dublin Extensions

APPC (C),

OOF (C),

A&AI (TO)

APPC: Committed (Orange)

OOF: Committed (Orange)


Orange



2Testing confirmed by AT&TYChange Management Dublin Extensions - Schedule OptimizationOOFChange Management Dublin Extensions

OOF (C),

Policy (TO)

OOF: Committed (AT&T)
AT&T

3Testing confirmed by AT&T

Y

Model Driven Control Loop Design (Close Loop sub-committee)DCAE, CLAMP, Policy

Model driven Control Loop Design





DCAE: AT&T Committed

CLAMP: Committed

Policy: Committed

AT&T commits to finding the required resources

AT&T, Nokia

3

SO Only

Testing confirmed by SO Team

Y with Condition: Limited to SO Scope


Modularity

SO, SDC, VFC, APPC, SDNC

https://wiki.onap.org/download/attachments/45293323/2018-12%20Virt%20F2F%20-%20%20Dublin%20Architecture%20Requirements-pa3.pptx?version=1&modificationDate=1544650581000&api=v2


https://jira.onap.org/browse/CCSDK-575




SDC: Not committed

APPC: Not committed

SO: Committed based on the code from R3

SDNC: Not committed

VFC: Partially committed

SDC: no resources, not enough info

APPC: no resources

SDNC: no resources

VFC: optimize DB microservice

CDS project will provide Resource assignment functionality




3

ETSI Alignment

SOOL003 plug-in to SO


Y

ETSI Alignment

SO plugint to support SOL003 to connect to an external VNFM

SO, SDC, AAI,https://wiki.onap.org/download/attachments/45293323/2018-12%20Virt%20F2F%20-%20%20Dublin%20Architecture%20Requirements-pa3.pptx?version=1&modificationDate=1544650581000&api=v2


SDC: Partially committed (based on Ericsson contribution)

SO: Committed (SOL003) based on contribution from Nokia and Ericsson

AAI: Not Committed

SDC: no resources

.AAI: no resources (detailed impact to be discussed) Action Byuong





 3

ETSI Alignment.

SOL005 plug-in to SO 

NETSI Alignment

SO plugin to support SOL005 to connect to an external NFVO

SO, SDC, AA, External API, VFC (underdiscussion)

https://wiki.onap.org/download/attachments/45293323/2018-12%20Virt%20F2F%20-%20%20Dublin%20Architecture%20Requirements-pa3.pptx?version=1&modificationDate=1544650581000&api=v2


     SO: SOL005 under dicusion with Verizon   
4Architecture did not approveNOSAM/PNF??????







4
NTOSCA Task Force???https://wiki.onap.org/download/attachments/45293323/2018-12%20Virt%20F2F%20-%20%20Dublin%20Architecture%20Requirements-pa3.pptx?version=1&modificationDate=1544650581000&api=v2


OOF: Policy Tosca model API and ONAP CLI integrationIntel


4
NAlloted Network Function??????







 3

Y

#Action- Need to confirm testing resource

Phase 1 - VSP Compliance Check

 SDC

CLI/VNFSDK

 VSP Compliance Check within SDC (Dublin)   SDC: Committed based on contribution from VF, Huawei and iconectiv

Vodafone, iconectiv, huawei

   

...

PriorityM1 Scorecard

TSC M1

Approval

Non Functional RequirementOwnerProject ImpactedLink(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)Committed (C)/Partially Committed (P) or not (N) per Impacted projectsIf Partially or not Committed, then what are the gaps per impacted project (people/FTEs; HLD/LLD; etc)Company EngagementNotesM4 Status
1

Y Yes with Condition: It does not include Ability to instantiate the entire service with API (VID)


Improve our E2E Process Automation

SO
SDC
CCSDK
OOM
Testsuite
Documentation

Jira
serverONAP JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyTSC-53

https://wiki.onap.org/download/attachments/48529726/ONAP-E2E-Automation-v3.pptx?api=v2

AAI
AAF
DMaaP
Policy

PNF use case (5G)
XL

Code:
SO
SDC
CCSDK
OOM
Testsuite

APPC (CDS)

TO:
AAI
DMaaP
Policy


SDC:
TechM (C)
IBM (C)

CCSDK:
ATT (C)
Bell   (C)
IBM (C)
Ericsson (C)
TechM (C)

SO:
Ericsson (C)
Bell (C)
ATT (P)

OOM:
Orange (P)
Bell (C)

Testsuite:
Orange (C)
Huawei (C)
Dutch T (C)

Documentation:
Orange (C)
Bell (C)
Dutch T (C)

AAI: TO


AT&T
Bell Canada
Ericsson
Huawei
IBM
Orange
Tech Mahindra



1

Container optimization : on –going (eg SDNC)

Component/memory optimization: Ongoing Assessment
  • Global optimization (e.g. shared DB) - stretch goal=shared PostgreSQL; shared MariaDB
  • Yes with Condition:

    Need to confirm testing resource to Yang Xu and what they will be able to test

    #Action-clarifications will be provided on PTL Call concerning Manageability/Footprint optimization

    1) have we the resources (dev/test)

    2) what are the impacts on the other requirements + backward compatibility & migration path from Casablanca Architecture to Dublin Architecture

    #action to split per item

    S3P - Footprint Optimization (Integration with Alpine)OOM + ALL

    https://wiki.onap.org/download/attachments/45293323/Dublin-Footprint-Optimizations.pdf?version=1&modificationDate=1544543600000&api=v2

    CIA Dublin Release Planning




    SDC: N

    CCSDK, CLAMP: Committed

    Multi-VIM/loud: committed

    Policy: committed

    DCAE: Not committed

    SDC: no resources


    DCAE: Resource constraint

    1

    phase 1

    manual

    magic word "run-helm-deploy" in queue at LF, Orange and Log team

    Move to POC





    Component/memory optimization: Ongoing Assessment

    Yes with Condition:

    Need to confirm testing resource to Yang Xu and what they will be able to test

    1) have we the resources (dev/test)

    2) what are the impacts on the other requirements + backward compatibility & migration path from Casablanca Architecture to Dublin Architecture

    split per item
    CI/CD


    OOM + ALL

    https://wiki.onap.org/download/attachments/45293323/Dublin-Footprint-Optimizations.pdf?version=1&modificationDate=1544543600000&api=v2

    CIA Dublin Release Planning




    SDC: N

    CCSDK, CLAMP: Committed

    Multi-VIM/loud: committed

    Policy: committed

    DCAE: Not committed

    SDC: no resources


    DCAE: Resource constraint





    Global optimization (e.g. shared DB) - stretch goal=shared PostgreSQL; shared MariaDB

    Yes with Condition:

    Need to confirm testing resource to Yang Xu and what they will be able to test

    1) have we the resources (dev/test)

    2) what are the impacts on the other requirements + backward compatibility & migration path from Casablanca Architecture to Dublin Architecture


    OOM + ALL

    https://wiki.onap.org/download/attachments/45293323/Dublin-Footprint-Optimizations.pdf?version=1&modificationDate=1544543600000&api=v2

    CIA Dublin Release Planning




    SDC: N

    CCSDK, CLAMP: Committed

    Multi-VIM/loud: committed

    Policy: committed

    DCAE: Not committed

    SDC: no resources


    DCAE: Resource constraint




    1Manual PH1

    Yes with Condition: Manual PH1



    CI/CD

    OOM + Integration

    (Infrastructure)


    Jira
    serverONAP JIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId425b2b0a-557c-3c0c-b515-579789cceedb
    keyTSC-25

    Integration

    Logging

    OOM

    + ALL (helm charts)

    L

    no except devops/scripts

    in

    oom/integration

    OOM:

    Linux Foundation (C)

    Orange (C)

    Bell (C)

    Amdocs (C)

    Logging:

    Bell (C)

    Amdocs (C)

    Integration:



    Amdocs

    Orange

    Linux Foundation

    Bell

    Huawei



    1
    YesDocument as You CodeALLTracked in JIRA - Label: Documentation







    1

    Yes with Conditions

    #Action - provide findings on the PTL call

    Security by DesignSecurity SubcommitteeALL

    https://wiki.onap.org/download/attachments/45293323/2018-12%20Virt%20F2F%20-%20%20Dublin%20Security%20-%20Requirements-pa2.pptx?version=1&modificationDate=1544453068000&api=v2









    1

    Yes

    #Action on TSC

    Modeling M3 Checklist enhancementModeling SubcommitteeSO, SDC, VFC, APPC, VNFSDKProposed M3 Checklist modeling updates discussion


    VFC: Committed



    1

    #Action - Need to be discussed on the PTL Call


    Phasing approach:

    #0 conf change only

    #1 upgrade with no data schema change

    #2 upgrade with data schema change

    S3P - Provide Upgrade CapabilitiesOOM + ALLDublin Release Platform Maturity





    In Dublin will establish plan & basis for platform release upgrade strategy to be implemented in following release.
    1
    YMove Helm Chart (OOM) at project levelOOM + ALL



    During the PTL meeting on 12/17 -it was agreed that

    No enforcement to make it happen for all project in Dublin release, but expectation to to completed within El Alto release. This could potentially be a S3P items.

    6 projects have been identified for trial: Logging, Policy, APPC, CLAMP, AAI and ONAP CLI




    1
    YoParent Integration to fix vulnerabilities

    Security Subcommittee

    Yang Xu

    Integration +ALL


    Modeling: TO

    AAI, DCAE, DMaaP, Holmes, Logging, Modeling, MSB, Multi-Cloud, ONAP CLI, UUI, Policy, Portal, SO, VFC, VNFSDK, AAF,CLAMP, MUSIC: Already Integrated

    ExtApi, VID: Committed

    SDC: Not Committed

    CCSDK/SDNC, OOM, APPC, OOM: No

    CCSDK/SDNC, APPC: dependency on ODL

    OOF (HAS, OSDF): python, not Java

    SDC: No resource

    OOM: No java code





    1
    Yes with Conditions: to be discussed on PTL call on 2/4CIST running OOMPTLsNeed to assess
    Infrastructure capacity






    2See Dublin Release Platform Maturity

    Yes with Conditions:

    #Action - Need to be discussed on the PTL Call

    S3P- Geo-RedundancyOOM/MUSIC Integration to ONAP ComponentsDublin Release Platform Maturity







    2

    Yes with Conditions:

    Need to confirm testing resource to Yang Xu and what they will be able to test by 2/4 otherwise this item will be descoped

    SOL 004 (VNF Package Security)Samuli KuuselaSDC, VNFSDK

    SDC:

    Jira
    serverONAP JIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId425b2b0a-557c-3c0c-b515-579789cceedb
    keySDC-1980
    Jira is for PNF package.

    VNFSDK:
    Partially implemented in Casablanca
    .

    Jira
    serverONAP JIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId425b2b0a-557c-3c0c-b515-579789cceedb
    keyVNFSDK-342




    SDC: Partially committed (based on Ericsson contribution)



    3

    Yes with Conditions:

    #action - Stephen/SECCOM to follow-up on testing

    xNF communication security enhancementsAAF, DCAE, ControllersSlide presented on PTL Call (1/14/2019)


    DCAE - Committed based on Nokia's contribution


    Controller part (SDNC) committed from Ericsson, see 5G UC





    4
    NoS3P - Service Mesh (ISTIO)Security & Architecture SubcommitteesALL except MSB or performed at K8S level (OOM); Poc of ISTIO plug-in to AAF not resourcedhttps://wiki.onap.org/download/attachments/45293323/2018-12%20Virt%20F2F%20-%20%20Dublin%20Architecture%20Requirements-pa3.pptx?version=1&modificationDate=1544650581000&api=v2







    4
    NoS3P Manageability - Logging Capabilities

    see yellow/red in

    in progress

    log, aaf cli, consul, contrib, dcae, dmaap, nbi, oof, sdnc, so, uui, vid, vnfsdk, vvp

    good

    aai, appc, clamp, esr, multicloud, policy, pomba, portal, sdc, vfc


    Library: In progress portal/sdk and possible so library adjustment

    Jira
    serverONAP JIRA
    serverId425b2b0a-557c-3c0c-b515-579789cceedb
    keyPORTAL-348

    Infrastructure: dmaap is adding containers, need to work with other teams in red

    Jira
    serverONAP JIRA
    serverId425b2b0a-557c-3c0c-b515-579789cceedb
    keyDMAAP-853

    as part of overall

    Jira
    serverONAP JIRA
    serverId425b2b0a-557c-3c0c-b515-579789cceedb
    keyLOG-487

    Log

    OOM

    Portal

    SO

    AAI


    OOM (c)

    LOG (c)

    Portal (c)

    SO (c)

    AAI (c)

    Multicloud(c)

    LOG/POMBA

    OOM



    Amdocs

    AT&T

    Bell

    Hauwei

    Intel




    3

    Yes with Conditions:

    Need to confirm testing resource to Yang Xu and what they will be able to test - to be concluded on 2/4

    Locale/Internationalization language supportPortal, UsecaseUIInternationalization language supportPortal, UsecaseUIL

    Code:
    PORTAL, UsecaseUI

    UsecaseUI (C))



    3
    Yes with Condition: Stretch Goal3Angular 6 Upgrade of ONAP Portal and SDKPortal

    Jira
    serverONAP JIRA
    serverId425b2b0a-557c-3c0c-b515-579789cceedb
    keyPORTAL-330

    PortalXL

    Code:

    PORTAL

    TO:

    Policy, VID

    PORTAL (C)



    ...

    IBM, AT&T, VMware (Architecture/Modelling), Intel (Architecture),

    TypeRequirementOwnerProject ImpactedLink(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
    Functional Requirement

    Self Serve Control Loop (Closed Loop Subcommittee)

    DCAE, Policy, SDC


    Model driven Control Loop Design

    This is a stretch goal for Dublin.  We are still trying to align resources so that this can be accomplished this release



    DCAE: Stretch Goal

    Policy: Stretch Goal

    SDC: Stretch Goal

    AT&T

    Functional RequirementFine-Grained Placement Service (F-GPS)Multi-Cloud, OOF

    https://wiki.onap.org/download/attachments/45293323/2018-12%20Virt%20F2F%20-%20%20Dublin%20Architecture%20Requirements-pa3.pptx?version=1&modificationDate=1544650581000&api=v2

    F-GPS (Dublin Summary)

    OOF: Committed

    MultiVIM/Cloud: Committed

    End-to-end Use Case Integration: Stretch Goal (due to several workflow changes)

    Sub-ProjectDataLakeGuobiao MoDCAEChina Mobile, Huawei, ZTE, VMware

    1544650581000&api=v2

    F-GPS (Dublin Summary)


    OOF: Committed

    MultiVIM/Cloud: Committed

    End-to-end Use Case Integration: Stretch Goal (due to several workflow changes)

    IBM, AT&T, VMware (Architecture/Modelling), Intel (Architecture),




    Sub-ProjectDataLakeGuobiao MoDCAE



    China Mobile, Huawei, ZTE, VMware

    Sub-ProjectComposable Disaggregrated Infrastructure (CDI)@Alex VulMulti-Cloud



    Intel

    Non-Functional Requirement

    CI/CD

    Magic word "run-helm-deploy" in queue at LF, Orange and Log team

    Move to POC

    OOM + Integration

    (Infrastructure)





    Amdocs

    Orange

    Linux Foundation

    Bell

    Huawei

    Sub-ProjectComposable Disaggregrated Infrastructure (CDI)@Alex VulMulti-CloudIntel



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

    ...