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
Linda Horn
Agenda and Minutes
Agenda Item | Notes | Action Items |
---|
Open Gerrit Reviews | None |
|
Progress Update on Assigned Stories |
|
|
Guilin Release Planning | Release Not Assigned Guilin Stories |
|
Fallback IP Proposal | Fallback IP proposals - Some progress made on single FQDN w/ rotating IPs vs. primary/secondary
Heartbeat Duplication - Vijay confirmed that duplicate heartbeats would be de-duplicated by DCAE. If we maintain, primary and secondary endpoints this should be specified in the Event Listener spec (pending discussion above)
| - 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
|
3GPP Liaison Update | Magnus Buhrgard raised a concern that 3GGP required a stable link to the spec by 5/12 which precedes when the Frankfurt release docs would be created for ONAP. Presented 3 options: - Point 3GPP at the GitHub link instead: https://github.com/onap/vnfrqts-requirements/blob/frankfurt/docs/Chapter8/ves7_1spec.rst. This renders the content quite well, already has the Frankfurt branch created, and won’t be impacted by the overall Frankfurt docs release timeline. (my preference)
- 3GPP addresses the timing in their documentation. The content isn’t changing, but the link will. They could list both links.
- We’re moving to more “stand-alone” builds of the docs. So the documentation is available here for just VNFRQTS: https://onap-doc.readthedocs.io/projects/onap-vnfrqts-requirements/en/latest/index.html. Perhaps this could be branched earlier than the other projects. I don’t have any issue with that from my perspective since we have everything wrapped up for Frankfurt, but I don’t know the technical implications to the doc project
Still awaiting feedback from Magnus |
|
Open for Additional Topics |
|
|
Attachments
No files shared here yet.