2020-03-18 Policy Bi-Weekly Meeting (shared with CLAMP)
AGENDA
Duration | Agenda Item | Requested by | Notes / Links |
|---|---|---|---|
START RECORDING | |||
| CLAMP Update - question for Policy team regarding treating Policy Types with different versions. | CLAMP Team |
|
| Policy Team |
| |
|
|
|
|
ATTENDEES
@Pamela Dragosh @Jorge Hernandez @Liam Fallon @James Hahn @Aditya Puthuparambil @Former user (Deleted) @Peyton Puckett @Pramod Jamkhedkar @Sebastien Determe @vidyashree.rama @Ram Krishna Verma
NOTES
CLAMP Update:
Doing pairwise testing in Policy Lab - lots of fixes, mainly with Policy synchronization controller (in charge of synch of policies with policy engine).
Question: What if we have multiple version of a specific Policy Type Model? Cannot have multiple keys due to TOSCA is a map.
@Liam Fallon - will get back all the latest policy versions in Frankfurt (due to ambiguity in TOSCA specification). Will address in Guilen how to get specific versions.
@Sebastien Determe - issue is if v1.0.0 is used, added into loop (created and deployed)
Need to describe workarounds for folks that update Policy Type's - TOSCA specification is unclear/un-implementable. Recommend clients to bake versioning into the name of the policy type.
@Jorge Hernandez - found in the lab that you could not retrieve old version via API. He will create a bug for @Chenfei Gao to investigate.
@vidyashree.rama - Seb is still working on sending string - will work with your code and get back to you if has an issue.
pairwise testing with CDS - per Seb should be able to work as before just take the latest code. Will send mail on how to add it.
Need to test the submit and deploy - Xue will do this week.
Policy scrum - see above wiki
RECORDING: