charm-nova-compute:stable/20.02

Branch merges

Related source package recipes

No recipes using this branch. (?)

Create packaging recipe

Related snap packages

Related charm recipes

6ce5162... 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: Ia527fb9020fa576e5b77dd9452278efb08681789

0120c59... by Stamatis Katsaounis <email address hidden> on 2020-02-10

Add live_migration_scheme to Train configuration template

Use live_migration_scheme instead of deprecated live_migration_uri
which is not set by charm code on versions greater than Ocata.
Furthermore, remove the check from every template >= Ocata because
live_migration_uri is never set by nova_compute_context.py (L205)

Change-Id: Id19a0e72dad28fbd729002ec1dfb7cf4acfcf2bc
Closes-Bug: #1862659
Signed-off-by: Stamatis Katsaounis <email address hidden>

3b4aca0... by Liam Young on 2020-02-04

Charmhelper sync for 20.02

Change-Id: I44c0e7b4fa85b59415078c449962551b0cb64657

508f2d0... by Corey Bryant on 2020-01-17

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

Change-Id: I72a772446c0b3bdd22fc635d67a694b5a5b54692

73b0eaa... by Syed Mohammad Adnan Karim on 2020-01-14

Updated AppArmor profile to allow vm migration

Updated AppArmor profile usr.bin.nova-compute to allow access to
required resources for vm migration, resizing, and evacuation.

Change-Id: Ieb196b337cf03eac798124f4da71d1ebb5707253
Closes-Bug: 1846300
Related-Bug: 1859236 # Duplicate Bug

e397383... by David Ames on 2020-01-10

Get DNS domain for nova metadata

Get the DNS domain for the dhcp_domain setting for nova metadata over
the cloud-compute relation from nova-cloud-controller.

Fixes Bug #1805645 when using provider networks with no network node.

Change-Id: Iaba14e6939ab5d488c6299ce5cb33e26f757cf95
Partial-Bug: #1805645

1869bfb... by Frode Nordahl on 2020-01-10

Use hosts official name for FQDN

The current implementations use of a specific interface to build
FQDN from has the undesired side effect of the ``nova-compute`` and
``neutron-openvswitch`` charms ending up with using different
hostnames in some situations. It may also lead to use of a
identifier that is mutable throughout the lifetime of a deployment.

Use of a specific interface was chosen due to ``socket.getfqdn()``
not giving reliable results (https://bugs.python.org/issue5004).

This patch gets the FQDN by mimickingthe behaviour of a call to
``hostname -f`` with fallback to shortname on failure.

Add relevant update from c-h.

Needed-By: Ic8f8742261b773484687985aa0a366391cd2737a
Change-Id: I82db81937e5a46dc6bd222b7160ca1fa5b190c10
Closes-Bug: #1839300

b4e6d2c... by Frode Nordahl on 2020-01-10

Fix python shebang for hugepagereport action

Change-Id: I643524f3ebf3f26a0a1f2bff03f9516ef0269da8
Closes-Bug: #1859186

49bf54c... by Zuul <email address hidden> on 2020-01-08

Merge "Fix for not restarting subordinate services on managed upgrade"

dc8a6d0... by Alex Kavanagh on 2020-01-07

Fix for not restarting subordinate services on managed upgrade

This fixes the referenced bug by ensuring that the action does initiate
remote restarts for container scoped related units.

Change-Id: I149b753355b64113adfd8fd4eea972978b7ed20b
Closes-Bug:#1835557