Added option to sync vm config via csync2

When save_config_on_stop AND sync_config_on_save is enabled the config gets synced with csync2 -x vm.conf to all nodes configured in csync2. This will make sure that wherever the VM starts it will inherit the config changes.

On Tue, Nov 18, 2014 at 07:45:03AM -0800, David Vossel wrote:
> > @@ -424,6 +436,11 @@ force_stop()
> >  	return $OCF_SUCCESS
> >  }
> >  
> > +sync_config(){
> > +	ocf_log info "Syncing $DOMAIN_NAME config file with csync2 -x ${OCF_RESKEY_config}"
> > +	csync2 -x ${OCF_RESKEY_config}
> 
> Also, we need some sort of error/warning message output if csync fails.  That error doesn't need to cause the 'stop' action to fail,  we just need to know something bad happened.

Yes, better that the stop action doesn't fail.

However, the next start on the other node will use the previous
configuration. Is that OK or at least mostly OK? Or should in
that case the RA refuse to start the VM? And what to do if it's
a failover (which would in this case obviously fail)?

Note that the logs are almost never read.