Re: [onap-discuss] [Policy] Empty policies in Standalone mode

Hi Bharath, you should be able to do all operations within the drools container, try this: docker exec -it drools bash cd /tmp wget https://git.onap.org/policy/drools-applications/tree/controlloop/packages/apps/src/files/apps-installer (may have to tweak it to go through proxy) chmod +x

Re: [onap-discuss] [Policy] Empty policies in Standalone mode

Hi Jorge, Do you mean to run apps-installer file in drools container and restart the drools container? Is that my understanding right? Best Regards Bharath T From: HERNANDEZ-HERRERO, JORGE Sent: Tuesday, February 20, 2018 11:53 PM To:

Re: [onap-discuss] [Policy] Empty policies in Standalone mode

Hi Bharat, Yes, proxy issue seems like, collecting the dependencies. Can you try to see you can get out through proxy with linux shell, by running this script: https://git.onap.org/policy/drools-applications/tree/controlloop/packages/apps/src/files/apps-installer If that works, restart pdp-d,

Re: [onap-discuss] [Policy] Empty policies in Standalone mode

Hi Jorge, I have tried the same with the policy VM in original ONAP setup I got the same output. After adding proxy, now I am facing the following error in drools container [name=amsterdam, alive=false, locked=false, droolsController=null]: cannot init-drools because of

Re: [onap-discuss] [Policy] Empty policies in Standalone mode

Hello Barath, This set up may have some limitations with operations that involve DMaaP communication, such as the brmsgw and drools pdp when a new operational policy is pushed (rules jar) since the DMaaP container is not spawned here.You could confirm that this is the case by going into