config: add notification-format option
This require a change in charm-helper: https://github.com/juju/charm-helpers/pull/310/ Related-Bug: 1825016 Signed-off-by: Sahid Orentino Ferdjaoui <sahid.ferdjaoui@canonical.com> Change-Id: I7887b5f06e194450ec69d8adc5d6fd7f84fee6fe
This commit is contained in:
parent
089823288a
commit
599245bbd1
15
config.yaml
15
config.yaml
|
@ -514,4 +514,17 @@ options:
|
||||||
an unmount of the corresponding device so that it can be used for as the
|
an unmount of the corresponding device so that it can be used for as the
|
||||||
backing store for local instances. This is useful for testing purposes
|
backing store for local instances. This is useful for testing purposes
|
||||||
(cloud deployment is not a typical use case).
|
(cloud deployment is not a typical use case).
|
||||||
|
notification-format:
|
||||||
|
type: string
|
||||||
|
default:
|
||||||
|
description: |
|
||||||
|
There are two types of notifications in Nova: legacy notifications
|
||||||
|
which have an unversioned payload and newer notifications which have
|
||||||
|
a versioned payload.
|
||||||
|
.
|
||||||
|
Setting this option to `versioned` will use the versioned
|
||||||
|
notification concept, `unversioned`, the unversioned notification concept
|
||||||
|
and finally `both` will use the two concepts.
|
||||||
|
.
|
||||||
|
Not setting this option will use the default configured in charm template
|
||||||
|
which is currently `unversioned`.
|
Loading…
Reference in New Issue