Guangrong, Yes and no.
The vnf-id is important in the ONSET as Policy has to lock that VNF to ensure multiple requests are not sent to it at the same time. The service-instance-id (and other subsequent A&AI information) helps performance in that Policy does not need to look that information up to make the call to VFC. For ABATED, we are probably ok with NOT adding any A&AI details. As long as the controlLoopControlName and RequestID match the previous ONSET, then we can tie them together and finish the control loop. Thanks, Pam From: "[email protected]" <[email protected]> Date: Friday, October 20, 2017 at 9:12 AM To: "DRAGOSH, PAMELA L (PAM)" <[email protected]> Cc: "[email protected]" <[email protected]>, "[email protected]" <[email protected]> Subject: [policy] CL Event Filed for Abated Alarms Hi Pam, For the onset alarms, Policy requires the vnf-id and the service-instance-id in the CL event. How about the abated ones? Do we still have to fill in these two fields as well? I think the answer is negative because for the abated alarms, Policy does not use them to trigger any actions on VMs. They're just a certain kind of confirmation. Is that right? Regards, Guangrong
_______________________________________________ onap-discuss mailing list [email protected] https://lists.onap.org/mailman/listinfo/onap-discuss
