Policy doesn’t execute closed loop for each received event. For a given event, Policy runs one closed loop every X minutes, this is why the VNF is locked. At the expiration of the timeout (lock), the closed loop is executed again. I can’t remember where locks are kept, Jorge can help with that. Guard policies are pushed by the user from CLAMP typically (unless you call Policy API directly), so they do what the user tells them to do. Note however that for scale out, Policy doesn’t call APPC, it calls SO (which later on calls APPC for VNF health check and reconfiguration). I’m not sure whether your configuration reflects this. You shouldn’t expect Policy to publish in APPC-LCM-READ.
Marco From: Ferrero Marco Angelo <[email protected]> Date: Monday, September 2, 2019 at 11:13 AM To: "[email protected]" <[email protected]>, "PLATANIA, MARCO (MARCO)" <[email protected]>, "PLATANIA, MARCO (MARCO)" <[email protected]>, "HERNANDEZ-HERRERO, JORGE" <[email protected]> Cc: "Malinconico Aniello Paolo <[email protected]> ([email protected])" <[email protected]>, D'Alessandro Alessandro Gerardo <[email protected]>, Signorelli Marco <[email protected]> Subject: VF Module Scale Out Use Case - questions about closed-loop chain. Hi everybody, We are testing the VF Module Scale Out use case. Our vLB correctly sends data to the VES Collector and it correctly publishes data on DMaaP topic unauthenticated.VES_MEASUREMENT_OUTPUT. TCA correctly read data from this topic and, as the threshold is violated, correctly publishes data on DMAAP topic unauthenticated.DCAE_CL_OUTPUT Policy Drools read data from this topic and applies frequency guard but it does not propagate the event even if it seems send evets to DMaap topic POLICY-CL-MGT Who consumes messages from this topic (POLICY-CL-MGT) and who writes to topic APPC-LCM-READ in order to propagate the commands to the APPC ? Accessing to network.log file of policy drools we have found the following messages : [2019-08-31T00:37:54.089+00:00|Session org.onap.policy.drools-applications.controlloop.common:controller-usecases:1.4.2:usecases][OUT| { "AAI": { "vserver.prov-status": "ACTIVE", "vserver.resource-version": "1566468980498", "vserver.is-closed-loop-disabled": "false", "vserver.vserver-name2": "RegionOne_ONAP-NF_20190821T135252709Z_vlb_001", "vserver.vserver-id": "ccadfb9d-0386-43d5-b007-887ec9ce3fcc", "vserver.vserver-selflink": "http://163.162.95.137:8774/v2.1/a9d84b4e2c1e47bfaa4d26d2d894c9c2/servers/ccadfb9d-0386-43d5-b007-887e<https://urldefense.proofpoint.com/v2/url?u=http-3A__163.162.95.137-3A8774_v2.1_a9d84b4e2c1e47bfaa4d26d2d894c9c2_servers_ccadfb9d-2D0386-2D43d5-2Db007-2D887e&d=DwQFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0&m=9F0hi2lvf516P4W9z1pFsP2SQyQELSaXXduf8XCZUR0&s=a66daKjKvJGjrCVBjQAagtnJGP6GkDySc0AOFhJkPRU&e=> "vserver.in-maint": "false", "vserver.vserver-name": "RegionOne_ONAP-NF_20190821T135252709Z_vlb_001" }, "closedLoopAlarmStart": 1567211854626801, "closedLoopControlName": "LOOP_vLoadBalancer_20190821_v1_0_vLoadBalancer_201908210_k8s-tca-clamp-policy", "version": "1.0.2", "requestId": "2d530ae5-cdc5-41a3-83fe-0166431d26e7", "closedLoopEventClient": "DCAE_INSTANCE_ID.dcae-tca", "targetType": "VM", "target": "vserver.vserver-name", "from": "policy:usecases", "policyScope": "onap.policies.controlloop.Operational:1.0.0", "policyName": "OPERATIONAL_vLoadBalancer_20190821_v1_0_vLoadBalancer_201908210_k8s-tca-clamp-policy.EVENT.MANAGER", "policyVersion": "1.0.0", "notification": "REJECTED", "message": "The target RegionOne_ONAP-NF_20190821T135252709Z_vlb_001 is already locked", "notificationTime": "2019-08-31 00:37:54.089000+00:00", "history": [] } [2019-08-31T00:38:08.124+00:00|qtp1534754611-39]10.42.10.195 - - [31/Aug/2019:00:38:08 +0000] "GET /healthcheck HTTP/1.1" 200 102 root@cp-1:~/oom/kubernetes# 00|qtp1534754611-35]10.42.10.195 - - [31/Aug/2019:00:38:23 +0000] "GET /healthcheck HTTP/1.1" 200 102 It seems that we vserver entry in the AAI (vserver relative to the vLB) is locked ? Why it is locked ? Who locks it ? Where are kept the locks ? I have also accessed the policy db root@dev-policy-policydb-868884d57f-g4h9g:/# mysql -uroot -psecret Welcome to the MariaDB monitor. Commands end with ; or \g. Your MariaDB connection id is 776820 Server version: 10.2.14-MariaDB-10.2.14+maria~jessie mariadb.org binary distribution Copyright (c) 2000, 2018, Oracle, MariaDB Corporation Ab and others. Type 'help;' or '\h' for help. Type '\c' to clear the current input statement. MariaDB [(none)]> show databases; +---------------------+ | Database | +---------------------+ | information_schema | | log | | migration | | mysql | | onap_sdk | | operationshistory | | operationshistory10 | | performance_schema | | policyadmin | | pooling | | support | +---------------------+ 11 rows in set (0.02 sec) And I have checked the operationhistory schema : I made the resume query MariaDB [operationshistory]> select count(*),message from operationshistory group by message; +----------+---------------------------+ | count(*) | message | +----------+---------------------------+ | 1474 | 999 Failed | | 11411 | Operation denied by Guard | +----------+---------------------------+ 2 rows in set (0.03 sec) And I always got ‘999 Failed’ every time the guard let it me execute the policy. Who send this code ? Where I can get the log of the policy executor that generate this message ? Thank you in advance for your precious help, Marco Ferrero ------------------------------------------------------------------ TIM Marco Angelo Ferrero Mobile & Fixed Innovation IP, Transport & Core Innovation TIM S.p.A. Via G. Reiss Romoli, 274 – 10148 TORINO +39 011 2286739 +39 331 6001354 [https://img.tim.it:443/sdr/banner-mail-dipe.jpg]<https://urldefense.proofpoint.com/v2/url?u=https-3A__on.tim.it_banner-2Dmail-2Ddip&d=DwMFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0&m=9F0hi2lvf516P4W9z1pFsP2SQyQELSaXXduf8XCZUR0&s=4U5QxZWZQCB1NrAZBIB5Jfnzl7eOlV1Oc2DkNq1QtUs&e=> Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. Rispetta l'ambiente. Non stampare questa mail se non è necessario. -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#18783): https://lists.onap.org/g/onap-discuss/message/18783 Mute This Topic: https://lists.onap.org/mt/33113086/21656 Group Owner: [email protected] Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
