Hi all, As discussed in the Vancouver Summit, we are going to drop the bay lock implementation. Instead, each conductor will call Heat concurrently and rely on heat for concurrency control. However, I think we need an approach for state convergence from heat to magnum. Either periodic task [1] or heat notification [2] looks like a candidate.
[1] https://blueprints.launchpad.net/magnum/+spec/add-periodic-task [2] http://lists.openstack.org/pipermail/openstack-dev/2015-March/058898.html --hongbin If we use periodic task to sync state from heat to magnum, I think we should make periodic task a independent process and magnum-conductor only operates heat stack. How to make periodic task high available？ 1.We can run several periodic tasks. 2.Or we can use a leader selection mechanism to make only a periodic task running and other periodic tasks waiting. Shall we make periodic task a independent process? How to make periodic task high available? Regards, Hua Wang
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
