- devstack plugin: run manage.py using $PYTHON (defined by devstack,
it points to the Python interpreter used by DevStack;
- add an explicit envlist for py36;
- add the classifier for Python 3.6 to setup.cfg;
- bump the minumum tox version to 2.0, which is the de-facto
minimum version.
Change-Id: I2bce1562b9ac49abf2e80efd3d6df392e40328b1
Since Django 1.10 a new property DATA_UPLOAD_MAX_NUMBER_FIELDS causes some
plugins to fail during NGT creation. This patch adds a file to override
this property for sahara dashboard.
Depends-On: Id4d15b8bd5f032ff457395af5d77b255b6077a2a
Change-Id: I29ec88d7c733d4a977867dc24e13eb8e98fbcc48
Closes-bug: #1714575
Co-Authored-By: ArchiFleKs <lefevre.kevin@gmail.com>
A working directory in DevStack is not sahara-dashboard directory,
so the directory path must be specified by an absolute path.
In addition, django manage.py works if 'locale' directory exists.
This commit uses django manage.py to simplify the command.
When I tested the devstack plugin for translation previously,
it seems compiled message catalogs existed and I didn't notice it.
Change-Id: I8dde297976faf01a6dbe1f70ec5cd3be4ba3f160
In Liberty, sahara-dashboard supports translations, but does not now.
Once this patch is merged, we can enable the infra tranlation jobs.
* Prepare babel-{django|djangojs}.cfg so that the infra script
extracts message catalogs [1]
* Update devstack plugin to compile message catalogs
* Remove babel related entries in setup.cfg because it does not
work for horizon plugins. Babel does not support message extraction
for multiple domains.
* Create symlink sahara_dashboard/content/data_processing/locale
(which points to sahara_dashboard/locale)
The infra translation script assumes <modulename>/locale as
locale dir. On the other hand, sahara dashboard registers
"sahara_dashboard.content.data_processing" in INSTALLED_APPS.
Django search locale data from <apps>/locale for each INSTALLED_APPS.
Thus this symlink is required to make translation work.
Note that I am not sure why sahara dashboard uses
"sahara_dashboard.content.data_processing" as INSTALLED_APPS unlike
other horizon related projects, but it needs more investigation
and this patch does not touch it at the moment.
[1] http://docs.openstack.org/infra/manual/creators.html#enabling-translation-infrastructure
Change-Id: I93609a1af08b5a6f64fc43c16722f4c759f68302
Passing --upgrade to setup_develop completely breaks sahara-dashboard
plugin devstack as it conflict with constraint environments.
It is a mistake of commit 65f0836936
Change-Id: Idd095ed3a26d7d2d94b0befbd4b711e34efc199c
* Use setup_develop to install python module as most projects do.
This also makes translation management easier in development.
* Deploy 'enabled' files into horizon local/enabled directory.
* collectstatic and compress are no longer required during horizon
plugin installation. The timing of horizon installation was fixed
in https://review.openstack.org/#/c/257744/
Change-Id: I256a91025dafa3a5f9a7a52408fe82e04c29a019
sahara-dashboard can now be installed as a devstack plugin by
following the instructions added to the README.rst
Change-Id: I45e0353da99feb908fcd96fe4dac4d6b820f1705
Luigi Toscano