Gitiles
Code Review Sign In
gerrit.nordix.org / onap / dcaegen2 / platform / policy-handler / 2322ef8736e839d62930d9b6c847ce818261c26c
commit2322ef8736e839d62930d9b6c847ce818261c26c[log] [tgz]
authorAlex Shatov <alexs@att.com>Thu Jan 25 17:40:39 2018 -0500
committerAlex Shatov <alexs@att.com>Thu Jan 25 17:40:39 2018 -0500
tree9940107d0d380ede948aa932f43069c711037840
parentf53e5e70d88d813fb84848538472c601914ec652 [diff]
on not finding the policy return 404 and json

* json of what is returned from policy-engine instead of 404 html

Change-Id: I44fb7e113e23f68cac44e6ad21c1bc9b37cf3d58
Issue-ID: DCAEGEN2-249
Signed-off-by: Alex Shatov <alexs@att.com>
2 files changed
tree: 9940107d0d380ede948aa932f43069c711037840
  1. etc/
  2. etc_upload/
  3. policyhandler/
  4. tests/
  5. .coveragerc
  6. .gitignore
  7. .gitreview
  8. Dockerfile
  9. LICENSE.txt
  10. MANIFEST.in
  11. mvn-phase-lib.sh
  12. mvn-phase-script.sh
  13. pom.xml
  14. README.md
  15. requirements.txt
  16. run_policy.sh
  17. setup.py
  18. tox-local.ini
  19. tox.ini
  20. version.properties
README.md

policy_handler

web-service for policies to be used by DCAE-Controller

  • GET /policy_latest/<policy-id> -- get the latest policy from policy-engine
  • receives the push notifications from policy-engine through the web-socket, filters and gets the full policy-configs, and delivers that to deploy-handler

manual http API

  • GET /catch_up -- catch up with the latest state of the policy-engine
  • GET /policies_latest -- get all the latest policies in policy-engine through web-service API
  • GET /shutdown -- shutdown the server

installation

virtualenv policy_venv

cd policy_venv

source bin/activate

cd ../policy_handler

pip install -r requirements.txt

preparation to run

cd policy_venv

source bin/activate

cd ../policy_handler

configure

in folder policy_handler:

- `config.json` contains
    - `"scope_prefixes" : ["DCAE_alex.Config_"]` - the list of policy-scope-class values
    - `"policy_engine"` - the http connect info to ECOMP **policy-engine**
        - headers.ClientAuth : base64(<mech-id with namespace>:<password>)
        - headers.Authorization : base64(<policy-engine server auth>)
    - `"deploy_handler"` - the http connect info to _policy part_ of the **deploy-handler**
- `policy_engine.properties` contains config info for the client lib of ECOMP **policy-engine** that receives push notifications from the ECOMP **policy-engine** server
    - CLIENT_ID is the mech-id with the namespace - need to register with policy-engine team thru email
    - CLIENT_KEY is the base64 of the mech-id password - separate passwords for TEST versus PROD

run

in folder policy_handler:

./run_policy.sh