Hello Jorge, I sent the message to "PDPD-CONFIGURATION" channel by changing the name to "amsterdam" using postman and I could see drool container success to deploy the artifact. I probably need to cre

#policy #drools

Hi Min, Yes, in the message, the "name":"default", should be "name":"amsterdam" to match the drools controller name. If you look in the actual "createPolicy" messages using the legacy APIs, https://gi

#policy #drools

Hello, Thank you for your response. I could see below message sent from brmwgw {"requestId":"258701a8-d094-4f83-a2e6-d9ddd325a8c6","entity":"controller","controllers":[{"name":"default","drools":{"gro

#policy #drools

Check out in the drools container the $POLICY_LOGS/network.log , look for configuration messages over the PDPD-CONFIGURATION channel, you should see an update configuration request commanding drools t

#policy #drools

I tried to push the operational policy from policy GUI to default PDP group, but I can see the error message from drool log like below. [2019-10-03T17:52:51.345+00:00|WARN|PolicyEngineManager|DMAAP-so

#policy #drools

Hello, Please monitor this ticket for resolution to this problem: https://jira.onap.org/browse/CLAMP-484. It's related to the payload field being a (empty) string. Best regards, Jorge

#drools #controlloop #dublin #clamp

Submit from CLAMP generate error in drols pod - configuration is not stored. Is it known issue? How to solve that? Logs from drools pod: (dev-policy-drools-0) [2019-08-23T13:49:41.144+00:00|INFO|contr

#drools #controlloop #dublin #clamp

Hello, Try changing "ueb" to dmaap, for example: http --verify=no -a "${TELEMETRY_USER}:${TELEMETRY_PASSWORD}" PUT https://localhost:9696/policy/pdp/engine/topics/sources/dmaap/DCAE_TOPIC/events @./dc

#drools #policy #dmaap

I am trying to trigger the policy by sending the event to Dmaap 'unauthenticated.DCAE_CL_OUTPUT' topic. I expected to see log from drool that subscribe this topic, but I cannot see any log for that ev

#drools #policy #dmaap

Hello, According to your output, readiness checks are failing, make sure that policydb and nexus container dependencies come up ok. Best regards, Jorge

#install #usecaseui #kubernetes #policy #drools

Hello, In Beijing installation the drools pod status is init and doesn't run. It's waiting on init status even deleted the pod several times, although there is no error in the logs. It can't create th

#install #usecaseui #kubernetes #policy #drools

Dear community, I had switched to the beijing branch of the demo repository and that brought the vFW demo back up. It turns out that the repository branch and the artifact versions are tightly coupled

#install #usecaseui #kubernetes #policy #drools

Cristina, Please follow this webpage to download VM images: https://docs.openstack.org/image-guide/obtain-images.html I typically use whatever is in the current directory here: http://cloud-images.ubu

#install #usecaseui #kubernetes #policy #drools

Hello, Thank you but this did not help. Mainly, I am getting errors regarding curl and brctl missing on the SINC VM: Making evel.o from evel.c /opt/VES/evel/evel-library/bldjobs/../code/evel_library/e

#install #usecaseui #kubernetes #policy #drools

Dear Cristina, You need to use latest heat files for onboarding vFWCL (from https://github.com/onap/demo) Then, for the preload follow the structure that is attached in "preload.txt" file. I hope this

#install #usecaseui #kubernetes #policy #drools

Hello Jorge, This time, the PDP healthcheck was Successful. However, regarding the ping from brmsgw: no, it cannot do name resolution and thus cannot ping the three pods (it's using their kubernetes c

#install #usecaseui #kubernetes #policy #drools

Cristina, I am wondering if you are now able to ping from brmsgw to nexus, drools or message-router. Regarding your last message, I don't know what happened but I had a similar issue before (VMs sudde

#install #usecaseui #kubernetes #policy #drools

Dear Jorge, This really did fix my problem for Policy upload. Thank you for that. However, it seems that after the update, the SINC vFW VMs get created on Openstack, they have no errors in the logs, t

#install #usecaseui #kubernetes #policy #drools

I see .. I think the lab installation is not in good state. It may be beyond the policy component, if you cannot ping the "message-router" service, which may be an indication of bigger problems. Check

#install #usecaseui #kubernetes #policy #drools

Hello Jorge, Thank you for pointing me in the right direction. I did go through the wiki page that you are mentioning. Here is the overview in short: - Healthcheck: PDP and PAP are unreachable - Polic

#install #usecaseui #kubernetes #policy #drools