This mail is generic to all openstack service and explained the problem with 
respect to heat here.

I have come across the situation where, updates are involved in the heat db 
model and corresponding code changes in the heat-engine component. Now assume 
that in a given deployment, there are two heat-engines and customer wants to 
update as follows:

1.       Run db sync and update the first heat-engine and restart the 

2.       Don't touch the second heat-engine.

In this scenario, first heat-engine will work properly as its updated with new 
db change done by the db sync. But second heat-engine is not updated and it 
will fail. To address this problem, would like to know if any other service 
came across the same scenario and a solution is already provided? Thanks.

Kanagaraj M
OpenStack-dev mailing list

Reply via email to