[AppFramework] Application configuration is not re-applied on new nodes if configuration key has not been changed

[Alexander Tivelkov]

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.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/387606

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/387606
Committed: https://git.openstack.org/cgit/openstack/murano/commit/?id=d698116869beaf3411bcf6f0c0292cbdf6e8e69b
Submitter: Jenkins
Branch: master

commit d698116869beaf3411bcf6f0c0292cbdf6e8e69b
Author: Alexander Tivelkov <email address hidden>
Date: Mon Oct 17 20:09:25 2016 +0300

    Configuration is now properly applied to new nodes

    If the configuration of software component has not been changed, but a
    set of nodes in the server group has been modified, the component's
    default checkClusterIsConfigured method will now properly return true,
    thus the configuration will be applied on newly added nodes.

    This is achieved by storing instance ids as part of component's
    'configuration' attributed stored for its server group.

    Change-Id: Ic8bbddc577518071d90a6e33518156047a1d2e2e
    Closes-bug: #1634206

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/murano 3.1.0 release.