Added directions on how to run collectstatic and compress as part of the
install process. Fixing obvious typos as well.
Change-Id: Ia51bb7bb644dc213b3ec3fd3866633700a73c7f9
Closes-Bug: 1392804
By default modal form is closed after clicking outside of it on a dark
backdrop (data-backdrop="true"). For the forms with a lot of fields
this could lead to a loss of data the user had entered before he has
unintentionally clicked outside of the form. So more preferable option
for such forms (and workflows/client-side modals) would be
data-backdrop="static".
DocImpact
Change-Id: I56fca9131a4e4d3991d53184ee1332e84138cdc2
Partially-Implements: blueprint form-template-to-view
Related-Bug: #1062065
Replace URLs for workflow documentation to appropriate parts of the
OpenStack Project Infrastructure Manual.
Change-Id: Ibf8fb2f6a1e8b0f80db6ab1180894c235046e785
Horizon does not support Python 2.6 anymore starting with Kilo and might
not work correctly with it, so remove the classifier.
Change-Id: Idb2a044968bf35c1fbe4ab42188c6f7df096d442
In the tutorial "Building a Dashboard using Horizon" there is a bug
in the view.py example that in case of exception return a var that
has not been defined.
Closes-Bug: #1388576
Change-Id: I271a30215bb245ffa65ee76e86027ae003816a15
It is painful to increment the venv version manually because
requirements.txt and test-requirements.txt are now updated by cron job.
This commit changes run_tests.sh to just store two requirements
files to .venv/environments file and check if it is up-to-date.
(Note that the environment cache file is moved to .venv directory
as there is no reason to store it in the top directory.)
Closes-Bug: #1376485
Change-Id: Ie44ccf6e2e65890baca3f316468254b600c518b1
Cinder API v1 was deprecated in Juno and is being removed in Kilo.
Implements: blueprint horizon-cinder-v2-preferred-version
Closes-Bug: 1376424
Change-Id: I9bbdf1753a06d33b441a85ff448f475545eafc80
In the context selection dropdown, there is currently an always disabled
link to do more advanced filtering. The original intent was to open a
modal to do more advanced context selection. With the use of RBAC in a
previous bp, the Identity->Projects panel is always accessible. This
panel provides the entire project list for the user. We can just use
this to provide the larger project list to select from.
Change-Id: I0d6674e75785206f3be48c8bf004a29906bb6860
Closes-Bug: #1382650
* Exclude test files from source code index
* Add an index to jump to sub indexes in source code index
* Ensure the order of source code index by using an array
rather than a dict.
Change-Id: I5c28a3e29c9c0b0332732d3f598030a77536563a
Added documentation for auto_fade_alerts.
Also added to the OpenStack section documentation for:
OPENSTACK_API_VERSIONS,
OPENSTACK_KEYSTONE_MULTIDOMAIN_SUPPORT,
OPENSTACK_KEYSTONE_DEFAULT_DOMAIN,
OPENSTACK_KEYSTONE_BACKEND,
CONSOLE_TYPE,
TROVE_ADD_USER_PERMS,
TROVE_ADD_DATABASE_PERMS.
In the Django section, added ALLOWED_HOSTS
and a note about use of SECRET_KEY.
Closes-Bug: #1221115
Change-Id: I16596fef2af62b892cef00ab25e2bfe4a80e1c65
* Add "Using Horizon" section to the docs, which describes
how to install and configure Horizon. It is for operators
who install Horizon from source code.
* Clean up README.rst as much of the information is out-of-date
and most of it is covered by the developer docs.
* Minor update of page titles.
Change-Id: I09aab0d0bc47e07c8d663e7f7b5801e456434950
*Updating to avoid use of manage.py directly.
*Making it more DevStack friendly.
*Adding a sample DevStack local.conf to allow for exercise Horizon
against more services.
*Added simple developer instructions so new developers aren't tempted
to work on the DevStack instance of Horizon.
Change-Id: I0840c63183e7cec3b08e4f2ce208479ff7552f60
Dashboards are now configured via the pluggable dashboard/panel
mechanism and the order can be specified in the pluggable config.
On the other hand, we have HORIZON "dashboards" and its tuple order
overrides the order specified in the pluggable config.
It is confusing to be able to configure the order of dashboards
in two places, and we no longer need to have "dashboards" config
parameter in settings.py and a sample local_settings.py.
* If HORIZON_CONFIG contains "dashboards" and update_dashboards
is called, a deprecation warning will be displayed. It is useful
to warn operators to change OpenStack Dashboard settings.
* HORIZON_CONFIG "dashboard" parameter itself still works and
there is no chnage in the behavior, so it is a safe change
and have no upgrade impact.
* This change also removes default_dashboard from settings because
it can be configured via pluggable dashboard config too.
After removing "dashboards" config, the order of the dashboards
are now controlled by the order of openstack_dashboard/enabled and
"Identity" dashboard is displayed before "Settings" dashboard
in the navigation menu.
Closes-Bug: #1366270
Change-Id: Ifa35128691c4fa4843b3c3c051682392e59905a6
HA (high availability) mode support is one of the important topics in
Neutron Juno, and this patch adds HA router mode support to Horizon.
This commit also changes the default value of enable_distributed_router
in the example local_settings.py to False. In Juno release of Neutron,
the distributed router and L3 HA mode cannot be enabled at the same
time and only L3-agent deployment with L3 Router service plugin
support both features. Thus I believe it is reasonable to make both
options default to False to avoid unnecessary confusions to operators.
Closes-Bug: #1370110
Change-Id: I77b0292b761f08b4580846f6d58443f7df9a1f6b
With https://review.openstack.org/#/c/116509/ ,
django-openstack-auth will support a new option for the token hash
algorithm. This adds the documentation to Horizon's local settings
example file.
This is for security hardening. The token hash algorithm defaults
to MD5, which is considered too weak due to the potential for hash
collisions. Some security standards require a SHA2 hash algorithm to
be used.
DocImpact
SecurityImpact
Change-Id: I6774b9b7215d191259586e4721e357487bb777cd
Closes-Bug: #1174499
We have two imports with #noqa: django.conf.urls.patterns and
django.conf.urls.url however using them is a standard way of creating
any urls.py module. So there are over 150 imports in Horizon code
where #noqa could be replaced with two lines in list of import_exceptions.
Change-Id: I81c3290e0dc958b5037dd6a87e44df18adfbe751
Nova currently expose an api to let the users update
the flavors metadata so horizon should expose
this functionality. At the same time Glance is exposing
a metadata dictionary in Juno, where users can register
the key/value pairs that describe their cloud deployment.
This patch uses the glance metadata api to expose the available
metadata and the nova api to update the aggregates metadata.
Implements: blueprint glaance-metadata-flavors
Co-Authored-By: Santiago Baldassin <santiago.b.baldassin@intel.com>
Co-Authored-By: Pawel Skowron <pawel.skowron@intel.com>
Co-Authored-By: Pawel Koniszewski <pawel.koniszewski@intel.com>
Co-Authored-By: Michal Dulko <michal.dulko@intel.com>
DocImpact:
New UI. FLAVOR_EXTRA_KEYS setting deprecated.
Change-Id: Ica9d3d06314a4d5afa77f644bd1f8900a1c328f7
Remove intersphinx from the docs build as it triggers network calls that
occasionally fail, and we don't really use intersphinx (links other
sphinx documents out on the internet)
This also removes the requirement for internet access during docs build.
This causes docs jobs to fail because we error out on warnings.
Change-Id: I71e941e2a639641a662a163c682eb86d51de42fb
Related-Bug: #1368910
In Juno, Glance is providing a metadata definitions catalog[1][2] where
users can register the available metadata definitions that can be used
on different types of resources (images, artifacts, volumes, flavors,
aggregates, etc). This includes both simple tags and key / value pairs
(properties, specs, etc).
This widget will get the metadata definitions from Glance
and will let the user add the metadata to the resource being edited.
It provides value validation as well as description information
about the metadata.
An implementation for Images is included in this patch. Additional
patches will be made for other resource types.
This patch also removes Edit Image Custom Properties screen as new
widget provides the same functionality. To avoid regressions owner
property is added to Image Detail screen.
********************** TESTING **************************
You can test this code with Glance patches by following
the instructions at the bottom of this etherpad:
Go to: https://etherpad.openstack.org/p/j3-glance-patches
*********************************************************
[1] Approved Glance Juno Spec:
https://github.com/openstack/glance-specs/blob/master/specs/juno/metadata-schema-catalog.rst
[2] Glance PTL Juno Feature Overview:
https://www.youtube.com/watch?v=3ptriiw1wK8&t=14m27s
Implements: blueprint tagging
DocImpact
Co-Authored-By: Santiago Baldassin <santiago.b.baldassin@intel.com>
Co-Authored-By: Pawel Skowron <pawel.skowron@intel.com>
Co-Authored-By: Travis Tripp <travis.tripp@hp.com>
Co-Authored-By: Szymon Wroblewski <szymon.wroblewski@intel.com>
Co-Authored-By: Michal Dulko <michal.dulko@intel.com>
Co-Authored-By: Bartosz Fic <bartosz.fic@intel.com>
Co-Authored-By: Pawel Koniszewski <pawel.koniszewski@intel.com>
Co-Authored-By: Heather Whisenhunt <heather.whisenhunt@hp.com>
Change-Id: I335d4708f5ce8afe58fb88dbe9efd79e2c04fc9e
As reported in the bug, the documentation needs to be updated with
a list of browsers we support. This patch adds faq entry and updates
information for contributing.
Change-Id: I6218194d031bc6b47a0fd13e5e11749df441398b
Closes-Bug: 1359246
Neutron features like LBaaS, FWaaS or VPNaaS are provided as
extensions in Neutron. This commit changes these features are enabled
only when they are included in the extension list from Neutron.
It also change the default settings of enable_lb/firewall/vpn to True.
The default of these settings were set to False to avoid confusion to
users because LB/FW/VPNaaS are optional features in Neutron. By this
commit corresponding features in Horizon are enabled dynamically, so
it is reasonable to change the default to True.
This commit introduces Horizon version of override_settings
"update_settings" decorator which allows override an item in dict.
Django original override_settings replaces a dict completely,
however OpenStack dashboard setting has many dictionary configuration
and there are test case where we want to override only one item
in a dictionary and keep other items in the dictionary.
This version of override_settings allows this.
DocImpact
Implements blueprint neutron-feature-control-with-ext-list
Change-Id: I19424d448c800524de0ee8ac769974272dbb84a0
We where able to set the CONSOLE_TYPE in local_settings.py, but not able to
deactivate it.
We added a new option to CONSOLE_TYPE which is None.
To keep the legacy behaviour, CONSOLE_TYPE defaults to 'AUTO' and has to be
explicitly set to None to deactivate the console.
implements bp hide-vnc-console-access
Change-Id: Id23f3d5e37509b846858d480ad781f2b4ffc3590
If the config option 'enable_router' is set to False,
Floating IP features are disabled when Neutron is enabled.
It does not affect when Neutron is disabled.
It also adds unit tests for api.network.servers_update_addresses
which is affected by this change.
Completes blueprint hide-router-panel-by-config
Closes-Bug: #1292022
Change-Id: Ib63c6a0e7bb5661d4a60d10a1722fdad978b50bb
Neutron setup allows operators not to enable Router feautre
(by not using Router service plugin in neutron.conf) and
some Neutron plugin does not support Router feature.
According to bug 1350639 there is also a case where operators
want to disable Router panel from their policy.
It seems nice we have a option to control Router panel.
This commit add a new option 'enable_router' to OPENSTACK_NEUTRON_NETWORK.
The default is True since router feature is enabled in most deployments
and it is the current default behavior of Horizon.
If this option is False, Router panel will disappear.
blueprint hide-router-panel-by-config
Partial-Bug: #1292022
Closes-Bug: #1350639
Change-Id: If90517bd35c5b18173c54c14a1ba229f97ba4797
Neutron DVR implementation allows to change router type from
centralized to distributed. This commit adds "Edit Router" form
which is not implemented so far to allow this feature.
This commit also adds:
- admin_state field to the router detail.
- documentation on a new option enable_distributed_router
Completes blueprint enhance-horizon-for-dvr
Change-Id: I4b46e44c417726217ed034e305827b102ba656f8
This adds the ability for admins to set the provider network
settings when creating a network. This includes the network type,
physical network, and segmentation ID. These options will only be
available if the provider network neutron extension is supported.
Change-Id: I6108504a92a32f067cf151ec103171a7bbb601df
Implements: blueprint quantum-network-provider-types
Closes-Bug: 1223360
This is the final fix to re-enable flake8/pep8 check in the gate.
E265 errors in doc/source/conf.py are also fixed.
Imports with "from xxxx import (xxxx)" style cannot pass "tox -e pep8"
though they pass "run_tests.sh -p". Newlines with backslash escape
is used in this commit to pass it.
The reason needs to be investigated later.
Change-Id: Ic0d765d404212d13f678b2a3aef7b9612bf5238d
Closes-Bug: #1347472
The existing tutorial is outdated, hard to follow and does not
work.
Update or rewrite the steps of the tutorial to create a dashboard,
a panel, a tab group, a tab and a table which contains some data
from backend a table which contains some data from backend.
Make sure the steps work.
Updated the brief explanation as well.
Closes-Bug: #1298490
Change-Id: I7c6769fa6b8cd5488afc03e8a284342549a6745f
