Cinder consistency group has been replaced by the generic group feature.
Horizon support of the generic group (in the project dashboard) is
available since Rocky release and it covers all existing support
for consistency group in horizon.
The consistency group support is horizon was marked as deprecated
in Stein release [1].
This commit drops the consistency group support.
[1] https://review.openstack.org/#/c/626846/
Change-Id: I11187d2b03b7e0033a6c6ba3f8be25b8b5e4dd74
This commit allow admin to list/show and delete volume-group snapshots
using horizon dashboard.
Partially-Implements blueprint cinder-generic-volume-groups
Change-Id: If00d156a7a56ed699425b35ac60314c3a8cd049c
This commit allow admin to list/show cinder volume group-type
using horizon dashboard and user can perform the following
table action :
1. group-type-create
2. group-type-delete
3. group-type-update
TODO:
1.group-type-specs support
Partially-Implements blueprint cinder-generic-volume-groups
Change-Id: Iea18913765cda146a0fcae7abe64c999a29cccfe
This commit allows admin to list /show cinder volume groups
using horizon dashboard.
TODO:
1. Modify/Delete volume groups
Partially-Implements blueprint cinder-generic-volume-groups
Change-Id: I75d463204cf83492b30523f46dd0507bbb86dd2e
openstack_dashboard/context_processors.py:94:15: C0122: Comparison should be link['url'] != 'horizon:project:api_access:openrcv2' (misplaced-comparison-constant)
openstack_dashboard/settings.py:467:4: C0412: Imports from package horizon are not grouped (ungrouped-imports)
openstack_dashboard/enabled/_1370_project_vg_snapshots.py:9:0: C0301: Line too long (86/80) (line-too-long)
openstack_dashboard/enabled/_1360_project_volume_groups.py:9:0: C0301: Line too long (85/80) (line-too-long)
openstack_dashboard/usage/base.py:62:8: W0106: Expression "[instance_list.extend(u.server_usages) for u in self.usage_list]" is assigned to nothing (expression-not-assigned)
openstack_dashboard/dashboards/project/images/utils.py:43:12: W0106: Expression "[public_images.append(image) for image in images]" is assigned to nothing (expression-not-assigned)
openstack_dashboard/dashboards/project/images/utils.py:75:12: W0106: Expression "[community_images.append(image) for image in images]" is assigned to nothing (expression-not-assigned)
openstack_dashboard/api/glance.py:47:4: C0412: Imports from package glanceclient are not grouped (ungrouped-imports)
openstack_dashboard/api/cinder.py:60:4: C0412: Imports from package cinderclient are not grouped (ungrouped-imports)
openstack_auth/user.py:358:4: E0211: Method has no argument (no-method-argument)
openstack_auth/user.py:362:4: E0211: Method has no argument (no-method-argument)
openstack_dashboard/api/keystone.py:75:4: C0412: Imports from package keystoneclient are not grouped (ungrouped-imports)
horizon/loaders.py:43:16: W0706: The except handler raises immediately (try-except-raise)
horizon/themes.py:174:8: W0706: The except handler raises immediately (try-except-raise)
Change-Id: I40cf3ffbc4519657e11180d2e2fe7401387c5556
Add RBAC Policies panel to support Role-Based Access Control
functionality.
Implements: blueprint rbac-policies
Change-Id: I883ad629d735dadf49e8bf9c50475050fdfcf797
This commit adds cinder generic group support.
Consistency group support are not shown if the generic group
support is available.
blueprint cinder-generic-volume-groups
Change-Id: I038eeaf2508926f18b6053db0082a8aa3f3e20c6
This patch adds support for creating application credentials in
keystone[1]. Application credentials can be created by any user for
themselves. An application credential is created for the currently
selected project. A user may provide their own secret for the application
credential, or may allow keystone to generate a secret for them. After
the application credential is created, the secret is revealed once to
the user. At that point they may download a clouds.yaml or openrc file
that contains the application credential secret and will enable them to
use it to authenticate. The secret is not revealed again.
[1] https://docs.openstack.org/keystone/latest/user/application_credentials.html
bp application-credentials
Depends-On: https://review.openstack.org/557927
Depends-On: https://review.openstack.org/557932
Change-Id: Ida2e836cf81d2b96e0b66afed29a900c312223a4
This patch adds angular server groups panel under the
project->compute panel group.
To be added in subsequent patches:
- Create Action
- Delete Action
- Detais
To view the server groups panel only the 'ServerGroups' nova API
extension is available.
Change-Id: Ide9f54439c52cce9642c2dd417f9e7a8ad98e846
Implements: blueprint ng-server-groups
Enable admin panel for trunks. For the admin panel the delete action and
the readonly operations are enabled (table view and details view).
Change-Id: Icfc01612cc60798e4b0ff7379a9c8b83d3f1d60b
Implements: blueprint neutron-trunk-ui
Previously _2150_admin_flavor_panel.py used double underscores,
but there is no reason to use double underscores.
This commit makes the enabled filenames consistent.
Change-Id: I9c2de7075c715c1c41798c098e97560c14a554be
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
The trunk panel in the project dashboard is completed,
so this commit enables it by default.
To test it build devstack with neutron trunk support. Eg:
local.conf:
enable_plugin neutron https://git.openstack.org/openstack/neutron
enable_service q-trunk
As long as the 'trunk' API extension is available (openstack
extension show trunk) the panel should automatically appear under
Project/Network/Trunks.
Change-Id: I5f5e343f21ac92e4195825e44f0f3d58b44c134a
Implements: blueprint neutron-trunk-ui
The way of setting default panel of project dashboard and admin
dashboard is the "pluggable settings" mechanism, but for identity
dashboard, a traditional "hard-coded" way is used. It's a good
idea to make it consistent with other dashboards.
Change-Id: I52c584b5ef4981ede981385d39615ab8e7922abe
Closes-Bug: #1717932
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
For now refreshing ngdetails view by browser using F5 key or reload
button, it causes 404 error from django. To fix this issue, this patch
adds the url for '/ngdetails'.
Furthermore, to specify current navigation and to check access grants
to current panel, each access to Horizon django framework needs its
dashboard and panel objects. It means that we need to specify dashboard
and panel that ngdetails view belongs to.
Also, this patch adds the process and settings to specify dashboard and
panel object for each ngdetails view.
Change-Id: I4bcffd2e222ce2df186551cceba0aa38f600d9c8
Closes-Bug: #1681627
'ngdetails' had removed 'project' from its URL as following:
https://review.openstack.org/#/c/396800/
The change for URL is coded in 'openstack_dashboard/static/app/core/
core-constants.module.js'.
Furthermore ngdetails is not linked from any django panels and
doesn't have urls.py for '/project/ngdetails' originally.
On the otherside Angularized panel has routes for details view as SPA.
So 'ngdetails' doesn't need django panel for '/project/ngdetails/'.
This patch removes django panel for '/project/ngdetails/'
Change-Id: I1431c93eeabaa1778a35c0cbacd019b44822edc9
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
Enable display of trunks on the project dashboard.
To test it devstack needs to have neutron with trunk support, eg:
local.conf:
enable_plugin neutron https://git.openstack.org/openstack/neutron
enable_service q-trunk
No special horizon config is needed. As long as the 'trunk'
API extension is available (openstack extension show trunk)
the panel should automatically appear under Project/Network/Trunks.
Co-Authored-By: Akihiro Motoki <amotoki@gmail.com>
Co-Authored-By: Bence Romsics <bence.romsics@ericsson.com>
Change-Id: Iacb83f22f81e09457953622e61065f0bb2c27407
Partially-Implements: blueprint neutron-trunk-ui
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
This edit unfortunately contains more changes than the others
because it effectively merges a bunch of files under
admin/volumes/*.py
Change-Id: I52f3444a92fc83982a95760673419b4b4d746ad3
Implements: blueprint reorganise-volumes
Note that there was state leaking from one of the existing
tests that was relied upon in other tests and moving that test
in the run order caused the others to fail. All related tests
have been altered to not leak state.
Change-Id: I972bc5650fa77044de8a027f570cf2cb41febef8
Implements: blueprint reorganise-volumes
Notes on enabling consistency groups in devstack:
http://docs.openstack.org/admin-guide/blockstorage-consistency-groups.html
You'll also need to modify the local cinder policy file.
Though that's not actually enough to make it work since
devstack only provides the LVM volume type and CGs don't
work with LVM. You can attempt to create CGs, but they
will error.
Change-Id: I0ab541c81570cd5f67bb7d04c01bc92bc5cc3ab5
Implements: blueprint reorganise-volumes
In doing this I found that the permission check on the
project Volume Snapshots table was incorrectly defined,
resulting in always-denied. Removing a level of nesting
in the permission structure fixed it.
Change-Id: I1bc5bd4820700d29861ec1dcd6c87a41b5230266
Implements: blueprint reorganise-volumes
This patch moves the Security Groups tab from the Access and Security
panel into its own panel under the Network panel group. As this is the
last tab in Access and Security, that panel is also removed by this
patch.
Change-Id: Id29c7ce635d46383742aec140def265d4b249aa5
Implements: blueprint reorganise-access-and-security
This patch makes the Floating IPs tab in Access & Security its own panel
under Project > Network
Change-Id: Ibb83ae5a0448d2824c10f867e620cec8219b7b72
Implements: blueprint reorganise-access-and-security
This panel was added in the old style (whole new "ng" panel with its own
enabled file), and since there's no additional code added to it since
then, we should be safe in removing this stub and starting afresh using
our current style (extending the existing panel with ANGULAR_FEATURES setting).
This reverts commit 3b5d9764fe0a93498993124379ea9e95fa58430b.
Change-Id: Ic8c4bffb44126c69fecd56cce6adfb16d30b4e85
This patch moves the API Access view, from a tab on the Access
& Security panel to its own panel under the Compute panel group
Change-Id: I1e523ba2e7e959474c0fc77f8b6c42994a481081
Implements: blueprint reorganise-access-and-security
As part of the breaking up of Access and Security, move the Key Pairs
tab to a new panel under Compute. Separate patches will address Floating
IPs, Security Groups, and API Access.
Fixes include:
- Should be significantly faster to access Key Pairs, as we are no
longer running multiple API calls for the other Access & Security tabs
at the same time. Hooray for speed!
- Should be easier for new users to find where Key Pairs are located.
- Reduce reuse of identical translatable strings
- Use common templates instead of duplication
- Updated policy rules and added missing rules to table get_data
- Small cleanup of the Key Pair download page, which was previously
using modal classes despite not being a modal.
Change-Id: I66f1f65a2cb49bd10e0364b12efba4346f373ed3
Implements: blueprint reorganise-access-and-security