Hi Bharath, I think first you need to inject the proxy values to policy helm templates and scripts in different places and watch the logs of brmsgw, pap and pdp before even start testing CL.
In oom/kubernetes/policy/resources/config/pe/push-policies.sh (before wget) and then unset In oom/kubernetes/policy/charts/drools/resources/config/opt/policy/config/drools/apps-install.sh Also, in order to update the settings.xml for mvn, you need to add the sed logic (the same way we did for Amsterdam release) to docker image files. Locate docker-install.sh Search for configure_settings; if found then; Add sed -i "/<\/servers>/a\ \<proxies> <proxy> <id>http-proxy<\/id> <active>true<\/active> <protocol>http<\/protocol> <host>host<\/host> <port>port<\/port> <nonProxyHosts>localhost|127.0.0.1<\/nonProxyHosts> <\/proxy> <proxy> <id>https-proxy<\/id> <active>true<\/active> <protocol>https<\/protocol> <host>host<\/host> <port>port<\/port> <nonProxyHosts>localhost|127.0.0.1|nexus:8081<\/nonProxyHosts> <\/proxy> <\/proxies>" $HOME_M2/settings.xml after configure_settings function call if not found then Add sed -i "/<\/servers>/a\ \<proxies> <proxy> <id>http-proxy<\/id> <active>true<\/active> <protocol>http<\/protocol> <host>host<\/host> <port>port<\/port> <nonProxyHosts>localhost|127.0.0.1<\/nonProxyHosts> <\/proxy> <proxy> <id>https-proxy<\/id> <active>true<\/active> <protocol>https<\/protocol> <host>host<\/host> <port>port<\/port> <nonProxyHosts>localhost|127.0.0.1|nexus:8081<\/nonProxyHosts> <\/proxy> <\/proxies>" $HOME/.m2/settings.xml after if condition for [[ -f $HOME/.m2/settings.xml]] There are not the proper fixes but these should make you to move forward Thanks, Kranthi From: Bharath Thiruveedula <[email protected]> Date: Tuesday, July 24, 2018 at 12:10 PM To: "HERNANDEZ-HERRERO, JORGE" <[email protected]> Cc: onap-discuss <[email protected]>, Kranthi Guttikonda <[email protected]>, bharath thiruveedula <[email protected]>, "[email protected]" <[email protected]>, "[email protected]" <[email protected]>, "Parigi, Raghavender" <[email protected]> Subject: Re: [E] Re: [onap-discuss] Closed Loop Documentation for Beijing Hi Jorge, I tried the same command to bring up pdp again, I can see same resolving issues. I am running the environment behind the proxy This is the log from pap/xacml-pap-rest ErrorDescription=This is an Invalid Schema Error. Please check the error message for detail information server=dev-pap-678b44cd87-lzjvxMetricEndTimestamp=2018-07-24T16:05:42.119+00:00 targetEntity=POLICY partnerName=USER serviceName=PAP.put TransactionEndTimestamp=2018-07-24T16:05:42.120+00:00 StatusCode=COMPLETE ErrorCategory=ERROR TransactionElapsedTime=18 requestId=b12ca0c9-7304-4d9f-9b58-3407b4b60dd9 serverIpAddress=10.42.160.99 ClassName= targetServiceName=PE Process ErrorCode=POLICY-400E MetricElapsedTime=14 MetricBeginTimestamp=2018-07-24T16:05:42.105+00:00 statusCode=COMPLETE EELF9998E RESOURCE ID [ERROR_SCHEMA_INVALID] CANNOT BE FORMATTED - NO RESOURCE WITH THAT ID EXISTS!\nREQUEST FOR RESOURCE WAS MADE FROM:\n AT COM.ATT.EELF.I18N.EELFRESOURCEMANAGER.FORMAT(EELFRESOURCEMANAGER.JAVA:326)\n AT COM.ATT.EELF.CONFIGURATION.SLF4JWRAPPER.WRITETOLOG(SLF4JWRAPPER.JAVA:815)\n AT COM.ATT.EELF.CONFIGURATION.SLF4JWRAPPER.ERROR(SLF4JWRAPPER.JAVA:908)\n AT ORG.ONAP.POLICY.COMMON.LOGGING.EELF.POLICYLOGGER.ERROR(POLICYLOGGER.JAVA:648)\n AT ORG.ONAP.POLICY.XACML.UTIL.XACMLPOLICYSCANNER.READPOLICY(XACMLPOLICYSCANNER.JAVA:657)\n AT ORG.ONAP.POLICY.XACML.STD.PAP.STDPDPPOLICY.READPOLICYDATA(STDPDPPOLICY.JAVA:155)\n ... 44 MORE FRAMES\n EELF9998E Resource id [ERROR_SCHEMA_INVALID] cannot be formatted - no resource with that id exists!\nRequest for resource was made from:\n at com.att.eelf.i18n.EELFResourceManager.format(EELFResourceManager.java:326)\n at com.att.eelf.configuration.SLF4jWrapper.writeToLog(SLF4jWrapper.java:815)\n at com.att.eelf.configuration.SLF4jWrapper.error(SLF4jWrapper.java:908)\n at org.onap.policy.common.logging.eelf.PolicyLogger.error(PolicyLogger.java:648)\n at org.onap.policy.xacml.util.XACMLPolicyScanner.readPolicy(XACMLPolicyScanner.java:657)\n at org.onap.policy.xacml.std.pap.StdPDPPolicy.readPolicyData(StdPDPPolicy.java:155)\n ... 44 more frames Let me know if you need any specific logs Best Regards Bharath T On Tue, Jul 24, 2018 at 4:37 AM HERNANDEZ-HERRERO, JORGE <[email protected]<mailto:[email protected]>> wrote: Hello Barath, It seems that pushing of the policies took place when what sounds like pdp service was up (resolvable with dns). The quickest thing to try is to delete the pdp with “kubectl delete pod dev-pdp-0 -n onap”, and check if it syncs up (will trigger some reconfiguration). Let me know how it goes. Jorge From: Bharath Thiruveedula [mailto:[email protected]<mailto:[email protected]>] Sent: Monday, July 23, 2018 11:04 AM To: HERNANDEZ-HERRERO, JORGE <[email protected]<mailto:[email protected]>> Cc: onap-discuss <[email protected]<mailto:[email protected]>>; Kranthi Guttikonda <[email protected]<mailto:[email protected]>>; bharath thiruveedula <[email protected]<mailto:[email protected]>>; [email protected]<mailto:[email protected]>; ROSE, DANIEL V <[email protected]<mailto:[email protected]>>; Parigi, Raghavender <[email protected]<mailto:[email protected]>> Subject: Re: [E] Re: [onap-discuss] Closed Loop Documentation for Beijing HI Jorge, Thanks for the hints. Here are my findings 1) I waited for 1 hr and then tried the steps 2) Yes I am using 1.2.3 tag images of policy 3)Here is what brmsgw logs saying WebSocketConnectReadThread-35|||||ERROR|POLICY-519E||POLICY-519E ERROR: PE300 - Data Issue: Invalid Data is given.:org.onap.policy.api.PolicyException: PE300 - Data Issue: :400:[{"policyConfigMessage":"Error in Calling the Configuration URL com.att.research.xacml.api.pdp.PDPException: PE300 - Data Issue: Error in ConfigURL","policyConfigStatus":"CONFIG_NOT_FOUND","type":null,"config":null,"policyName":"com.Config_BRMS_Param_BRMSParamVOLTE.1.xml","policyType":"BRMS_PARAM","policyVersion":"1","matchingConditions":{"ONAPName":"DROOLS","ConfigName":"BRMS_PARAM_RULE"},"responseAttributes":{"controller":"amsterdam"},"property":null}] - at org.onap.policy.std.StdPolicyEngine.callNewPDP(StdPolicyEngine.java:740) - at org.onap.policy.std.StdPolicyEngine.getConfigImpl(StdPolicyEngine.java:621) - at org.onap.policy.std.StdPolicyEngine.getConfig(StdPolicyEngine.java:236) - at org.onap.policy.api.PolicyEngine.getConfig(PolicyEngine.java:247) - at org.onap.policy.brms.api.BrmsHandler.addedPolicies(BrmsHandler.java:174) - at org.onap.policy.brms.api.BrmsHandler.runOnNotification(BrmsHandler.java:135) - at org.onap.policy.brms.api.BrmsHandler.notificationReceived(BrmsHandler.java:75) - at org.onap.policy.std.AutoClientEnd.callHandler(AutoClientEnd.java:235) - at org.onap.policy.std.AutoClientEnd.onMessage(AutoClientEnd.java:70) - at org.java_websocket.client.WebSocketClient.onWebsocketMessage(WebSocketClient.java:462) - at org.java_websocket.drafts.Draft_6455.processFrame(Draft_6455.java:696) - at org.java_websocket.WebSocketImpl.decodeFrames(WebSocketImpl.java:367) - at org.java_websocket.WebSocketImpl.decode(WebSocketImpl.java:212) - at org.java_websocket.client.WebSocketClient.run(WebSocketClient.java:389) - at java.lang.Thread.run(Thread.java:748) - Caused by: org.springframework.web.client.HttpClientErrorException: 400 Bad Request - at org.springframework.web.client.DefaultResponseErrorHandler.handleError(DefaultResponseErrorHandler.java:86) - at org.springframework.web.client.RestTemplate.handleResponse(RestTemplate.java:708) - at org.springframework.web.client.RestTemplate.doExecute(RestTemplate.java:661) - at org.springframework.web.client.RestTemplate.execute(RestTemplate.java:621) - at org.springframework.web.client.RestTemplate.exchange(RestTemplate.java:539) - at org.onap.policy.std.StdPolicyEngine.callNewPDP(StdPolicyEngine.java:718) - ... 14 more - WebSocketConnectReadThread-35|||||ERROR|POLICY-519E||POLICY-519E ERROR: PE500 - Process Flow Issue: Rertriving policy failed PE300 - Data Issue: Invalid Data is given.:org.onap.policy.api.PolicyConfigException: PE300 - Data Issue: Invalid Data is given. - at org.onap.policy.std.StdPolicyEngine.getConfigImpl(StdPolicyEngine.java:628) - at org.onap.policy.std.StdPolicyEngine.getConfig(StdPolicyEngine.java:236) - at org.onap.policy.api.PolicyEngine.getConfig(PolicyEngine.java:247) - at org.onap.policy.brms.api.BrmsHandler.addedPolicies(BrmsHandler.java:174) - at org.onap.policy.brms.api.BrmsHandler.runOnNotification(BrmsHandler.java:135) - at org.onap.policy.brms.api.BrmsHandler.notificationReceived(BrmsHandler.java:75) - at org.onap.policy.std.AutoClientEnd.callHandler(AutoClientEnd.java:235) - at org.onap.policy.std.AutoClientEnd.onMessage(AutoClientEnd.java:70) - at org.java_websocket.client.WebSocketClient.onWebsocketMessage(WebSocketClient.java:462) - at org.java_websocket.drafts.Draft_6455.processFrame(Draft_6455.java:696) - at org.java_websocket.WebSocketImpl.decodeFrames(WebSocketImpl.java:367) - at org.java_websocket.WebSocketImpl.decode(WebSocketImpl.java:212) - at org.java_websocket.client.WebSocketClient.run(WebSocketClient.java:389) - at java.lang.Thread.run(Thread.java:748) - Caused by: org.onap.policy.api.PolicyException: PE300 - Data Issue: :400:[{"policyConfigMessage":"Error in Calling the Configuration URL com.att.research.xacml.api.pdp.PDPException: PE300 - Data Issue: Error in ConfigURL","policyConfigStatus":"CONFIG_NOT_FOUND","type":null,"config":null,"policyName":"com.Config_BRMS_Param_BRMSParamVOLTE.1.xml","policyType":"BRMS_PARAM","policyVersion":"1","matchingConditions":{"ONAPName":"DROOLS","ConfigName":"BRMS_PARAM_RULE"},"responseAttributes":{"controller":"amsterdam"},"property":null}] - at org.onap.policy.std.StdPolicyEngine.callNewPDP(StdPolicyEngine.java:740) - at org.onap.policy.std.StdPolicyEngine.getConfigImpl(StdPolicyEngine.java:621) - ... 13 more - Caused by: org.springframework.web.client.HttpClientErrorException: 400 Bad Request - at org.springframework.web.client.DefaultResponseErrorHandler.handleError(DefaultResponseErrorHandler.java:86) - at org.springframework.web.client.RestTemplate.handleResponse(RestTemplate.java:708) - at org.springframework.web.client.RestTemplate.doExecute(RestTemplate.java:661) - at org.springframework.web.client.RestTemplate.execute(RestTemplate.java:621) - at org.springframework.web.client.RestTemplate.exchange(RestTemplate.java:539) - at org.onap.policy.std.StdPolicyEngine.callNewPDP(StdPolicyEngine.java:718) - ... 14 more - WebSocketConnectReadThread-48||||||POLICY-515E||POLICY-515E ERROR: XACMLErrorConstants.ERROR_PROCESS_FLOW + Error connecting to: ws://pdp:8081/pdp/notifications, Exception occured ... java.net.ConnectException: Connection refused (Connection refused) 2018-07-23T13:51:32.165+00:00||WebSocketConnectReadThread-35||||||POLICY-515E||POLICY-515E ERROR: XACMLErrorConstants.ERROR_PROCESS_FLOW + Error connecting to: ws://pdp:8081/pdp/notifications, Exception occured ... java.net.UnknownHostException: pdp Though the logs saying pdp host not found, but from brmsgw pod, I can ping pdp. Am I missing something here? Best Regards Bharath T On Mon, Jul 23, 2018 at 7:33 PM HERNANDEZ-HERRERO, JORGE <[email protected]<mailto:[email protected]>> wrote: Hi Bharath, Try a few things to make sure, the loading of policies in drools can take some time, it requires fetching jar dependencies, etc .. not sure if you tried the command a little too soon, but just if you can verify that you gave it enough time. Check also the nexus repo. Another thing to check is if you are running the latest Beijing images in the oom/kubernetes/policy charts (1.2.3 I think is the official version if I recall correctly). Last resort, would be to log into the brmsgw container and check for errors, that component is the one that places maven artifacts into nexus and notifies drools of its availability. Best regards, Jorge From: Bharath Thiruveedula [mailto:[email protected]<mailto:[email protected]>] Sent: Saturday, July 21, 2018 6:47 AM To: onap-discuss <[email protected]<mailto:[email protected]>>; HERNANDEZ-HERRERO, JORGE <[email protected]<mailto:[email protected]>>; Kranthi Guttikonda <[email protected]<mailto:[email protected]>> Cc: bharath thiruveedula <[email protected]<mailto:[email protected]>>; [email protected]<mailto:[email protected]>; ROSE, DANIEL V <[email protected]<mailto:[email protected]>>; Parigi, Raghavender <[email protected]<mailto:[email protected]>> Subject: Re: [E] Re: [onap-discuss] Closed Loop Documentation for Beijing Hi Jorge, I am just following the document you shared. I have couple of issues : 1) When I am trying to run "curl --silent --user '@1b3rt:31nst31n' -X GET http://<replica-ip>:9696/policy/pdp/engine/controllers/amsterdam/drools<https://urldefense.proofpoint.com/v2/url?u=http-3A__-253creplica-2Dip-253e-3A9696_policy_pdp_engine_controllers_amsterdam_drools&d=DwMGaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=UTP8N06L2trD3jawJkElFfA6CQYtkCWzTnn4GsHkmJw&m=Ur-XRXEFh1qc3tkK5fH5fSpp3emNdnMG_mYXwEANUPU&s=AVKkrpyoX-A-gdmWuLNe2Qv_vwrX2RsrD5-aH3wB5Wk&e=> | python -m json.tool" I got following json { "error": "amsterdam not found" } 2) After running push-policies.sh , it went as expected, but I couldn't see anything from nexus Error! Filename not specified. But I could see the expected output from curl --silent -X POST --header 'Content-Type: application/json' --header 'Accept: application/json' --header 'ClientAuth: cHl0aG9uOnRlc3Q=' --header 'Authorization: Basic dGVzdHBkcDphbHBoYTEyMw==' --header 'Environment: TEST' -d '{"policyName": ".*vFirewall.*"}' http://pdp:8081/pdp/api/getConfig<https://urldefense.proofpoint.com/v2/url?u=http-3A__pdp-3A8081_pdp_api_getConfig&d=DwMGaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=UTP8N06L2trD3jawJkElFfA6CQYtkCWzTnn4GsHkmJw&m=Ur-XRXEFh1qc3tkK5fH5fSpp3emNdnMG_mYXwEANUPU&s=L9oYbhfieUUWrXVdbFxIxUHTZspzmyOWePZh7FyULpE&e=> | python -m json.t Error! Filename not specified. Am I missing something here? Best Regards Bharath T On Sat, Jul 21, 2018 at 1:51 AM Jorge Hernandez <[email protected]<mailto:[email protected]>> wrote: Hello Bharath, For OOM install, take a look at https://wiki.onap.org/display/DW/Policy+on+OOM<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_display_DW_Policy-2Bon-2BOOM&d=DwMFAg&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=UTP8N06L2trD3jawJkElFfA6CQYtkCWzTnn4GsHkmJw&m=jv-6KYq7YDq57BtgMKFTBGtPhofGScCNH4hs1jPyFjA&s=C1pv926tIXVlUo7hDaMYpau2dH3mGelkk1t4TsCDSAA&e=>. For Heat install, should work in a similar way as Amsterdam. Jorge From: [email protected]<mailto:[email protected]> [mailto:[email protected]<mailto:[email protected]>] On Behalf Of bharath thiruveedula Sent: Friday, July 20, 2018 3:16 PM To: [email protected]<mailto:[email protected]>; Gary Wu <[email protected]<mailto:[email protected]>>; ROSE, DANIEL V <[email protected]<mailto:[email protected]>> Subject: [onap-discuss] Closed Loop Documentation for Beijing Hi, I am just going through the ONAP Beijing setup. I am just wondering is there any docs related to closed loop of vDNS/vFW in Beijing or is it the same as in Amsterdam? Best Regards Bharath T -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#11399): https://lists.onap.org/g/onap-discuss/message/11399 Mute This Topic: https://lists.onap.org/mt/23774607/21656 Group Owner: [email protected] Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
