charm-openstack-dashboard:stable/20.02

Branch merges

Related source package recipes

No recipes using this branch. (?)

Create packaging recipe

Related snap packages

Related charm recipes

bfbcc90... by Alex Kavanagh on 2020-03-31

Fix CONFIGS=None issue with action openstack-upgrade

When the CONFIGS was made lazy in the charm, unfortunately, some of the
work wasn't carried through correctly to the openstack-upgrade action
code. This patch corrects that. Tested manually as okay.

Change-Id: I095613ef2eca62da5fae5462e76fa83926d2e80a
Closes-Bug: #1869865
(cherry picked from commit 851821ff39a66fcdd75b414427b64c2979ba8bb7)

03cd9d1... by Liam Young on 2020-02-17

Updates for stable branch creation

Set default branch for git review/gerrit.

Switch amulet tests to stable.

Switch zaza bundles to stable charms.

Switch to using stable charm-helpers branch.

Change-Id: I0c35cb696b86a2fc909d74703e0b99eec7162150

b33a77a... by Liam Young on 2020-02-04

Charmhelper sync for 20.02

Change-Id: Ib6ef3bb40a790762fef42f1a65138ab38bb545fd

3387091... by Zuul <email address hidden> on 2020-01-31

Merge "Do not access DB when it is in maintenance mode."

1e2515e... by Alex Kavanagh on 2020-01-28

Fix issue with plugins breaking packages

The core issue is that the plugin had no way to signal to the
principal charm what packages needed to be installed, and crucially,
which conflicted with the packages that the plugin needs to operate.
The referenced bug exhibits this issue in that, on install, a package
is removed by the plugin, but the principal charm "doesn't know". Then
on upgrade, the principal charm re-installs the package, and breaks
the plugin.

This patch allows the plugin to signal which packages it requires to
operate via the dashboard-plugin interface. This ensures that when
the openstack-dashboard charm upgrades it already "knows" what a
plugin needs and acts accordingly. Equally, plugins can change their
requirements and this patch allows them to update/remove/install
packages as needed.

The local_settings.py is already controlled by the principal, and this
just shifts absolute control over packaging to the principal as well.
The plugin charm's purpose is to indicate packages and config to the
principal.

Note. There should be no backwards compatibility issues with this
change. If a plugin doesn't notify the principal of any packages then it
won't take any action. This does mean that the openstack-charm should
be upgrade prior to any plugins that gain this feature.

Also disable disco test as disco is EOL.

Change-Id: Ib3fc0b0525dabf70f45fd050af2ed05ba31129b9
Related-Bug: #1853851

c9e844a... by Liam Young on 2020-01-30

Do not access DB when it is in maintenance mode.

If the database is in maintenace mode do not attempt to access
it.

Depends-On: I5d8ed7d3935db5568c50f8d585e37a4d0cc6914f
Change-Id: I91d3f858888a169cf85d51533a54ef37d7a72c58

de4e9ec... by Liam Young on 2020-01-23

When resuming, exclude haproxy

When resuming services exclude those managed by hacluster, in
this case haproxy. If pacemaker lacks quorum it may shut haproxy
down which will cause this charm to error.

Charmhelper sync included to bring in required
get_managed_services_and_ports method.

Change-Id: I6f997df31922b6090e5b4b1daeec342a044be5c3

0496ab7... by Corey Bryant on 2020-01-17

Sync charm-helpers for Ussuri/Focal release and version details

Change-Id: I4e9ca451157527ca0f19ef981970c5447d510e92

8ec3598... by Zuul <email address hidden> on 2020-01-16

Merge "Add disable-instance-snapshot config item"

03cb557... by Alex Kavanagh on 2020-01-09

Add disable-instance-snapshot config item

This patchset adds the disable-instance-snapshot config item that
controls the "disable_instance_snapshot" dictionary item in the
LAUNCH_INSTANCE_DEFAULTS setting in local_settings.py

Change-Id: Ic15f60517ed8a7f67704b15f4b42baabe74f83c6
Closes-Bug: #1818221