cd13f8496a
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 Instad 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. Change-Id: Ie752e0d0a3c80933888f986e2497b45adce730c9 Closes-Bug: #1595548
13 lines
218 B
Plaintext
13 lines
218 B
Plaintext
alembic==0.6.7
|
|
Flask==0.10.1
|
|
Flask-JsonSchema==0.1.1
|
|
Flask-Migrate==1.2.0
|
|
Flask-Script==2.0.5
|
|
Flask-SQLAlchemy==2.0
|
|
psycopg2==2.5.4
|
|
python-dateutil==2.2
|
|
python-memcached>=1.56
|
|
PyYAML==3.11
|
|
six>=1.8.0
|
|
SQLAlchemy==0.9.8
|