VES Working Session | 2020-04-14

Owned by Trevor Lovett
Last updated: Apr 14, 2020 by damian.nowak
2 min read

Standard Antitrust Policy

Meetings of the ONAP Project involve participation by industry competitors,  and it is the intention of the Project to conduct all of its activities in accordance  with applicable antitrust and competition laws. It is therefore extremely  important that attendees adhere to meeting agendas, and be aware of and not  participate in any activities that are prohibited under applicable U.S. state,  federal or foreign antitrust and competition laws. Examples of types of actions  that are prohibited at ONAP Project meetings and in connection with ONAP  Project activities are described in the The Linux Foundation Antitrust Policy. If  you have questions about these matters, please contact your company  counsel or Andrew Updegrove, of the firm of Gesmer Updegrove LLP, which  provides legal counsel to The Linux Foundation. Linux Foundation Antitrust

Policy:  https://www.linuxfoundation.org/antitrust-policy

Attendees

@Trevor Lovett

Oskar Malm

Marge Hillis

@damian.nowak

Linda Horn

@Vijay Kumar

Agenda and Minutes

Agenda Item

Notes

Action Items

Agenda Item

Notes

Action Items

Open Gerrit Reviews

None



Progress Update on Assigned Stories





Guilin Release Planning 

Release Not Assigned

Guilin Stories



Open for Additional Topics

3GPP Alignment

  • Reviewed proposal from Damian to make the primary and fallback IPs requirements conditionally mandatory

  • Some concerns raised that this makes the decider of whether primary and fallback IPs are supported the sole decision of the NF provider which has implications to reliable delivery of events for the Operator

  • As it exists today, there is a disconnect between ONAP, O-RAN, and 3GPP on this item.

  • We agreed to jointly review the proposal offline and come back to discuss again



VES Fall Back to Primary (note: this is dependent on the outcome of the fallback

  • Damian - Can we send duplicate Heart Beats to primary and secondary simultaneious? 

    • Vijay - that should be fine with DCAE, but the NF would need to know not to buffer the failure on the non-active endpoint.

    • The de-duplication may need to be handled (it may already be cared for Vijay will confirm)

Do we need need to probe the primary listener endpoint when on the secondary to trigger a fallback?

  • DCAE expects the NF to use the primary endpoint when available.

    • The proposal is to use the Heart Beat to check the primary (when in failover mode) and if the Heart Beat

@Vijay Kumar - Confirm if any changes are required to handle duplication proposed in sending heart beats to primary and secondary simulataneously

Reminder: Next week's session will be cancelled due to the ONAP F2F








Attachments

  File Modified

Microsoft Powerpoint Presentation 3GPP_Harmonization_Pri_Sec_IP_address_20200414.pptx

Apr 14, 2020 by damian.nowak