+Jorge from the Policy team. Perhaps he can take a look. Pam
From: <[email protected]> on behalf of Alexis de Talhouët <[email protected]> Date: Thursday, December 7, 2017 at 10:09 AM To: "PLATANIA, MARCO (MARCO)" <[email protected]>, "[email protected]" <[email protected]> Subject: [onap-discuss] [Amsterdam][OOM] vFW close-loop testing Hello Marco, team, I’ve been following the close-loop video https://wiki.onap.org/display/DW/Running+the+ONAP+Demos?preview=/1015891/16010290/vFW_closed_loop.mp4<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_display_DW_Running-2Bthe-2BONAP-2BDemos-3Fpreview-3D_1015891_16010290_vFW-5Fclosed-5Floop.mp4&d=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=jwTiArcEj6aUX0HjV0M3dT12gUtk7rC07xpgpVZkS_4&m=eGdp3ha1Dvenrua6ZSDOjXaZ7Q2pW83DPaI5PU-eIIs&s=MgFmqh-hgsbZkP6-8Rdj1E_-qrczm96BKpPlXsAF7P8&e=> to fix OOM. I’m currently at the stage where I’m updating the vFW Operation Policy. Mu issue is the following, running the update-vfw-op-policy.sh works fine, but I don’t have any artifacts after drools restarts, nor any close loop params. Does someone has an idea where I should look at to fix this? Thanks Alexis Bellow my run: FYI, I adapted the script for OOM. $ ./update-vfw-op-policy.sh Usage: update-vfw-op-policy.sh <k8s-host> <policy-pdp-node-port> <policy-drools-node-port> <resource-id> $ ./update-vfw-op-policy.sh 10.195.197.141 30220 30221 780661ba-d934-408a-99dd-295263e7a80d Updating vFW Operational Policy .. * Trying 10.195.197.141... * TCP_NODELAY set * Connected to 10.195.197.141 (10.195.197.141) port 30220 (#0) > PUT /pdp/api/updatePolicy HTTP/1.1 > Host: 10.195.197.141:30220 > User-Agent: curl/7.54.0 > Content-Type: application/json > Accept: text/plain > ClientAuth: cHl0aG9uOnRlc3Q= > Authorization: Basic dGVzdHBkcDphbHBoYTEyMw== > Environment: TEST > Content-Length: 1328 > Expect: 100-continue > < HTTP/1.1 100 Continue * We are completely uploaded and fine < HTTP/1.1 200 OK < Server: Apache-Coyote/1.1 < Content-Type: text/plain;charset=ISO-8859-1 < Content-Length: 149 < Date: Thu, 07 Dec 2017 15:02:06 GMT < * Connection #0 to host 10.195.197.141 left intact Transaction ID: 5f582dd6-d4b4-4665-8274-0403775be82f --Policy with the name com.Config_BRMS_Param_BRMSParamvFirewall.2.xml was successfully updated. Pushing the vFW Policy .. * Trying 10.195.197.141... * TCP_NODELAY set * Connected to 10.195.197.141 (10.195.197.141) port 30220 (#0) > PUT /pdp/api/pushPolicy HTTP/1.1 > Host: 10.195.197.141:30220 > User-Agent: curl/7.54.0 > Content-Type: application/json > Accept: text/plain > ClientAuth: cHl0aG9uOnRlc3Q= > Authorization: Basic dGVzdHBkcDphbHBoYTEyMw== > Environment: TEST > Content-Length: 99 > * upload completely sent off: 99 out of 99 bytes < HTTP/1.1 200 OK < Server: Apache-Coyote/1.1 < Content-Type: text/plain;charset=ISO-8859-1 < Content-Length: 162 < Date: Thu, 07 Dec 2017 15:02:12 GMT < * Connection #0 to host 10.195.197.141 left intact Transaction ID: 6495f424-78d5-4434-a2f2-83a335d2523f --Policy 'com.Config_BRMS_Param_BRMSParamvFirewall.2.xml' was successfully pushed to the PDP group 'default'. Restarting PDP-D .. Defaulting container name to drools. Use 'kubectl describe pod/drools-3276366710-tlszz' to see all of the containers in this pod. [drools-pdp-controllers] L []: Stopping Policy Management... Policy Management (pid=4791) is stopping... Policy Management has stopped. [drools-pdp-controllers] L []: Policy Management (pid 5041) is running PDP-D amsterdam maven coordinates .. * Trying 10.195.197.141... * TCP_NODELAY set * Connected to 10.195.197.141 (10.195.197.141) port 30221 (#0) * Server auth using Basic with user '@1b3rt' > GET /policy/pdp/engine/controllers/amsterdam/drools HTTP/1.1 > Host: 10.195.197.141:30221 > Authorization: Basic QDFiM3J0OjMxbnN0MzFu > User-Agent: curl/7.54.0 > Accept: */* > < HTTP/1.1 200 OK < Date: Thu, 07 Dec 2017 15:03:13 GMT < Content-Type: application/json < Content-Length: 231 < Server: Jetty(9.3.14.v20161028) < { [231 bytes data] * Connection #0 to host 10.195.197.141 left intact { "alive": false, "artifactId": "NO-ARTIFACT-ID", "brained": false, "canonicalSessionNames": [], "container": null, "groupId": "NO-GROUP-ID", "locked": false, "recentSinkEvents": [], "recentSourceEvents": [], "sessionNames": [], "version": "NO-VERSION" } PDP-D control loop updated .. * Trying 10.195.197.141... * TCP_NODELAY set * Connected to 10.195.197.141 (10.195.197.141) port 30221 (#0) * Server auth using Basic with user '@1b3rt' > GET > /policy/pdp/engine/controllers/amsterdam/drools/facts/closedloop-amsterdam/org.onap.policy.controlloop.Params > HTTP/1.1 > Host: 10.195.197.141:30221 > Authorization: Basic QDFiM3J0OjMxbnN0MzFu > User-Agent: curl/7.54.0 > Accept: */* > < HTTP/1.1 200 OK < Date: Thu, 07 Dec 2017 15:03:14 GMT < Content-Type: application/json < Content-Length: 2 < Server: Jetty(9.3.14.v20161028) < { [2 bytes data] * Connection #0 to host 10.195.197.141 left intact []
_______________________________________________ onap-discuss mailing list [email protected] https://lists.onap.org/mailman/listinfo/onap-discuss
