Versions Compared

Old Version 26

changes.mady.by.user Stephen terrill

Saved on

compared with

New Version 27

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 Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyREQ-101

ArchCom approved

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyONAPARC-320

 LCM API Evolution

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyREQ-92

 ArchCom approved

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
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
  • 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 Mesh
      • Istio/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.

Distributed Analytics as a Service - has not been presented, not Achcom approved

Scope for Frankfurt 
  • Performance features 
    • Security (ingress, egress, inter-component, RBAC for each package)
  • Way to customize  packages
  • Deployment using Multi-Cluster scheduler
  • GUI/CLI based configuration of stack
  • Monitoring of stacks - Ensure that each stack component has prometheus target.
  • Some real AI based analytics
    • Link: Distributed Analytics as a Service 

    3rd Party Operational Domain Controller

     

    Jira Legacy
    serverSystem Jira
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    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 Legacy
    serverSystem Jira
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyONAPARC-509

     Service Resolver

    Jira Legacy
    serverSystem Jira
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyREQ-13

     Not Yet Archcom approved

    Jira Legacy
    serverSystem Jira
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyONAPARC-509

     Model Driven ONAP

    << req >>

     Not Yet Archcom approved

    Jira Legacy
    serverSystem Jira
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyONAPARC-436

     Orchestration of Contain Based VNFs

    <<>>

    		 Frankfurt Release ??

     Applications on ONAP

    <<?? >>

     Not Yet Archcom approved

    Jira Legacy
    serverSystem Jira
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyONAPARC-500

     API-GW

    <<>>

     There will not be a proposal for Frankfurt.

    Jira Legacy
    serverSystem Jira
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyONAPARC-494

     Runtime DB

    << >>

     Status: need and concept OK by Archcom:

    Jira Legacy
    serverSystem Jira
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyONAPARC-514

     5G / ORAN & 3GPP Standards Harmonization

    Jira Legacy
    serverSystem Jira
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyREQ-38

     Status: Archcom approved

    Jira Legacy
    serverSystem Jira
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyONAPARC-516

     ONAP CLI for VNF

    <<??>>

     

    Status: Note yet Archcom approved

    Jira Legacy
    serverSystem Jira
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyONAPARC-478

     Slicing Evolution

    Jira Legacy
    serverSystem Jira
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyREQ-60

    Jira Legacy
    serverSystem Jira
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyREQ-158

    Jira Legacy
    serverSystem Jira
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyREQ-159

    		 Not Archcom Approved

     Multidomain optical service

    Jira Legacy
    serverSystem Jira
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyREQ-37

    		 Not Archcom Approved (no conceptual issue identified, only due diligence required for CCVPN alignent).

     Integrate Acumos with DCAE

    Jira Legacy
    serverSystem Jira
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyREQ-166

    Self Service Control Loop

    Jira Legacy
    serverSystem Jira
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyREQ-9

    		 Archcom approved
    xNF licencing with ONAP

    Archcom approved (principles)

    Jira Legacy
    serverSystem Jira
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyONAPARC-520

    ...