In Zed cycle, we have dropped the python 3.6/3.7[1] testing
and its support. Add release notes and update the python
classifier for the same.
[1] https://governance.openstack.org/tc/reference/runtimes/zed.html
Co-Authored-By: Ghanshyam Mann <gmann@ghanshyammann.com>
Change-Id: Iebd573f07fde5cae14b48a89c7292a923ff03aee
This repo is now testing only with Python 3, so let's make
a few cleanups:
- Remove python 2.7 stanza from setup.py
- Add requires on python >= 3.6 to setup.cfg so that pypi and pip
know about the requirement
- Remove obsolete sections from setup.cfg
- Update requirements, no need for python_version anymore
- Use newer openstackdocstheme version
- Remove install_command from tox.ini, the default is fine
- Use TOX_CONSTRAINTS_FILE instead of UPPER_CONSTRAINTS_FILE since
the later is obsolete
- Increase lower constraints to fullfill package requests
Change-Id: I7126c2646f272b3f8c568630293a194bc5ba98a9
Now that we are running the Victoria tests that include a
voting py38, we can now add the Python 3.8 metadata to the
package information to reflect that support.
Change-Id: I4a3aab7b687fb57368a67f7b76577e4ccb167278
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
- 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
The new openstack-discuss mailing list is going to replace few
mailing lists, including openstack-dev.
Change-Id: I4c886a417c2bd1ebcd4c57b4872265a689019b57
The gating on python 3.4 is restricted to <= Mitaka. This is due to
the change from Ubuntu Trusty to Xenial, where only python3.5 is
available. There is no need to continue to keep these settings.
Change-Id: Ic28c0a6e8db6d6360c00ec834e474826cc3ada27
Python 3.3 is not supported from Mitaka, as per Infra.
This patch removes the support for the same.
Change-Id: Ib92e8ee8c7e7ba43537772b30d98e67b3df17685
Now that there is a passing gate job, we can claim support for Python 3.5
in the classifier. This patch also adds the convenience py35 py34 venv.
Change-Id: I75cae6b3a810a955b4d81dcda9c9bf920f9e6bd7
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
OpenStack projects are no longer being tested under Python 2.6, so
remove the trove classifier implying that this project supports 2.6.
Change-Id: I9c30cfbc633c5316bc5a69fd55ebd8fec489aed6
This plugin moves the current content from the horizon repo to this
plugin repo. The code has been tested in a devstack install using the
following steps:
1. packaging the plugin: "python setup.cfg sdist"
2. pip installing the tar.gz in the resulting dist directory
3. a. (temporary step) remove existing sahara enabled files from
horizon
"rm openstack_dashboard/enabled/_18*.py"
b. finding the install location and changing to it
"cp sahara_dashboard/enabled/* /opt/stack/horizon/local/enabled"
4. in /opt/stack/horizon
a. python manage.py collectstatic
b. python manage.py compress
5. restarting the horizon server
Additionally, you can run the unit tests by:
./run_tests.sh
Note: added script to programmatically remove the old configuration
files from the targeted horizon install, either in venv or system
install.
Known issues:
1. running tests locally emits missing neutron service messages.
2. plugin code for devstack needs to be added
3. README is inadequate
4. integration tests are still in horizon repo
5. local copy of run_tests is heavy weight, but a better solution is
not available currently.
6. localization tooling and strings
Change-Id: Icdce2d3e945e612d368556dd5cea1930194c7b67
Clearing out all of the old code from the Sahara
dashboard repo in preparation for bringing the new
code back into the repo for the Mitaka release.
Change-Id: I83cb932c35987ea80ac9233bd355355398b9164b
* Renaming savannadashboard directory to saharadashboard which
also includes updating all of the places where that package
is referenced.
* Also including some renaming in the documentation.
* Changing the name of the top level panel to Sahara
* Changing the name of the top level Dashboard class to SaharaDashboard
Partial-Implements: blueprint savanna-renaming-dashboard
Change-Id: If51b85d22ec7798c214c56189359260198e69374
'universal=True' means app supports py2 and py3 which isn't checked for savanna
dashboard (and horizon), so, my bad, it should be reverted atm.
W/o 'universal=True' wheel bdist still could be built.
This reverts commit 89c4cdb772
Change-Id: If206a1778f00555845b8c559b6f9ae8b8a91a745