High: nfsserver: Allow dynamically setting rpc.nfsd options.
High: nfsserver: Do not require shared info directory when cloned

The shared info directory is used for Active Passive nfs server
instances. This shared directory allows for client data to failover
and follow the server instance whenever the server is reallocated to
another node.

There is another use case where the nfs server instance does not
fail over, but only the nfs exports move. When this use case is in use
the shared info directory is not necessary. Often this use-case will
involve a cloned nfs server spread out amoung several nodes. We now
allow this agent to work as a cloned resource as long as a shared info
directory is not in use.
Medium: exportfs: allow multiple exports

This commit enables exportfs to export multiple directories.
The parameter names remained the same which makes for an awkward
singular vs. plural in name vs. value. The alternative of adding
another parameter for multiple directories seemed more awkward.
In case of multiple directories, the fsid becomes a start_fsid,
i.e. the fsid of those directories are fsid, fsid+1, and so on.
Dev: exportfs: add ocft testcase for multiple directories
High: nfsserver: Add options for explicitly setting nfs daemon ports

Some deployments require setting predictable port numbers for the
nfs daemons in /etc/sysconfig/nfs. New port specific options have
been added to the ocf agent so the port configuration can live
in the cluster config.
High: nfsserver: Keep statd directories synced with ha backup

This reduces the complexity of the statd/sm and statd/sm.ha directories.
Right before shutdown we sync statd/sm with statd/sm.ha so client statd
info will failover with the server. This prevents us from having to manage
the third backup folder, statd/sm.ha.save.

This also fixes an issue where stale file handlers are encountered
on the client side after nfsserver failover. Now we always postpone
sending lock reclaim notifications until after both the locking
daemons and nfsd are up.
High: nfsserver: introducing nfs_no_notify option for suppressing reboot notifications

There is a use-case for nfsserver that requires NFSv3 reboot
notifications to be posponed until after both the nfs server
and floating IP have been started. The nfs_no_notify option
allows us to suppress the reboot notifications until after
the floating ip has started.
High: nfsnotify: Introducing nfsnotify agent for decoupling NFSv3 reboot notifications out of nfsserver
High: nfsserver: regenerate statd state file before starting nfs

Client will ignore SM_NOTIFY requests if they've already gotten one
from the NSM state id. Make sure to regenerate the statefile during
startup to avoid this.
Low: nfsserver: fix syntax error
Dev: apache: Avoid use of ! to delimit heredocs
Medium: apache: SUSE no longer uses /etc/init.d/apache2
Merge pull request #445 from krig/suse-apache

Make use of /etc/init.d/apache2 conditional in SUSE-specific configuration
ctdb: add ctdb_rundir parameter and create on startup

By default, ctdbd puts a .socket_lock file in RUNDIR/ctdb. The directory
must exist prior to startup.

Signed-off-by: David Disseldorp <ddiss@suse.de>
Merge pull request #447 from ddiss/ctdb_rundir

ctdb: add ctdb_rundir parameter and create on startup
Merge pull request #342 from dmuhamedagic/exportfs-multiple-exports

Exportfs multiple exports
Merge pull request #443 from davidvossel/nfs-cleanup

Support new NFS Active Passive and Active Active use-cases.