Mox3 was listed in requirements, but it not actually used
anywhere. Removing it from test-requirements so it does
not look like it is being used to help with removal from
global-requirements.
Change-Id: I1273ece298ac3de3e372ba23b6e999c858402ff3
Use namespaces when referencing python packages. Also, as per
https://review.opendev.org/#/c/527320/, replace all references to
django.core.urlresolves with django.urls.
Change-Id: I6460d0734aa11ffa44f259baa7155d2a202f7162
The initial checkin of the stable/train branch referenced the
wrong stable branch (stein) in the gate jobs. This patch fixes
that.
Change-Id: Ia54a1de30683f7f448f3708ce0b04fb5293a2653
Previous patch fixed the form but did not fix yet
another bug in the original implementation of the
patching of the create instance workflow. Namely,
the patched logic was always assuming the need for
a PTG, and would override the supplied network
arguments. This is being fixed here.
Also caps the cmd2 dependency whose latest version is
incompatible.
Change-Id: If0fff67cd2b811853a632055d1609b6057769bb8
Patching of the create instance dialog needs to happen
only when invoked from the GBP "create member" workflow.
An earlier commit c0f6597c7f
fixed this for launching from the Compute menu but left out
the launching option from the Network Topology (under
the Network option).
An attempt was made to change the logic in a way that the check
happens for the GBP URI (instead of the logic to check for all
other URIs from where it can be launched), however that did not
work. Hence the comment on evolving to a more resrtictive logic
has been preserved in the code.
Also fixes tox.ini
Change-Id: If124971c1954cb85fce244440e2408cd58ced3e6
An earlier commit:
d86c6ea3cc
patched the "create instance" dialog such that even when
its launched from Project -> Compute -> Instances, the "GBP" workflow step
is shown instead of the expected "Networks" and "Ports" steps. The former
should be shown only in the case when the dialog is launched from GBP and
the original behavior should be preserved when the dialog is launched from
Compute. This is being fixed here.
Change-Id: Ie9af2cca451942d51ea254bdf14bc2345743f938
This fixes a number of issues which were found during
testing (GBP UI is broken without these fixes):
1. Convert present/past action to methods
Table data_type_singular and data_type_plural attributes are
deprecated. action_present and action_past strings are also
deprecated. They are all being converted here.
Changes made per commit in the Horizon:
c393a6651f
2. Fixes to allow use of Django 1.11
There were some undocumented widgets used in Horizon, and in turn by us,
that were cut from Django 1.11. We are restoring some of the utility
methods that were dropped, but we are still using.
Changes based on the commit in Horizon:
52150749a6
3. Drop Django 1.7 vestiges
url template tag is no longer required to imported from the future template tag library.
Changes based on the commit in Horizon:
f2b2289b4a
Change-Id: I424cdaedd04ef9e887e34a09478e2c572d1ffd78
Modifies the create member button in group details to use the compute launch
instance AngularJS based launch dialog. The dialog itself is changed through
the Angular API to replace standard networking pages with a group setting page.
Change-Id: Ib9f5b601939ed9e8258e4eab2f2180efc98378ae
Closes-Bug: 1582457
Implements an angular-python bridge that allows django/horizon forms
to use transfer tables (as seen in other parts of horizon, e.g.:
computes launch instance dialog) as form fields. These fields are
then used to replace the multi select combos boxes in the different
GBPUI dialogs/forms.
Note 1: The add and remove policy rule set actions in group details
"Provided Policy Rule Set" and "Consumed Policy Rule Set" are currently
unaffected. These two tabs do not follow the "standard" horizon method
of adding and removing items through one transfer table; instead,
it uses two different dialogs to carry out each operation separately.
This should be addressed in a separate patchset.
Note 2: This is a bit of a stop gap measure, as horizon is slowly moving
away from native django based dialogs and wizards to AngularJS. The goal
should ultimately be to do the same in GBPUI.
Change-Id: I01c9dc08b1bc35309d62eb3da0bd26f3795867ab
Partial-Bug: 1712814
Removes unused templates and simplifies remaining templates and views by extracting common logic
in the same way as the previous partial patch for this bug did.
Change-Id: I832a7ab88e99103b9e6abdfd8be44fcd8bee1a11
Closes-Bug: 1710852
Co-Authored-By: viktor.krivak@ultimum.io
Templates used throughout GBP UI were not properly updated
for several OpenStack releases. This update removes unused templates
and reduces unnecessary complexity. Additionally, this fixes problems
with missing non-ajax version of templates, that breaks standalone
rendering of forms and workflows (e. g. when opened in new tab or after
re-login when session expires during while working with forms).
This commit fixes ony policytargets section.
Partial-Bug: #1710852
Co-Authored-By: Marek Lycka <marek.lycka@ultimum.io>
Change-Id: I4f8f6cef04fd514eccb428e8a89cc030ae99cb2a
Calling patterns method in urls.py files is redundant and as of Django
1.8 also deprecated. In order to support Django 1.10, we need
to update urls.
Closes-Bug: #1710857
Change-Id: I57a33d3ac166256fb18cc16665894c0c48c77af5
This commit fixes the delete buttons in all of the GBPUI panels where checked items were deleted even when using individual (row) delete actions.
Change-Id: I4ac44bda1baf28b5056d07adf1236b9a43fbad4c
Closes-Bug: 1707896
In cases where the member is not created via the UI, the metadata used
for filtering the members on retrieval is not added to the VMs. Hence any
member VMs that are created outside the UI are never shown in the member list.
This patch fixes this issue by reinstating the earlier filtering logic to
find the member VMs belonging to a particular PTG in case the above metadata
is not present.
Change-Id: Ic2154d04c292269dd7cb46edf19f3a7f3bbe1364
Closes-bug: 1691598
Description text in Add/Remove Policy Rule Set referenced Consumed PRS,
description for editation of groups inconsistent with UI.
Change-Id: Ided11d0df69515e9b75da9e7d6990a0b543e5c27
By default all PTGs will be listed as available groups
and allows to select any groups.There is no way to specify
PTGs to not consider while launching a member.
As a solution, providing optional configuration parameter
GBPUI_HIDE_PTG_NAMES_FROM_MEMBER_CREATE to specify
which group to excule based on group name regex match.
This optional parameter can be specified in openstack dashboard
local settings(openstack_dashboard/local/local_settings.py)
e.g.
GBPUI_HIDE_PTG_NAMES_FROM_MEMBER_CREATE =
['*.backup_network_group_name', '*.another_group_name']
With the above definition, create member form wont show PTGs with
name ending 'backup_network_group_name' and 'another_group_name'
Change-Id: Ibda517bb8bb747e9cf205979521c6903fdef8d17
Closes-Bug: #bug/1639137
ignoring stitching subnets by catching exception
while associating fixed ip with corresponding
subnet id
Change-Id: Ieccecc41b2608102c201f48fcd1c831db19882a6
User should not be able to associate ip address
from either stitching PTGs or subnets, hence
hiding the same during member launch.
Also moving out fixed ip address from square
brackets and changing square brackets to
function brackets around 'Click to Set IP'
and 'Click to Edit IP'
Change-Id: Ib64604801530c244cc469d75dd5fb2065316ac11
Closes-Bug: #1626903
Nisar