8e16219249
We don't use Elasticsearch for flexible reports generation on the fuel-stats web UI, only for five fixed reports. Thus using of Elasticsearch is overhead and it can be removed from the servers Instead of Elasticsearch we use fuel-stats json api calls and PostgreSQL + Memcached. Changes list: - api call added to fuel-stats json api for data required on the web UI page, - column release added to DB installation_structures table schema, - memcached is used for caching data for the web UI page, - elasticsearch client removed from js requirement, - web UI page rewritten to use fuel-stats json api instead Elaticsearch. Co-Authored-By: Kate Pimenova <kpimenova@mirantis.com> Change-Id: Ie752e0d0a3c80933888f986e2497b45adce730c9 Closes-Bug: #1595548 |
||
|---|---|---|
| .. | ||
| api | ||
| test | ||
| __init__.py | ||