| 2016-10-17 17:01:48 |
Alexander Tivelkov |
bug |
|
|
added bug |
| 2016-10-17 17:01:55 |
Alexander Tivelkov |
murano: assignee |
|
Alexander Tivelkov (ativelkov) |
|
| 2016-10-17 17:02:03 |
Alexander Tivelkov |
nominated for series |
|
murano/newton |
|
| 2016-10-17 17:02:03 |
Alexander Tivelkov |
bug task added |
|
murano/newton |
|
| 2016-10-17 17:02:08 |
Alexander Tivelkov |
murano/newton: assignee |
|
Alexander Tivelkov (ativelkov) |
|
| 2016-10-17 17:02:36 |
Alexander Tivelkov |
summary |
[AppFramework] Application configuration is not re-applied on new nodes if lod configuration has not been changed |
[AppFramework] Application configuration is not re-applied on new nodes if configuration key has not been changed |
|
| 2016-10-17 17:03:08 |
Alexander Tivelkov |
description |
In application development framework the application may report its "configuration key", i.e. signature of application's configuration. If it hasn't been changed since the previous deployment it does not get re-applied during subsequent deployments.
It 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 overriden, the configuration is not applied on new nodes. |
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 deployment it does not get re-applied during subsequent deployments.
It 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 overriden, the configuration is not applied on new nodes. |
|
| 2016-10-17 17:03:52 |
Alexander Tivelkov |
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 deployment it does not get re-applied during subsequent deployments.
It 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 overriden, the configuration is not applied on new nodes. |
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. |
|
| 2016-10-17 18:23:14 |
OpenStack Infra |
murano: status |
New |
In Progress |
|
| 2016-11-17 00:48:19 |
OpenStack Infra |
murano: assignee |
Alexander Tivelkov (ativelkov) |
Serg Melikyan (smelikyan) |
|
| 2016-11-24 07:06:46 |
OpenStack Infra |
murano: status |
In Progress |
Fix Released |
|
