The QoS panel is not complete and so is being disabled by default.
The merged part is working though, and users can view and delete trunks.
The panel can be re-enabled by deleting the DISABLED flag from the
file enabling the panel:
openstack_dashboard/enabled/_1510_project_network_qos_panel.py
Implements: blueprint network-bandwidth-limiting-qos
Change-Id: I5870885487ceeb2a73752a08945ca7de6ced423b
Unfortunately we missed to complete the trunks panel until the Pike
freeze. Since it is incomplete we better disable it by default.
The merged part is working though, users can view and delete trunks.
The panel can be re-enabled by deleting the DISABLED flag from the
file enabling the panel:
openstack_dashboard/enabled/_1500_project_trunks_panel.py
Change-Id: I956c10666f0449478e3489f13d7eff049ad95890
Partially-Implements: blueprint neutron-trunk-ui
Add details link to the trunk panel to show details of the given trunk,
like the subports list, with port_id and segmentation details.
Co-Authored-By: Bence Romsics <bence.romsics@ericsson.com>
Change-Id: I9000e2907a8f188d5e72e36818b7171f35158eb9
Partially-Implements: blueprint neutron-trunk-ui
Currently themes machinery works in such way that if we rely on
default theme in our branded theme, we have to include them both into
AVAILABLE_THEMES setting, otherwise default theme assets will be
unavailable and the branded theme assets compilation will fail. On
the other hand, mentioning them both leads to theme picker being
shown - which we would like to avoid (per marketing wish).
SELECTABLE_THEMES setting was added to allow limiting the user facing
themes by configuration.
Closes-bug: #1564543
Co-Authored-By: Ivan Kolodyazhny <e0ne@e0ne.info>
Change-Id: Ic00a9201d2d352685b1089a37a25987b75d6636d
* This patch adds support for the virtio-forwarder VNIC type.
* The virtio-forwarder VNIC type has been added as another option for
setting the "binding:vnic_type" property on a port. This requests a
low-latency virtio port inside the instance, likely backed by hardware
acceleration.
* The documentation for OPENSTACK_NEUTRON_NETWORK/supported_vnic_types
has been updated to clarify the term "supported VNIC types".
Unfortunately, the VNIC binding happens at scheduling and error
reporting in core Nova and Neutron is not optimal in this case.
* Corresponding python-openstackclient change:
https://review.openstack.org/#/c/483532/
* Corresponding neutron-lib change:
https://review.openstack.org/#/c/483530/
Signed-off-by: Jan Gutter <jan.gutter@netronome.com>
Closes-Bug: 1705548
Depends-On: I28315fb12f62dc7d52d099c211086b2b81eca39a
Change-Id: I02dc3581de8f31c659e545e340cbdf6a1b2bb837
The main purpose of prelude is to describe release highlights.
The current usage of prelude looks random and there is no need for
individual release notes to use prelude section.
This commit cleans them up.
Also add a note on this to the contributor guide.
Change-Id: Ib72a3f4fc1bac2befd900249d07f5d67a56079f3
At now, the horizon plugin framework does not allow to override default panel
settings by same filename. The embeded enabled files are always processed,
so this leads to make operators difficult to change the order of panels
from the default. In the original design of the plugin mechanism,
we allow to override embeded enabled files by local/enabled files.
For more detail, see bug 1700325.
This commit changes import_dashboard_config to override an embeded enabled
file by specifying a enabled file in local/enabled with the same filename.
Closes-Bug: #1700325
Change-Id: Id6b15848206a684eca850a8f510a8ba1608bb7bf
doc8 is a linter for documents and used in openstack-manuals.
It is better to enforce document linters for simple checking.
The current rules are really simple like:
- line length check (80 chars)
- new line at the end of file
Change-Id: I3810df521068ffc97e25a5fc56b72397bf9783bc
This commit is primarily a reorganisation fo our settings documentation.
The aim is to move away from the horizon / openstack_dashboard / django
distinction, which makes little sense to non-devs. This will be replaced
by a split between general horizon settings, service-specific settings,
and upstream Django settings. as well as organising the settings in
each section alphabetically. The aim is to promote discoverability of
settings for operators.
This patch also improves visiblity of deprecation, adds missing
tags (versionadded, seealso, deprecated, versionchanged), and
updates content where necessary. Some missing settings were added,
and many settings were also updated to reference other relevant
settings.
Change-Id: Idd496af7d4fe7d242772bb402d22c54c18f05d51
Implements: blueprint pike-docs-overhaul
It should be together with related change in django-openstack-auth, if
specified it will change the default service region calculation: it
will be taken from this setting (on a per-endpont basis) instead of a
value stored in cookies. This value is still checked for sanity,
i.e. it should be present in Keystone service catalog.
Change-Id: I7e36f766870793f3e8fc391a06f0ee49deaa7add
Related-Bug: #1506825
Closes-Bug: #1703390
On clouds that use domain-specific Identity configuration[1], a user
must provide both their username and domain in order to log into
horizon. Without this patch, users must be aware of their domain's name
and enter it into a text box at login. This is sensible on public
clouds, because supplying potential domains to an unauthenticated user
exposes too much information about other customers and makes potential
attacks easier. On private clouds, however, it is a hinderance to
usability. For example, when migrating from a single-domain
configuration to a multi-domain configuration, users must now guess or
be informed of their domain in order to enter it in the text box. As
another example, when keystone domains are mapped to Active Directory
domains, the user may not be used to having to know their AD domains and
would prefer to select a likely one based on their geographical location
or department from a dropdown menu.
This patch adds the config file examples and documentation for new
config options, "OPENSTACK_KEYSTONE_DOMAIN_DROPDOWN" for enabling a
dropdown menu instead of a textbox when MULTIDOMAIN_SUPPORT is enabled,
and "OPENSTACK_KEYSTONE_DOMAIN_CHOICES" for providing domains to choose
from. The behavior changes corresponding to these new options are
implemented in django_openstack_auth in a corresponding patch.
[1] https://docs.openstack.org/developer/keystone/configuration.html#domain-specific-drivers
Change-Id: I71d64182524d1f54745d9e42347b3a605fa2a920
Depends-On: Ie0a7e36b9975342fab81ddebb87880608d3ef187
* Nova 2.9 is confusing. It is not a nova version.
2.9 is a version of Nova API.
* It is better to say "Create Volume" in which panel.
"Create Volume in Launch Instance form" would be clear to readers.
* Fix typo in the drop-nova-network release note.
Change-Id: If967892a95a798349591b17c623f289ee882a6fe
Added a column to show the locked status on project/admin instances table.
There will be a locked or unlocked icon with help tooltip if nova 2.9 or
above is used. See openstack_dashboard/api/microversions.py
Added the locked field on project/admin instance details panel.
Change-Id: If31ae281d2782c71cd6112f3bd6228647a6130e4
Closes-bug: #1593903
tenant_quota_usage() is used to retrieve quota and usage
to determine if a resource can be created.
However, tenant_quota_usage retrieves quota and usage for
all resources and it can be a performance problem.
This commit allows to load quota and usage only for resources
which are actually required.
Closes-Bug: #1675504
Change-Id: Iab7322a337a451a1a040cc2f4b55cc319b1ffc4c
This patch adds the QoS panel which displays Neutron QoS policies.
This patch allows read only view of the policies, displaying the name,
id, description and shared status of each policy. Policy actions and
rules to be added in follow-up patches.
To test:
Neutron's QoS plugin must be enabled in your setup.
To enable the QoS plugin in devstack please add the following lines
in the local.conf
enable_plugin neutron git://git.openstack.org/openstack/neutron
enable_service q-qos
and rebuild your stack (./stack.sh).
Create some qos policies via CLI (neutron qos-policy-create policy1).
now you can list the policies using this patch.
Based on initial commit: https://review.openstack.org/#/c/247997
Co-Authored-By: Masco <mkaliyam@redhat.com>
Co-Authored-By: Rob Cresswell <robert.cresswell@outlook.com>
Change-Id: If46aeb04879d91a1a9305a94a23cecea2041d378
Implements: blueprint network-bandwidth-limiting-qos
Added two charts for Number of Volumes and Total Volume Storage quotas
on Angular launch instance modal when cinder is enabled.
The charts reflect the volume usage of the new instances to be created
as the user changes the configuration on the modal.
Updated the chart styling for the charts to align better.
Change-Id: Ie744ada2317624153fcfdf9abdf4d7b26996a35e
Partially-implements: blueprint launch-instance-volume-quotas
This patch adds the ability to configure the default "create volume"
value when launching an instance with Cinder enabled.
Co-Authored-By: Rob Cresswell <robert.cresswell@outlook.com>
Closes-Bug: 1678109
Change-Id: I272f7f1b20cc1276976c464a82d1776de92d17e7
enable_firewall and enable_vpn settings have been deprecated
since Juno release, but they have not been dropped yet just because
we need a lot of changes in unit tests if dropped.
The situation is resolved by the parent commit and we can now drop these
settings safely. We can control whether a specific panel should be
enabled or disabled via the pluggable panel mechanism ("enabled" dir).
Also clean up enable_lb which has gone several releases ago.
Closes-Bug: #1687185
Change-Id: I83fa48c5d9568a00294be7cd5f43ef181bc1f28d
The current default settings of openstack_dashboard OPENSTACK_ENDPOINT_TYPE
has two default values 'publicURL' and 'internalURL' and this leads to
require both endpoints in deployments.
Having two default values for one setting is confusing. The comment in
local_settings.py says OPENSTACK_ENDPOINT_TYPE defaults to publicURL
and operators does not think internalURL is used.
I believe there is no negative side because if operators want to
deploy horizon out side of their OpenStack clouds they use publicURL
and if they want to deploy horizon behind load balancer or something
they would use internalURL as OPENSTACK_ENDPOINT_TYPE.
This also help the current devstack setup which only configures
public endpoint (interface) and Horizon does not work by default
for Identity dashboard.
Closes-Bug: #1686717
Change-Id: If5c7bbc5188f6df65661c41d777a9c7846fe9008
python-openstackclient, shade, openstacksdk and Ansible's OpenStack
modules all support reading client config information from a file called
clouds.yaml instead of from environment variables set from openrc files.
Unfortunately, the only thing horizon currently offers for download is
old-style openrc files.
Add support for downloading clouds.yaml files.
Change-Id: I0611dd44524b746ad993bff7435ec8628a83a762
Neutron allows setting port or protocol wildcard by not specifying any value
for them.
Example, these are allowed by neutron:
neutron security-group-rule-create --direction egress <sgid>
neutron security-group-rule-create --direction egress --protocol tcp <sgid>
Specifying '-1' for IP protocol means a wildcard IP protocol.
validate_ip_protocol is updated accordingly.
'All ports' choice is added to 'Open Port' field.
Change-Id: I4a7262eda89e3206c743fee14c78aa6b49308ce6
Closes-Bug: 1669467
Previously the available language list is maintained manually.
This commit change horizon to check translation message catalog
is available for each language and generate the language list
automatically. settings.LANGUAGES is still used to determines
the initial set of languages and now defaults to the list provided
by django.
Change-Id: I9d9c934beebd7a641e2feb0d5cdfa839e0efa3c3
Closes-Bug: #1675298
action_present and action_past "attributes" have been deprecated
since the middle of Mitaka development cycle. There is no consumer
in the horizon repository and the deprecation warnings were emitted
appropriately so horizon plugins are expected not to use them already.
Now we are in the early stage for the next release (Pike),
so it is time to drop the deprecated way.
Change-Id: Ia93a6b17561068777845366b2b4c57b7144fab9f
There's some vendor specific code still lingering from several cycles
ago. This patch removes all usage of it, all related tests, and all
default settings.
Implements: blueprint horizon-vendor-split
Change-Id: Ic0bb84f547b07b130480e587bd365f6e7805dfb5
As Nova's API is unified to os_compute_api, the API policies are also
updated to use this format, Horizon needs to use Nova policy enforce
rules in the codebase. This patch also update nova_policy.json using
oslo-config-generator for Nova policy file.
Co-Authored-By: Rob Cresswell <robert.cresswell@outlook.com>
Implements: blueprint update-nova-enforce-policies
Change-Id: Id7d01a39930c88592301a5035f0befe5293a78fa
Admin dashboard shows too many panels now.
This commit introduces panel groups for Admin dashboard
as we do for Project dashboard.
The new order of admin panel groups are:
Compute, Volume, Network and System.
Note that the slug of "System" panel group is not changed
to avoid breaking horizon plugins which register panels to
Admin System panel group.
Implements blueprint reorganize-admin-dashboard
Change-Id: I533e60f7cbfab2539b9f8aa7044f7234165f2518
Now it is possible to enable/disable port security in Horizon, when
the port-security extension is available.
Closes-Bug: #1634877
Change-Id: I6b17b49bca8e5d1a2aff10fe613ecd70590c097b