Versions Compared

Version Old Version 5 New Version 6
Changes made by

Vijay Kumar

Vijay Kumar

Saved on

Key

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

...


 Time (est) Topics Requester/Assignee Notes/Links


Notice: Meeting time change
New meeting time effective from 11/07/2019 (until 03/05/2020) 

Thursday, 10.30 – 11.30 AM EST/3.30 -4.30 PM UTC

1
Project Status (El-Alto)

Vijay Kumar

START RECORDING

PARTICIPANT LIST

2
Project Status

Vijay Kumar

  •  Review Action Items from previous week


TSC Prioritization: [Onap-release] Frankfurt - ONAP TSC Prioritization.pdf  (RANK#0 and RANK#1 should be completed before Functional/Usecase work can be addressed)

3
E2E Network slice impact

 LIN MENG Swaminathan Seetharaman

Guobiao Mo

REQ-146: Usecase review/ DCAE impact

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyDCAEGEN2-1878

Issues discussed during review needing further review

  •  E2E Network slice per latest prioritization/update under Frankfurt Release Requirements has no DCAE impact identified. ARC approved only new adapter in SO and External API
  •  Flow proposed on 10/31 has couple of issues.
    • Following components should be outside DCAE scope
      1. DataLake (elastic search)
      2. Kpi collector (for getting proprietary fileready notification); this should be bundled within VNF/simulator
      3. Kpi MS (providing api to ExternalUI) doesn't fit under DCAE function either
    • VES Adapter/collector does not subscribe from Dmaap
    • Kpi MS1 function can be replaced by DL adapter subscribing into DRdirectly.

The new flow/proposal will require signoff again from ARC if TSC confirms DCAE impact for this UC


4
VES spec 7.1.1 updates

 alok411

10/31 - Deferred for next week

Review planned updates for VES 7.1.1

AttServiceSpecification-VesEventListener-v7.1.1 - AG1 DRAFT.docx

VES Event Registration Specification 3.2.1 Draft.docx

  • Impacts VES Collector to use new VES schema file (CommonEventFormat_30.1.1.json)

Provide any feedback by 10/24 to alok411. Targeting formalize/release of VES updates by EOM; will be work with VNFSDK and Modelleing for release.

 5
VES 8.0 updates review

 alok411

marge.hillis

10/31 - Deferred for next week

Review 8.0 domain updates  (

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyDCAEGEN2-1769

  • Review mandatory field list if should be classified as optional to consider other similar stream
  • cmNotify has consensus; fault (update required to support fault3gpp) being worked.
  •  Combine both updates and publish 8.0 before M3

ONAP CM NOTIFICATIONS October 24.pptx

6
CBS TLS in SDKPiotr Wielebski

10/31 - Deferred for next week

ticket: https://gerrit.onap.org/r/#/c/dcaegen2/services/sdk/+/94266/

Confluence: TLS support for CBS - Migration Plan

K8s plugin updates (DCAEGEN2-1550)

  1. Cloudify deployments of service components should include following environments


"Library Enhancement (CBS java sdk - DCAEGEN2-1552, CBS python util - DCAEGEN2-1551)

  1. Verify if the new environment setting for TLS (below) added by K8s plugin is visible within POD.
    • CONFIG_BINDING_SERVICE=<cbs_k8s_service_name>
    • DCAE_CA_CERTPATH=<path>
  2. If DCAE_CA_CERTPATH is defined, use the cacert for establishing secure end-point to interface with CBS (port 10443)
    1. An optional CBS_CONFIG_URL will be exposed providing the exact URL to be used for configuration retrieval. Application/Libraries can use this URL directly instead of constructing URL from HOSTNAME (which refers to ServiceComponentName) and CONFIG_BINDING_SERVICE env's.  By default, this URL will use HTTPS CBS interface
  3. If TLS env is undefined, use R4 service name and port (10000) to interface with CBS (HTTP)

Note: Libraries should stop using Consul service discovery to find CBS; instead rely on kubernetes DNS name (exposed via env CONFIG_BINDING_SERVICE) and port 10000 for HTTP and 10443 for HTTPS. Service registration on Consul will not be done for CBS TLS service"


Current implementation relies on trust.jks being available. Following options to be explored

  • Option 1: Work/address issue around using cacert.pem for CBS connection (original proposal)
  • Option 2: Enabled use_tls: true for all DCAE MS deployment (in blueprint) to ensure all AAF cert/trust and distributed (regardless of the MS/component being setup as server or not)
  • Option 3: Modify K8s plugin to include trust.jks distribution by default along with cacert.pem

Note: Current SDK change https://gerrit.onap.org/r/#/c/dcaegen2/services/sdk/+/94266/ relies on Option#2

Option3 preferred; Nokia team will analyze the impact for k8s plugin updates.

 7
Resource commitment for Frankfurt support

 Vijay Kumar

Contributors  to review and update contacts and jira/component focus under Resources 
 8
 Java 11 Migration

 Vijay Kumar

Identify components to be targeted for Java11 migration/support in Frankfurt


El-Alto Demo

 Vijay Kumar

DEMOS - R5 El-Alto Demos

...