[AppFramework] Application configuration is not re-applied on new nodes if configuration key has not been changed
Bug #1634206 reported by
Alexander Tivelkov
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Murano |
Fix Released
|
Undecided
|
Serg Melikyan | ||
Newton |
New
|
Undecided
|
Alexander Tivelkov |
Bug Description
In application development framework the application may define its "configuration key", i.e. signature of application's configuration. If it hasn't been changed since the previous deploymen, the configuration should not be re-applied during subsequent deployments.
This feature should not affect the new nodes added to server group (e.g. by a scale out action), however for now it affects them: when a new node is spawaned and if the configuration key is defined and hasn't been changed, the configuration is not applied on new nodes.
Changed in murano: | |
assignee: | nobody → Alexander Tivelkov (ativelkov) |
summary: |
[AppFramework] Application configuration is not re-applied on new nodes - if lod configuration has not been changed + if configuration key has not been changed |
description: | updated |
description: | updated |
Changed in murano: | |
assignee: | Alexander Tivelkov (ativelkov) → Serg Melikyan (smelikyan) |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/387606
Review: https:/