#opnfv-meeting: #Dovetail Weekly Meeting

Meeting summary

1. 1. program officially changed name to OPNFV Verified Program - we can probably use the acronym OVP moving forward (earrage, 16:11:06)
   2. launch of program will occur in January 2018 with 4-5 of the beta participants (earrage, 16:12:22)
   3. Stephen had an issue with admin services needing to be made public, which is fine in lab setting. However, this is not suitable for deployment testing (earrage, 16:15:34)
   4. ACTION: add version field for in OVP portal for both OPNFV and commercial SUTs (earrage, 16:35:14)
   5. will use branch of stable/danube for OVP first release (earrage, 16:49:13)
   6. git release tag will be used with dovetail artifact versioning (earrage, 16:50:11)
   7. ACTION: identify HA test-cases we can potentially use in Euphrates OVP (earrage, 16:51:19)
   8. ACTION: how ONAP and Dovetail compliance programs work together or merge (earrage, 17:04:20)
   9. ACTION: continue audit of available Functest/Yardstick test cases available from Euphrates (earrage, 17:04:55)
   10. ACTION: start writing test specifications for use-case and forwarding performance test areas (earrage, 17:05:40)
   11. ACTION: ask C&C committee if Dovetail container can use versioning that aligns with external OVP versioning (earrage, 17:06:55)

Action items

1. add version field for in OVP portal for both OPNFV and commercial SUTs
2. identify HA test-cases we can potentially use in Euphrates OVP
3. how ONAP and Dovetail compliance programs work together or merge
4. continue audit of available Functest/Yardstick test cases available from Euphrates
5. start writing test specifications for use-case and forwarding performance test areas
6. ask C&C committee if Dovetail container can use versioning that aligns with external OVP versioning

People present (lines said)

1. earrage (14)
2. collabot (3)