commit 8a422879594d9f8492ab6b9222b6842bfb9c2b70
Author: Igor Gajsin <email address hidden>
Date: Fri Mar 17 19:23:27 2017 +0300
Reorder configs_query by time
There is the possibility to change OpenStack config after deployment.
Changes could be applied per role. And in the case of multiple roles
on a node, many changes could pretend to be applied. I.e. if we have
a config for the role 'compute', a config for the role 'cinder' and
a node with role 'cinder+compute' we have to choose one of them.
Previous decision was 'sort it in the lexicographical order', so it
applies 'cinder' then --- 'compute'. It is contra intuitive. The best
option is applying to a node the last related config, to new config
overlaps old ones.
Reviewed: https:/ /review. openstack. org/450779 /git.openstack. org/cgit/ openstack/ fuel-web/ commit/ ?id=8a422879594 d9f8492ab6b9222 b6842bfb9c2b70
Committed: https:/
Submitter: Jenkins
Branch: stable/newton
commit 8a422879594d9f8 492ab6b9222b684 2bfb9c2b70
Author: Igor Gajsin <email address hidden>
Date: Fri Mar 17 19:23:27 2017 +0300
Reorder configs_query by time
There is the possibility to change OpenStack config after deployment.
Changes could be applied per role. And in the case of multiple roles
on a node, many changes could pretend to be applied. I.e. if we have
a config for the role 'compute', a config for the role 'cinder' and
a node with role 'cinder+compute' we have to choose one of them.
Previous decision was 'sort it in the lexicographical order', so it
applies 'cinder' then --- 'compute'. It is contra intuitive. The best
option is applying to a node the last related config, to new config
overlaps old ones.
Change-Id: I7db388ca3baeb3 51adc9fdb70c55b 0be50fafe48
Closes-bug: #1671521