I just added Jorge as a member of tenant ‘demonstrable’ , please go with this tenant.
Thanks. Best Regards, Bin Yang, Solution Readiness Team, Wind River Direct +86,10,84777126 Mobile +86,13811391682 Fax +86,10,64398189 Skype: yangbincs993 From: DRAGOSH, PAMELA L (PAM) [mailto:pdrag...@research.att.com] Sent: Tuesday, January 16, 2018 10:23 PM To: Yang, Bin; Matt, Brian; onap-discuss@lists.onap.org Cc: HERNANDEZ-HERRERO, JORGE Subject: Re: [onap-discuss] [APPC][POLICY] Drools and APPC issues in Amsterdam with vFWCL Sure – please add Jorge. Not sure what his username is, he can provide that. Thanks, Pam From: "Yang, Bin" <bin.y...@windriver.com<mailto:bin.y...@windriver.com>> Date: Tuesday, January 16, 2018 at 9:20 AM To: "DRAGOSH, PAMELA L (PAM)" <pdrag...@research.att.com<mailto:pdrag...@research.att.com>>, "Matt, Brian" <brian.m...@windstream.com<mailto:brian.m...@windstream.com>>, "onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>" <onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>> Cc: "HERNANDEZ-HERRERO, JORGE" <jh1...@att.com<mailto:jh1...@att.com>> Subject: RE: [onap-discuss] [APPC][POLICY] Drools and APPC issues in Amsterdam with vFWCL Hi Pam, Appreciate your quick response, I am using the ONAP lab but in my newly created tenant. Please let me know the username of your team members who will working on this this issue, so I can add him/her to be member of my tenant. Thanks. Best Regards, Bin Yang, Solution Readiness Team, Wind River Direct +86,10,84777126 Mobile +86,13811391682 Fax +86,10,64398189 Skype: yangbincs993 From: DRAGOSH, PAMELA L (PAM) [mailto:pdrag...@research.att.com] Sent: Tuesday, January 16, 2018 9:40 PM To: Yang, Bin; Matt, Brian; onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org> Cc: HERNANDEZ-HERRERO, JORGE Subject: Re: [onap-discuss] [APPC][POLICY] Drools and APPC issues in Amsterdam with vFWCL Bin, Sorry I missed this the other day. Let’s have our team take a look as it looks like the Drools PDP is missing the Amsterdam controller. That should never have been deleted. Which lab are you in? If you can give access to Jorge, he can take a quick look. Regards, Pam From: <onap-discuss-boun...@lists.onap.org<mailto:onap-discuss-boun...@lists.onap.org>> on behalf of "Yang, Bin" <bin.y...@windriver.com<mailto:bin.y...@windriver.com>> Date: Tuesday, January 16, 2018 at 4:50 AM To: "Matt, Brian" <brian.m...@windstream.com<mailto:brian.m...@windstream.com>>, "onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>" <onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>> Subject: Re: [onap-discuss] [APPC][POLICY] Drools and APPC issues in Amsterdam with vFWCL Hi Brian, Have you been able to get policy issue fixed? I observed the same issue, and the branches are correct for my ONAP template file. Does anyone could help on this issue? Thanks. policy_repo http://gerrit.onap.org/r/policy/docker.git<https://urldefense.proofpoint.com/v2/url?u=http-3A__gerrit.onap.org_r_policy_docker.git&d=DwMFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=jwTiArcEj6aUX0HjV0M3dT12gUtk7rC07xpgpVZkS_4&m=nT1UQBgEJJ5r-3awkwNBEErfZCmfcE9l9H200o6J1Y0&s=Bgrtd5jVAIdKPXyoFZWdfe-AEdVKgEaeTRnL_sMPZ6I&e=> policy_docker v1.1.2 policy_branch amsterdam policy_repo http://gerrit.onap.org/r/policy/docker.git<https://urldefense.proofpoint.com/v2/url?u=http-3A__gerrit.onap.org_r_policy_docker.git&d=DwQFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=jwTiArcEj6aUX0HjV0M3dT12gUtk7rC07xpgpVZkS_4&m=nT1UQBgEJJ5r-3awkwNBEErfZCmfcE9l9H200o6J1Y0&s=Bgrtd5jVAIdKPXyoFZWdfe-AEdVKgEaeTRnL_sMPZ6I&e=> $ ./demo/vnfs/vFW/scripts/update-vfw-op-policy.sh policy.api.simpledemo.onap.org 7fe331bc-f46e-4cb3-aaa3-639024381f86 ./onap_dev.pem Removing the vFW Policy from PDP.. * Trying 10.12.9.121... * Connected to policy.api.simpledemo.onap.org (10.12.9.121) port 8081 (#0) > DELETE /pdp/api/deletePolicy HTTP/1.1 > Host: policy.api.simpledemo.onap.org:8081 > User-Agent: curl/7.50.1 > Content-Type: application/json > Accept: text/plain > ClientAuth: cHl0aG9uOnRlc3Q= > Authorization: Basic dGVzdHBkcDphbHBoYTEyMw== > Environment: TEST > Content-Length: 133 > * upload completely sent off: 133 out of 133 bytes < HTTP/1.1 200 OK < Server: Apache-Coyote/1.1 < Content-Type: text/plain;charset=ISO-8859-1 < Content-Length: 91 < Date: Tue, 16 Jan 2018 09:32:08 GMT < * Connection #0 to host policy.api.simpledemo.onap.org left intact Transaction ID: 310812b5-858f-4ee7-82a7-0b6723466a19 --The policy was successfully deleted. Updating vFW Operational Policy .. * Trying 10.12.9.121... * Connected to policy.api.simpledemo.onap.org (10.12.9.121) port 8081 (#0) > PUT /pdp/api/updatePolicy HTTP/1.1 > Host: policy.api.simpledemo.onap.org:8081 > User-Agent: curl/7.50.1 > Content-Type: application/json > Accept: text/plain > ClientAuth: cHl0aG9uOnRlc3Q= > Authorization: Basic dGVzdHBkcDphbHBoYTEyMw== > Environment: TEST > Content-Length: 1309 > 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: Tue, 16 Jan 2018 09:32:29 GMT < * Connection #0 to host policy.api.simpledemo.onap.org left intact Transaction ID: 8ea2a93d-9e9a-4d30-b944-c6d169cc2eb5 --Policy with the name com.Config_BRMS_Param_BRMSParamvFirewall.2.xml was successfully updated. Pushing the vFW Policy .. * Trying 10.12.9.121... * Connected to policy.api.simpledemo.onap.org (10.12.9.121) port 8081 (#0) > PUT /pdp/api/pushPolicy HTTP/1.1 > Host: policy.api.simpledemo.onap.org:8081 > User-Agent: curl/7.50.1 > 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: Tue, 16 Jan 2018 09:32:35 GMT < * Connection #0 to host policy.api.simpledemo.onap.org left intact Transaction ID: 9ad6377c-6a4c-4a8c-870f-df9fa69a5003 --Policy 'com.Config_BRMS_Param_BRMSParamvFirewall.2.xml' was successfully pushed to the PDP group 'default'. Restarting PDP-D .. The authenticity of host 'policy.api.simpledemo.onap.org (10.12.9.121)' can't be established. ECDSA key fingerprint is SHA256:PzUojk3RJNW5LsjcrMA80lyIV3opeekfg7fbbOqsqE8. Are you sure you want to continue connecting (yes/no)? yes Warning: Permanently added 'policy.api.simpledemo.onap.org,10.12.9.121' (ECDSA) to the list of known hosts. [drools-pdp-controllers] L []: Stopping Policy Management... Policy Management (pid=5503) is stopping... Policy Management has stopped. [drools-pdp-controllers] L []: Policy Management (pid 5762) is running PDP-D amsterdam maven coordinates .. * Trying 10.12.9.121... * Connected to policy.api.simpledemo.onap.org (10.12.9.121) port 9696 (#0) * Server auth using Basic with user '@1b3rt' > GET /policy/pdp/engine/controllers/amsterdam/drools HTTP/1.1 > Host: policy.api.simpledemo.onap.org:9696 > Authorization: Basic QDFiM3J0OjMxbnN0MzFu > User-Agent: curl/7.50.1 > Accept: */* > < HTTP/1.1 404 Not Found < Date: Tue, 16 Jan 2018 09:33:44 GMT < Content-Type: application/json < Content-Length: 31 < Server: Jetty(9.3.14.v20161028) < { [31 bytes data] * Connection #0 to host policy.api.simpledemo.onap.org left intact { "error": "amsterdam not found" } PDP-D control loop updated .. * Trying 10.12.9.121... * Connected to policy.api.simpledemo.onap.org (10.12.9.121) port 9696 (#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: policy.api.simpledemo.onap.org:9696 > Authorization: Basic QDFiM3J0OjMxbnN0MzFu > User-Agent: curl/7.50.1 > Accept: */* > < HTTP/1.1 404 Not Found < Date: Tue, 16 Jan 2018 09:33:44 GMT < Content-Type: application/json < Content-Length: 87 < Server: Jetty(9.3.14.v20161028) < { [87 bytes data] * Connection #0 to host policy.api.simpledemo.onap.org left intact { "error": "amsterdam:closedloop-amsterdam:org.onap.policy.controlloop.Params not found" } Best Regards, Bin Yang, Solution Readiness Team, Wind River Direct +86,10,84777126 Mobile +86,13811391682 Fax +86,10,64398189 Skype: yangbincs993 From: onap-discuss-boun...@lists.onap.org<mailto:onap-discuss-boun...@lists.onap.org> [mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Matt, Brian Sent: Saturday, January 13, 2018 2:29 AM To: onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org> Subject: [onap-discuss] [APPC][POLICY] Drools and APPC issues in Amsterdam with vFWCL We’ve been working through the vFW demo with Amsterdam and have the VM deployed. However, the APPC mounting and Drools policy deployment are not working completely. We’ve got through the heatbridge setup and are having issues with the policy steps and the APPC steps. For APPC we found that the image being delivered by the heat templates for 1.0.0 appear to have a /opt/sdnc directory where the deployment is expecting an /opt/appc directory. We renamed these to get the container running and it appears to work fine that way, but it may be contributing to the issue? When attempting to do the APPC mount we are getting the following error. <errors xmlns="urn:ietf:params:xml:ns:yang:ietf-restconf"> <error> <error-type>protocol</error-type> <error-tag>malformed-message</error-tag> <error-message>Error parsing input: Unknown child(ren) node(s) detected, identified by: (urn:opendaylight:netconf-node-topology)host, in: list node</error-message> </error> </errors> Below are the details of our call. URL: http://{{appc_ip}}:8282/restconf/config/network-topology:network-topology/topology/topology-netconf/node/8d1df789-bf7f-4c6a-9515-8f4b7583febd<https://urldefense.proofpoint.com/v2/url?u=http-3A__-257b-257bappc-5Fip-257d-257d-3A8282_restconf_config_network-2Dtopology-3Anetwork-2Dtopology_topology_topology-2Dnetconf_node_8d1df789-2Dbf7f-2D4c6a-2D9515-2D8f4b7583febd&d=DwMFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=jwTiArcEj6aUX0HjV0M3dT12gUtk7rC07xpgpVZkS_4&m=nT1UQBgEJJ5r-3awkwNBEErfZCmfcE9l9H200o6J1Y0&s=FIp_sHfqYF0oXsRzTvjW2lzs76FEFj9I7G78scJXAyM&e=> Headers: Authorization: Basic YWRtaW46S3A4Yko0U1hzek0wV1hsaGFrM2VIbGNzZTJnQXc4NHZhb0dHbUp2VXkyVQ== Content-Type: text/xml Accept: application/xml Content: <node xmlns="urn:TBD:params:xml:ns:yang:network-topology"> <node-id>8d1df789-bf7f-4c6a-9515-8f4b7583febd</node-id> <host xmlns="urn:opendaylight:netconf-node-topology">10.0.80.2</host> <port xmlns="urn:opendaylight:netconf-node-topology">2831</port> <username xmlns="urn:opendaylight:netconf-node-topology">admin</username> <password xmlns="urn:opendaylight:netconf-node-topology">admin</password> <tcp-only xmlns="urn:opendaylight:netconf-node-topology">false</tcp-only> </node> For Drools we are able to delete the policy from PDP, Update the policy in PDP, and push the policy in PDP. When we get past that point, after restarting policy on the drools container, we are getting an error that the Amsterdam controller does not exist. { "error": "amsterdam not found" } This is coming back from http://policy.api.simpledemo.onap.org:9696/policy/pdp/engine/controllers/amsterdam/drools<https://urldefense.proofpoint.com/v2/url?u=http-3A__policy.api.simpledemo.onap.org-3A9696_policy_pdp_engine_controllers_amsterdam_drools&d=DwMFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=jwTiArcEj6aUX0HjV0M3dT12gUtk7rC07xpgpVZkS_4&m=nT1UQBgEJJ5r-3awkwNBEErfZCmfcE9l9H200o6J1Y0&s=P26cELmFhT4smi1iSdkSM9PCxy0oehkODPX2NhN7jQ0&e=>. If we back it up a bit to http://policy.api.simpledemo.onap.org:9696/policy/pdp/engine/controllers<https://urldefense.proofpoint.com/v2/url?u=http-3A__policy.api.simpledemo.onap.org-3A9696_policy_pdp_engine_controllers&d=DwMFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=jwTiArcEj6aUX0HjV0M3dT12gUtk7rC07xpgpVZkS_4&m=nT1UQBgEJJ5r-3awkwNBEErfZCmfcE9l9H200o6J1Y0&s=LI9lzgRawJIfQxDsP3hkpTkikz7wemYiGAZmEJBRPw4&e=> we get a response of an empty list, we assume this means there are no controllers created? I looked around the wiki and searched through the discuss conversations but couldn’t find references to these specific errors. Brian This email message and any attachments are for the sole use of the intended recipient(s). Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message and any attachments.
_______________________________________________ onap-discuss mailing list onap-discuss@lists.onap.org https://lists.onap.org/mailman/listinfo/onap-discuss
