This update is to ensure that the Zuul Canonical CI builds the charm
before functional tests and ensure that that artifact is used for the
functional tests. This is to try to ensure that the charm that gets
landed to the charmhub is the same charm that was tested with.
Change-Id: Ic9e267db4934cb95125eebb2ff3b1ca09d64e003
Switch to use Keystone v3 clients for Queens and setup
domains etc for new demo user.
Change-Id: I4a90a28212ec6e1a8e9f348b1318722141f35d2c
Requires: https://github.com/juju/charm-helpers/pull/119
During the recent py3 conversion of the charm a couple of places
where the charm writes text in binary mode were missed. This
fixes that problem. Without this fix the charm errors with:
"TypeError: a bytes-like object is required, not 'str'"
Change-Id: I5c2af1dce12092c1ba1be4b4ad9a50261000e886
Previously if enable-live-migration was true and migration-auth-type
was anything other than "ssh" then migration setup would be invalid.
The change puts the charm in a blocked state to make it clear that
the migration settings are not valid.
Change-Id: I796b54e9a08e8eab5c2b316a2aff0b29ee7e6bd9
Closes-Bug: #1431685
Provide the weight option to the Ceph broker request API for requesting
the creation of a new Ceph storage pool. The weight is used to indicate
the percentage of the data that the pool is expected to consume. Each
environment may have slightly different needs based on the type of
workload so a config option labelled ceph-pool-weight is provided to
allow the operator to tune this value.
Closes-Bug: #1492742
Change-Id: Ia9aba8c4dee7a94c36c282273a356d9c13df7f75
Fixes to nova-network and nova-api service restarts
Charm helpers sync to bring in the AppArmorContext class
Create specific service ApiAppArmorContexts
Add service specific templates for apparmor profiles
Add aa-profile-mode in config.yaml
Apply the apparmor profile as requested: disable, enforce, complain
Add aa-profile-mode change test to amulet
Charm-helpers sync to pull in AA Profile context changes
Change-Id: I18aff4bfe131010521ea9ff544c6bf76f888afa6
Reverting initial support for AppArmor as this change had
some un-intended side-effects and the profiles still need
further work.
This reverts commit b08fe04906.
Change-Id: I8538b491bc0c6bd3ad02ac0b1d4fda190b137c41
Charm helpers sync to bring in the AppArmorContext class
Create specific service ApiAppArmorContexts
Add service specific templates for apparmor profiles
Add aa-profile-mode in config.yaml
Apply the apparmor profile as requested: disable, enforce, complain
Change-Id: I886520d9e8296d2fcf0305dd021270c8530d2813