Octavia Dashboard used protected barbicanclient API that seems to be
broken now. Fixing that by replacing barbicanclient by future-proof
openstacksdk.
Closes-Bug: #2023534
Change-Id: I882869ef0f5b6381372e3447af7ca1981ca02d65
The oslo.log library is not required by octavia-dashboard itself. Thus
can be removed from requirements.
Change-Id: I9a8b64c83667d9fca50433efe568b7a3072e4c5a
Bump openstacksdk to 0.53.0, it provides the tls_enabled flag for
Octavia pools.
Story 2008368
Task 41277
Change-Id: I41559e3f2d13e5adbb850f28f058b72404e28124
This repo does not support Python 2 anymore, so we don't need
six for compatibility between Python2 and 3, convert six usage to Python
3 code.
Change-Id: I66624801278c2fbedfe29ed6166f525b3cef1d34
Django 1.11 ends its extended support in April 2020 (which is before
Ussuri release), so horizon drops Django 1.11 support in Ussuri.
tox envs for non-primary Django versions are no longer needed in tox.ini
as testing environments for non-primary Django versions are setup in
the zuul jobs now.
horizon>=17.1.0 is required to use Django 2.2. requirements.txt and
lower-constraints.txt are updated accordingly. for more info. please
refer [1].
Depends-On: https://review.opendev.org/#/c/700733/
[1] https://etherpad.openstack.org/p/Enable_Django22_support_in_Horizon_Plugin
Change-Id: If7c7ce79594449637655c4832db50c2c243ce1c0
Horizon test setting no longer depends on nose and related stuffs.
This commit cleans up nose related dependencies.
The change was made in horizon Rocky-3,
so horizon 14.0.0.0b3 is required at least.
Change-Id: I3b9a51d79de04279e1872cc41a2bb7c69a0f08f8
oslo.log, six, and python-keystoneclient where missing from the
requirements.txt file.
Change-Id: Ia8f85314b730458b0aaf4167a0be2f25f9bfc8a6
Story: 1688211
Task: 5667
This patch coverts the Octavia dasboard over to use the openstack SDK
and the new Octavia v2 API.
It's octavia-dashboard, now with less neutron-lbaas (ok, no neutron-lbaas)
Change-Id: I71fd67128210c3ff365838414920a1de1883ebd2
This adds support for the TERMINATED_HTTPS listener protocol when
creating a new listener. When this option is selected the SSL
Certificates tab is displayed after the Listener Details tab and
allows selecting one or more available certificates. The user must
have barbican available and authority to list certificates and
secrets. Certificate containers must be created in barbican before
they will be available when creating a listener.
Partially-Implements: blueprint horizon-lbaas-v2-ui
Change-Id: Ia9312fa865d85ca977c1daea347d97bd69e9c5ba
Tom Weininger