Alexis, During Amsterdam post-RC1 it was determined that the DCAE team had expectations for the Policy API that would not work in their architecture. It was too late for Policy to make change the API to accommodate them. Thus, any updates will not work. I don’t know what the workaround is for DCAE as Policy does work with updates.
It was agreed to fix it in Beijing: POLICY-434 and DCAEGEN2196 are tracking this. Regards, Pam Ps I can’t emphasize enough that help these teams (POLICY, DCAE, etc) need from other companies. These projects are not finished yet. In fact, DCAEGEN2 is brand new. There is still a lot of work to be done and I ask other companies within ONAP to help provide resources to harden, test and help fix issues. On 1/12/18, 3:13 PM, "[email protected] on behalf of Alexis de Talhouët" <[email protected] on behalf of [email protected]> wrote: Hi experts, I’m trying to understand how Policy works. Hence I tried to update the vFW policy (MS) to reduce the thresholds. My expectation was to see this being applied to the TCA application, but it seems it didn’t pick it up, tca_policy in CDAP remained un-changed. What should be the process to update a policy, and have this update probably reflected in TCA? Thanks, Alexis _______________________________________________ onap-discuss mailing list [email protected] https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.onap.org_mailman_listinfo_onap-2Ddiscuss&d=DwIGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=jwTiArcEj6aUX0HjV0M3dT12gUtk7rC07xpgpVZkS_4&m=HCMIEMWko9lPKkjqFMnASx5luljbnTjMLIClSlB0S2k&s=3jXal6Qt3V_-ZW1d6gBdbOelU5LhUqUydHHD6w7GuNI&e= _______________________________________________ onap-discuss mailing list [email protected] https://lists.onap.org/mailman/listinfo/onap-discuss
