high: conntrackd: allow probe to return OCF_RUNNING_MASTER
dnsupdate: resource agent for IP take-over via dynamic DNS
High: clvm: Properly detect directory for vg tools
Low: IPaddr2: fix error msg from manual clone/incarnation # era

Relevant commits:
- resource-agents: 8fd391725b83b5874daef826b4e4f76892207192
- pacemaker:       7df298fc25de2e89afcae330f6e2a4e6a351489a

Signed-off-by: Jan Pokorný <jpokorny@redhat.com>
Low: tomcat: Autodetects another possible tomcat startup script used in rhel6
Merge pull request #413 from davidvossel/master

kamailio cleanup and refactoring
Merge pull request #410 from davidvossel/tomcat-default-script

Low: tomcat: Autodetects another possible tomcat startup script used in rhel6
Merge pull request #409 from davidvossel/clvm-tools-dir

High: clvm: Properly detect directory for vg tools
High: nfsserver: preserve statd directory permissions during sm-notify or else lock recovery fails

sm-notify drops root privileges and executes as the rpc user.
If we do not maintain the statd ownership correctly sm-notify
can not access the lock state data.
Combined udptcp check can produce wrong test result, if tcp fails.
Merge pull request #415 from seabres/kammonerr

kamailio: Combined udptcp check can produce wrong test result, if tcp fails.
High: vm.sh: Monitor kvm resources without requiring libvirtd to be up
High: vm.sh: 'no_kill' option for preventing auto destruction of vm after timeout period
Merge pull request #417 from davidvossel/bz1079039-no-kill-vm

High: vm.sh: 'no_kill' option for preventing auto destruction of vm afte...
High: nfsserver: let systemd service files handle lock notifications
Low: nfsserver: make sure sm-notify can always execute

If a nfsserver restarts on a node without rebooting, the lock
notifications are not sent out properly because of a stale
sm-notify.pid file. In normal non-ha operation, this is to prevent
sm-notify from notifying clients multiple times, but in an ha
environment we need this to occur.
High: nfsserver: Do not fail monitor if lock services are enabled

nfs clients use lock services outside of ha nfs server
High: nfsserver: Re-structure how locking daemons are handled

Previously the nfsserver agent took in what binary to use
in order to send the NSM lock notifications. We don't need to know
what binary to use. It only makes sense to use sm-notify if rpc.statd
is already running as sm-notify re-notifies the clients of a change.
If rpc.statd is down, it has to be started for NSM locking to occur.
By default rpc.statd is going to invoke sm-notify on initialization.

So, if rpc.statd is down. We use rpc.statd to notify on start.
If rpc.statd is up, we use sm-notify to re-notify clients.

I've also made the nfs_ip argument optional. There are use-cases
where we do not want to bind rpc.statd to the floating ip. If no
nfs_ip is specified, rpc.statd binds to the wildcard address.

One more change to rpc.statd has been made. I removed the ability
to accidently execute rpc.statd in the foreground. rpc.statd never
returns. It is a daemon... This would cause start to timeout if
anyone ever set this option and rpc.statd was used to notify
the clients.
Low: nfsserver: better nfs init script auto detection
High: exportfs: Do not fail during monitor and stop operations if dir has trailing slash