Description text in Add/Remove Policy Rule Set referenced Consumed PRS,
description for editation of groups inconsistent with UI.
Change-Id: Ided11d0df69515e9b75da9e7d6990a0b543e5c27
(cherry picked from commit d6c00c4048)
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
(cherry picked from commit f4deab2aae)
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
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
As part of #1609363, links was added to associate
fixed IP while creating member for each group.
As part of this bug, sepated IP address association
links from group name as mentioned below
To set IP address : <group name> [Click to Set IP]
To edit associated IP:
<group name> [<ip address>, Click to Edit IP]
Change-Id: Ia51224aeb23559dd2ff6d0faa3cf5c6b9d4e3097
Closes-Bug: #1611908
Due to change in horizon base url from / to /dashboard,
javascript files are not getting loaded
Change-Id: I7bd713124ffaff4d3a884a1ba40b1bdd1342439e
Closes-bug: #1538679
OpenStack projects are no longer being tested under Python 2.6, so
remove the trove classifier implying that this project supports 2.6.
Change-Id: I437995c0d450c01586bf66740b4dd618d6c3dc19
Added Networking Tab to member create work flow.
Deault provider PTG will be shown as selected
NIC, additionally user can select other PTGs
to to add multiple NICs
Change-Id: I3ceadc0f2ca9de6d9be2c4349eba6623a9aa4cd4
Closes-Bug: #1491540
Added support to associate mulitple external
segments during create & update.
In L3Policy form, changed the external-segment
widget to MultiSelect to remove/unset
external-segment.
Made external segment IP optional.
Displaying all External segments
in L3Policy.
Closes-Bug: #1505348
Closes-Bug: #1506145
Closes-Bug: #1499935
Closes-Bug: #1499829
Closes-Bug: #1504884
Change-Id: I200e8d1fb4f354db3e8fa85c1458371628fe1dc2
Added support to associate multiple ext-segments
to external group while creation and also made
subnetID as optional field in ext-segment
creation.
Change-Id: I3cd591caede3a513e95c670235db47ed72249353
Closes-Bug: #1505416
We were getting this failure because of
incorrect query for Network service policy
from form context
Closes-Bug: #1503833
Change-Id: Ic8f565cb6bb05bef8e4fb9cdf70acb85a88a8c3c
When passing the source type of the block device mapping when booting
from a volume snapshot, we need to specify "snapshot" instead of
"volume".
This fix is the same as the one applied in horizon:
a1db17aeff
Change-Id: I4b110af9956773e1ce53dbce91557ac26f171c1a
Closes-Bug: #1499418