Comment 16 for bug 1348548

I was inaccurate with conclusion made at https://bugs.launchpad.net/fuel/+bug/1348548/comments/14.
Both 'stop' and 'freeze' policy showed no problems with corosync cluster after either in partitioned or in recovered state.
The only caveat is what some nodes will end up with stopped corosync service once the cluster recovered from partitioning - and the only way to handle it is either reboot them manually, or configure fencing. Please see http://goo.gl/Xd4KhQ for details. The spreadsheet linked inside was updated and double-checked :-)
I will provide the 3rd case as well - ignore policy, it'd nice to have it...