* Add gettext package for development environment
* Use 'apt install' command instead of legacy 'apt-get'
Change-Id: I2bd06b7708a72a1986e75968aee79ba27457bf62
Several teams are defined in the horizon project both in
gerrit and launchpad. It would be nice to document them.
Change-Id: Ic88912f6216bcef020a0839380f6528705a0a1a7
This commit updates the horizon contributor docs to follow
what the community goal [1] recommended.
* Reorganize doc/source/contributor/contributing.rst to the format
suggested in the community goal template.
* Cleanup obsolete information and topics covered by the general
OpenStack contributor guide.
* Move contributing.rst to the top in TOC of the contributor guide
as it is considered as the entry point for new contributors.
* Sync CONTRIBUTING.rst at the top level directory with the
community goal template.
* Update the core reviewer expectation along with PTL expectation.
[1] https://governance.openstack.org/tc/goals/selected/ussuri/project-ptl-and-contrib-docs.html
Story: #2007236
Task: #38525
Change-Id: Idce7fc08e7fdf854d8a7bca55169d18403362c45
Ussuri community goal "Project specific contributor and PTL docs"
want us to use doc/source/contributor/contributing.rst as an entry
point, but the current contributor/contributing.rst in horizon
contains a lot of information.
Before updating the file to satisfy the community goal criteria,
this commit reorganize the contributor doc.
It splits the existing contents in contributing.rst into pieces.
Change-Id: I8aa9a310a99e0eed5a93ed040a02a2829ee09bf7
pytest has a different way to run specific test from django test runner.
pytest migration patch did not update our document.
This commit is a follow-up patch.
Change-Id: Ifed388928f159a5a602088b2cfbf7f601d044387
There is still a single user of mox but all other references to this can
be removed. Do just that.
Change-Id: I611573a41c47e99e41a54bf53cea55322a493de1
Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
We already have a template 'horizon-non-primary-django-jobs'
to test horizon and plugins with non-primary django versions,
but we still need to update tox.ini in all horizon plugins
whenever we change Django versions used.
This commit prepares per-Django environment in the zuul job.
Per-Django tox environments like py3-{dj111,dj20,dj22} are
no longer needed. It would be a big merit that we will no longer
need to update tox.ini in all horizon plugins.
The downside is that we do not provide a convenient way to
test it locally, but I think it can be covered in the document.
Change-Id: I726b19130ee9e7d06eb33231071c2673cfd3a49f
The goal definition in the TC repo [1] defines the completion criteria.
We have already completed 1, 2, 3 and partially 4 in [1].
This commit completes 4 (requirements.txt etc) and 5 (release note).
Python dependency in the installation guide is updated.
Django support plan in Ussuri is updated as well.
References to python 2.7 in the document are updated as well.
[1] https://governance.openstack.org/tc/goals/selected/ussuri/drop-py27.html
Change-Id: I0383920e32e053e1611519be774fab8dec124ccc
The keystone doesn't use 5000 port anymore from Newton version. And all
the references should be changed together.
Change-Id: I3f02686ab5b3abf48f129fde92e90427ca148317
Curretnly, features from N-3 release are assumed as a baseline
in the horizon development policy document.
LTS of Ubuntu Cloud Archive supports upgrade from N-4 to N.
If we assume a case where horizon is upgraded first, N release of
horizon needs to be able to run with N-4 release of back-end services.
The difference of N-3 and N-4 would be small, so it sounds reasonable
to assume features from N-4 release.
N-4 is chosen considering LTS support in the major OpenStack distributions:
* Red Hat OpenStack Platform (RHOSP): X -> X+3
https://access.redhat.com/support/policy/updates/openstack/platform/
* SuSE OpenStack Cloud (SOC): X -> X+2
https://www.suse.com/releasenotes/x86_64/SUSE-OPENSTACK-CLOUD/8/#Upgrade
* Ubuntu Cloud Archive: X -> X+4
https://www.ubuntu.com/about/release-cycle
Change-Id: If7007e9d5b912b48d6bf3e4fac5decc53cd8388b
This list was tested on a fresh Ubuntu 18.04 and CentOS 8
environments without Devstack.
Co-Authored-By: Akihiro Motoki <amotoki@gmail.com>
Change-Id: Ib009e036d9fcebdad8faeb5d30ed14c525fabf10
contributor/ref/ directory contains the module reference and
local.conf was the only exception. "Topics" section looks
more appropriate place to have a guide to configure DevStack
for horizon.
Change-Id: Ibfafe7c608753633e0b78765073afa2924602551
* Remove sample devstack configuration from local.conf.
DevStack document provides the full set of configuration.
There is no need to have sample configurations and descriptions
in horizon.
* Change default passwords to match passwords used in the OpenStck CI.
It helps developers reproduce CI configurations in local envs.
If these passwords are different, we need to (re)configured
passwords for MySQL, RabbitMQ and so on.
Change-Id: I9540df7a1390aa0411713ea80d711e8cfc09292d
This commit tries to summarize the approach of ini-based-configuration
effort and the preparation for it.
Part of blueprint ini-based-configuration
Change-Id: I810a2f3c5d13fe70d840aa6460cb902f566c29b8
In Train, we will use python 3.6 and 3.7 for python3 runtime
in our gate jobs [1]. This commit drops python 3.5 info
and adds python 3.6 and 3.7 info.
[1] https://governance.openstack.org/tc/reference/runtimes/train.html
Change-Id: I8f024505ed9b37c9f2b480f49b5000d75da42cc0
Due to [1] patch it's better to update [2] file.
Otherwise it create confusion to a new devloper if use
"tox -e runserver" for developments.
[1] https://review.openstack.org/#/c/630790
[2] openstack_dashboard/local/local_settings.py.example
Change-Id: I2146b33f46c417c5f1d61a4958336c92f0c03e9c
This commit tries to capture basic policies on back-end feature
supports and so on that have not documented so far.
Change-Id: Ic1dc6029ce2a1cf54d313e8320b7ca206f5dfaea
The directory structure after executing the commands is
different from the document provided.
This patch make it consistent.
Change-Id: I5a78765c4760d3bc0b27a0f67f2d47960fd4824d
{% include %} syntax cannot have a newline.
Closes-Bug: #1774054
This commit also cleans up several things.
* setup.cfg: Rename "classifiers" to the correct keyword "classifier"
* setup.cfg: Add Python 3 classifier
* Quote literals
Change-Id: I14c2217a69ea489c72b311b26b5eb4a5e4865059
The django form field default is "required=True", so there
remove the redundant "required=True" in doc.
Change-Id: Id88e0a4d8e97e78ce8e6be760d67f0db3d69f50c
There was a typo in keystone's policy files, and it has been fixed in
Keystone already, we should also fix it to match.
Change-Id: I41e4381765f3bfc5988ca235e6cbeb6d1ba62fc2
Closes-bug: #1703369
Since 'tools/install_venv.py' has been removed during refactor[1].
This paragraph displayed in quickstart may cause some confusion to
someone who new to horizon, so remove this paragraph.
[1]6529cd1eb8
Change-Id: I302ef1f30781ce916c7309ebfa349fbedf8dd5a6
* topics/policy.rst and settings.rst both contain settings related
to policy engine. All settings are now defined in settings.rst.
* Add contents to maintain policy files. The process after switching
to policy-in-code is covered.
* Add subsections to "How to Utilize RBAC"
Change-Id: I912543ad6bef02e37ba4e2fec27dcdff61f89d23
This patch also adds checks for executable files in
pep8 job.
nose ignores executable files by default, so it is important
to ensure executable flag is not set for test files [1].
openstack_dashboard/test/test_plugins/panel_tests.py was not
tested actually and it was broken. This commit fixes it too.
[1] http://nose.readthedocs.io/en/latest/usage.html#cmdoption-exe
Co-Authored-By: Ivan Kolodyazhny <e0ne@e0ne.info>
Change-Id: I3a124fa2f9f0676b2b43a094e32e3d8b18fa6005
The keystone API version 3 has become the default API version
for a long time and our CI already uses keystone v3 API only.
In addition, our documentation recommended to use the cached session,
so switching the default API version to 3 does not hit the limitation
on the maximum size of session data when using the cookie-based
sessions.
This is based on django_opensatck_auth review
https://review.openstack.org/#/c/158384/
Implements blueprint: default-keystone-api-3
Change-Id: I79e9fbd3567cc69468694dbf043fecf422347c7e
According to bug 1737242, tox -e manage collectstatic/compress
can fail with a customized settings file (for example, a setting
which uses db backend for caching). After discussion with the bug
reporter, he develops a theme using a production settings file
and runs into a trouble. It looks better to use python manage.py
directly to avoid further confusion.
Change-Id: If34ba249745a110268cc99213cc404697b03495f
Closes-Bug: #1737242
Orchestration tab in the admin info panel needs a discussion.
It seems not to be covered by heat-dashboard yet.
blueprint heat-dashboard-split-out
Change-Id: I56e6edb1f2ac72e2f42d0e9f3291308e67f24cad