Karthick,
Please look for BRMS_DEPENDENCY_VERSION at the end of
${OOM_HOME}/kubernetes/config/docker/init/src/config/policy/opt/policy/config/pe/brmsgw.conf.
That parameter should be the same as the Policy container version number. For
Amsterdam, it has to be either 1.1.1 or 1.1.3, depending on the Policy version
that you are using (Amsterdam v1.1.1 or Amsterdam Maintenance v1.1.3).
Also,
${OOM_HOME}/kubernetes/config/docker/init/src/config/policy/opt/policy/config/pe/push-policies.sh,
line 11 should be:
wget -O cl-amsterdam-template.drl
https://git.onap.org/policy/drools-applications/plain/controlloop/templates/archetype-cl-amsterdam/src/main/resources/archetype-resources/src/main/resources/__closedLoopControlName__.drl?h=amsterdam<https://urldefense.proofpoint.com/v2/url?u=https-3A__git.onap.org_policy_drools-2Dapplications_plain_controlloop_templates_archetype-2Dcl-2Damsterdam_src_main_resources_archetype-2Dresources_src_main_resources_-5F-5FclosedLoopControlName-5F-5F.drl-3Fh-3Damsterdam&d=DwMF-g&c=LFYZ-o9_HUMeMTSQicvjIg&r=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0&m=LGT5idEEumK08dApXCgOxFAfXApvLoMJ1CW7sK4AiF0&s=qmCN2BpW641q_DVePqiSz6PvxNkhIe1v8lJoT7ifX6I&e=>
instead of wget -O cl-amsterdam-template.drl
https://git.onap.org/policy/drools-applications/plain/controlloop/templates/archetype-cl-amsterdam/src/main/resources/archetype-resources/src/main/resources/__closedLoopControlName__.drl
(note ?h=amsterdam at the end of the correct call).
You can make these changes in your OOM local repo, as described above, or
directly in the ONAP configuration folder in your NFS share (or local disk if
you have a single-host K8S cluster), in
/dockerdata-nfs/onap/policy/opt/policy/config/pe/push-policies.sh (and the same
path for brmsgw.conf). The former approach requires to rebuild ONAP, while the
latter requires to rebuild only Policy.
Marco
From: <[email protected]> on behalf of "Ramanarayanan,
Karthick" <[email protected]>
Date: Thursday, January 25, 2018 at 1:32 PM
To: "[email protected]" <[email protected]>
Subject: [onap-discuss] Demo update-vfw policy script when running without
closed loop
Hi,
In my kubernetes setup minus dcae (just vFW without closed loop),
I am trying to mount the appc packetgen interface but I am unable to see the
mounts in appc mounts list.
The policy that was pushed used the kubernetes update-vfw-op-policy.sh script
which seems to be applicable for closed loop.
Though the policy script runs and applies the policy and restarts the policy
pods, the get on controlloop.Params fails at the end.
curl -v --silent --user @1b3rt:31nst31n -X GET
http://$<https://urldefense.proofpoint.com/v2/url?u=http-3A__-24&d=DwQFAw&c=LFYZ-o9_HUMeMTSQicvjIg&r=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0&m=LPXvZgE66FrVN0FIXILCjCz_Ep8xUinjYJIIJRxdf7o&s=IRfCSSeF5ogZBUBhykVnXlspVj64QepZK_QHx6udwfc&e=>{K8S_HOST}:${POLICY_DROOLS_PORT}/policy/pdp/engine/controllers/amsterdam/drools/facts/closedloop-amsterdam/org.onap.policy.controlloop.Params
| python -m json.tool
{
"error": "amsterdam:closedloop-amsterdam:org.onap.policy.controlloop.Params
not found"
}
Moving ahead, I configure the packet gen interface with an appc put to network
topology for the packetgen vnf/ip.
Put succeeds but appc mounts doesn't show up.
Wondering if the policy script needs to be changed when executing without
closed loop?
What am I missing?
Thanks,
-Karthick
_______________________________________________
onap-discuss mailing list
[email protected]
https://lists.onap.org/mailman/listinfo/onap-discuss
