It is common for OpenStack projects to use oslo-config-generator to generate
a sample config file which contains all available configuration options.
Work items:
* removed etc/monasca/log-api.conf (it is autogenerated)
* keep all config in one place to mimic the configuration file
* added configuration files to documentation
Story: 2000970
Task: 4121
Change-Id: I8777ed6cd38739e87b19be248b9c120e84626ad1
Following commit introduces using composite
paste file to describe application pipelines.
With the help of composite feature it was possible to
define 4 distinct supapplications, each having different
pipeline setup:
* version_app => no keystoneauth, simple data return with error trap
* healthcheck_app => no keystoneauth, simple data return with error trap
* api_v2 => as it was, added error_trap though
* api_v3 => as it was, added error_trap though
Following approach opens up the possibilities of modelling an API
in far more flexible way and removes the need of any hacking inside
the codebase.
Note:
Keeps backward compatibility with older codebase.
Extra:
* removed dirty hack around skipping certain request.path
in keystonemiddleware (now described in paste file)
* removed 404 when issuing ```curl api_host:api_port/```. Request
is redirected down to VersionApp
Depends-On: I0323eacb5cbba8418550e3322189104c35cf4c36
Change-Id: I873e1376665c8cf66c8ee503975324f9b93ddb45
Fix Versions endpoint
- was conflicting with other endpoints starting
from v2.0 and v3.0 which for versions was {version_id}
- template dict VERSIONS was mutated every request
Additionally this commit provides moving /version
outside of keystone authentication
Change-Id: I184a0fbc2dcaca21aa5f1256d9a1c41597f9d184
Healthcheck allows to verify if:
- API is up and running
- Kafka, that monasca-log-api sends data to, is up and running
and an expected topic can be found there.
Other:
- added documentation entries
Change-Id: I316c1d9518cfed37119f11c326c071bfbfc7658e
Martin Chacon Piza