summaryrefslogtreecommitdiffstats
path: root/message-router-blueprint.yaml
diff options
context:
space:
mode:
authorJorge Hernandez <jh1730@att.com>2018-04-30 19:53:29 -0500
committerJorge Hernandez <jh1730@att.com>2018-05-06 22:26:03 -0500
commit823691fb0dbf7538b5d3319c1b3afdb051c001dd (patch)
tree9810cac402a2149022b2b5c35d9e7fbee99c4686 /message-router-blueprint.yaml
parentf4eea37ac0a03de52c254707887b69626aa9df78 (diff)
oom tweaks in pap configuration for pdp-x pooling
paplp_1 process is unused and causes intermittent bad behavior when issuing healthchecks. Since it provides no apparent benefit integrity monitor usage has been disabled. preloading policies apis are executed when the PAP come up. The PDP-Xs take longer to come up, therefore the push-policies script causes bad interactions. This operation has to be triggered after all the PDP-Xs are up and properly running, which is difficult to predict. Therefore, it is moved to a manual step execution. In the future, we could think of'how perhaps execute autonomously by some other means. It does not currently work as is, so it is disabled, at least temporarily, there were a couple problems with pap.conf, first the pdps hostname need to be explicitly provided, as PAP keeps a white list of pdp hosts that can connect to it and be served policies. Another limitation is the format, note the change to ";" to separate pdps, instead of ",". Further the automatic configuration sequence is only made for 1 PDP-X, does not work well when multiple PDP-Xs are provided, so for the first PDP-X, the credentials need to be explicitly added, otherwise, it denies access to PDP-Xs. Change-Id: I5d4a9a39822c036db26e97edb594ecaaa27f80d8 Issue-ID: POLICY-768 Signed-off-by: Jorge Hernandez <jh1730@att.com>
Diffstat (limited to 'message-router-blueprint.yaml')
0 files changed, 0 insertions, 0 deletions