Comment 41 for bug 1394188

Let me clarify the "remove it from corosync cluster in runtime without restarts of corosync/pacemaker"

A node will be removed from corosync cluster *only* after erased by Fuel orchestration, so there will be no corosync service running already. So that would allow us to not care about stopping the corosync service prior to do the node removal from the corosync cluster.