nova-compute charm should use unversioned notification format
Bug #1731828 reported by
Nusrath Mohammed
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Nova Compute Charm |
Triaged
|
Medium
|
Unassigned |
Bug Description
nova-compute charm needs a variable to set notification_format (both, versioned, unversioned)
Nova currently generates versioned_
By default, notification_format is set to both and hence the charm needs a feature to set this variable to unversioned until the versioned_
Changed in charm-nova-compute: | |
milestone: | 18.02 → 18.05 |
Changed in charm-nova-compute: | |
milestone: | 18.05 → 18.08 |
Changed in charm-nova-compute: | |
milestone: | 18.08 → 18.11 |
Changed in charm-nova-compute: | |
milestone: | 18.11 → 19.04 |
Changed in charm-nova-compute: | |
milestone: | 19.04 → 19.07 |
Changed in charm-nova-compute: | |
milestone: | 19.07 → 19.10 |
Changed in charm-nova-compute: | |
milestone: | 19.10 → 20.01 |
Changed in charm-nova-compute: | |
milestone: | 20.01 → 20.05 |
Changed in charm-nova-compute: | |
milestone: | 20.05 → 20.08 |
Changed in charm-nova-compute: | |
milestone: | 20.08 → none |
To post a comment you must log in.
I think we know what format should be used, so providing a configuration option makes little sense; lets just set the right values in the nova.conf templates for each supported release; when ceilometer does support the versioned format, we can just switch back to 'both'.