VES Working Session | 2020-04-28

Owned by Trevor Lovett
Apr 28, 2020
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

@Vijay Kumar

Oskar Malm

Marge Hillis



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

Considerations for items moving from VES Event spec to VNFRQTS

  • I will make any new mandatory requirements only applicable to VES 7.1 and greater clients

How long will we support 5.4.1?

  • No timeline to remove it. Big embedded base of logic based on 5.4.1 so not likely to be removed any time soon

Fallback IP proposals

  • The following is the general feedback shared, and no decisions were made due to the lack of attendees.  We will bring this up again on a future session.

  • Concern remains that the decision as proposed is solely with the NF (3GPP vs. ONAP)

  • ONAP model for resilient delivery of messages is still based on a 2 endpoint solution

  • Trevor Lovett's take is that removal of mandatory requirements for 2 IPs would take an alternate architecture or solution from DCAE.  This would need to be addressed between 3GPP and DCAE directly vs. in the ONAP requirements

  • Suggestion is to make the 3GPP model an additional, optional model for configuration and deployment, but not remove the mandatory configuration requirements.

  • Trevor will propose some requirement text for review

Notification of 3GPP Liasion

  • @Trevor Lovett completed this see attached email

DCAE Frankfurt Documentation Updated (Please review and provide feedback by the next meeting)_

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

@Trevor Lovett Provide feedback on VES fallback IPs
@Trevor Lovett Draft alternate proposal of language for fallback IPs




Attachments

  File Modified

File VES Updates for the Frankfurt Release 3GPP Liason Agreement.msg

Apr 28, 2020 by Trevor Lovett