Versions Compared

Old Version 29

changes.mady.by.user Stephen Terrill

Saved on

compared with

New Version 30

changes.mady.by.user ramki krishnan

Saved on

Key

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

...

Requirement/UseCase/...Status

Orchestration Scenarios

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

ArchCom approved

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

 LCM API Evolution

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

 ArchCom approved

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

  Edge Automation

Distributed Management Task Force - not ArchCom approved

  • Scope for Franfurt
    • What is accepted by ArchCom is :  Current orchestration mechanism of OOM and DCAE can co-exist to support Central and Edge use cases

      • Non-DCAE Application Orchestration (A&AI, Policy etc.)

        • Applicable to Central/Edge Deployment

      • DCAE Application Orchestration  (DCAE MS – Collectors/Analytics/Event proc)

        • Applicable to Central/Edge Deployment
    • Focus on current gaps/new features from ONAP Edge standpoint and build them using consistent design across ONAP 
      • Implementation may vary for OOM and DCAE deployed component
    • Defer Controller Alignment discussions beyond Frankfurt
    - "Extend Central K8S to register Edge Clouds"
    • Centrally manage k8s Edge Clouds (k8s-clusters)
    • Use Custom Resource Definition as Registry
    • Provide ability to extend CRD to contain metadata

      • -Location label 

      • -Edge type (ICN, AWS, Azure, etc.) 

      • -External IP 

      • -Namespaces, user for authorization

    • Edge Cloud Naming
      • Follow Cloud (AWS etc.) naming convention with additional operator name?
    Plan for Frankfurt & Beyond – Leverage Key Cloud Native Infra Orchestration Capabilities beyond K8S for ONAP management microservices
    • (Required discussion here is acceptance of difference in edge or not, or whether this is for edge and central).
    • Monitoring
      • Prometheus
    • Logging
      • Fluentd 
    •  Tracing
      • Jaeger 
    • Service MeshIstio/Envoy

Questions: still to be answered:

  • how to determine the location
  • Is it OK to use different services for the applications centrally and distributed.  Which applications are taking these up. 

3rd Party Operational Domain Controller

 

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

 ArchCom approved for current direction.

Note: Not full functionality in Frankfurt.  One open issue to resolve as to whether the external service needs to be wrapped in an ONAP service to have consistent orchestation approach (or not).

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

 Service Resolver

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

 Not Yet Archcom approved

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

 Model Driven ONAP

<< req >>

 Not Yet Archcom approved

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

 Orchestration of Contain Based VNFs

<<>>

 Frankfurt Release ??

 Applications on ONAP

<<?? >>

 Not Yet Archcom approved

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

 API-GW

<<>>

 There will not be a proposal for Frankfurt.

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

 Runtime DB

<< >>

 Status: need and concept OK by Archcom:

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

 5G / ORAN & 3GPP Standards Harmonization

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

 Status: Archcom approved

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

 ONAP CLI for VNF

<<??>>

 

Status: Note yet Archcom approved

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

 Slicing Evolution

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

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

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

 Not Archcom Approved

 Multidomain optical service

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

 Archcom Approved

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

 Integrate Acumos with DCAE

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

Self Service Control Loop

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

 Archcom approved
xNF licencing with ONAP

Archcom approved (principles) (licening server outside ONAP)

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

ETSI catalogue as a common service

Archom approved.  Part of ETSI-ONAP alignment requirements

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

CDS support of K8S

Archcom approved

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

Analytics (or VNF) at the edge using Akrono antaticis orchestrated by ONAP

Not Archcom approved

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

...