95eac8c932
This update enhanced keystone-api-proxy to take a sync_endpoint parameter from its configuration file and enqueue job for dcorch with that sync_endpoint type. If sync_endpoint doesn't present in its configuration file, it will use the default endpoint type to enqueue job. Change-Id: I85698638cee2598955c4deb41a6b8033b0ace9fd Story: 2004766 Task: 36156 Depends-On: https://review.opendev.org/#/c/682062/ Signed-off-by: Andy Ning <andy.ning@windriver.com> |
||
|---|---|---|
| .. | ||
| controllers | ||
| proxy | ||
| README.rst | ||
| __init__.py | ||
| api_config.py | ||
| app.py | ||
| enforcer.py | ||
README.rst
api
DC Orchestrator API is Web Server Gateway Interface (WSGI) applications to receive and process API calls, including keystonemiddleware to do the authentication, parameter check and validation, convert API calls to job rpc message, and then send the job to DC Orchestrator Engine through the queue. If the job will be processed by DC Orchestrator Engine in synchronous way, the DC Orchestrator API will wait for the response from the DC Orchestrator Engine. Otherwise, the DC Orchestrator API will send response to the API caller first, and then send the job to DC Orchestrator Engine in asynchronous way.
Multiple DC Orchestrator API could run in parallel, and also can work in multi-worker mode.
Multiple DC Orchestrator API will be designed and run in stateless mode, persistent data will be accessed (read and write) from the DC Orchestrator Database through the DAL module.
Setup and encapsulate the API WSGI app
- app.py:
-
Setup and encapsulate the API WSGI app, including integrate the keystonemiddleware app
- apicfg.py:
-
API configuration loading and init
- enforcer.py
-
Enforces policies on the version2 API's