Not sure why it the mail below did not reflect on the onap-discuss mailing list.
Re-posting here. Regards Aayush On 9 September 2017 at 09:04:14 IST, Aayush Bhatnagar <aayush.bhatna...@ril.com> wrote: There is one architectural doubt on Policy Enforcement, which is explained below - When we enforce a policy, we may have to define an associated hysteresis along with it. Consider the case for "auto scaling policies" for a VNF or even its VNF Component (VNF-C). The auto scaling policy may be based on CPU consumption thresholds, for example - A) Auto scale the VNF if the CPU consumption spikes and exceeds 70%, three times in any given hour (busy hour). B) Auto scale the VNF, if the CPU consumption exceeds 70% three times in a given 24 hour period (1 day). , and so on. Hence, unless the above hysteresis evaluates to "true", the policy for auto-scaling the VNF should not be enforced. In the current architecture, even though the policy rules are distributed to different ONAP sub-systems for enforcement - how do we plan to handle the "gating criteria" (hysteresis) for policies. Is it expected for individual ONAP subsystems to implement the gating criteria evaluation repeatedly for such cases? There is an element of data mining and time-series analytics involved here to evaluate the gating criteria. Or will this be centralised (Analytics?) and all ONAP subsystems are required to "consult" the central gating criteria before actually enforcing policies which need hysteresis? Clarifications will be helpful. Regards Aayush "Confidentiality Warning: This message and any attachments are intended only for the use of the intended recipient(s). are confidential and may be privileged. If you are not the intended recipient. you are hereby notified that any review. re-transmission. conversion to hard copy. copying. circulation or other use of this message and any attachments is strictly prohibited. If you are not the intended recipient. please notify the sender immediately by return email. and delete this message and any attachments from your system. Virus Warning: Although the company has taken reasonable precautions to ensure no viruses are present in this email. The company cannot accept responsibility for any loss or damage arising from the use of this email or attachment."
_______________________________________________ ONAP-TSC mailing list ONAP-TSC@lists.onap.org https://lists.onap.org/mailman/listinfo/onap-tsc
