fence_virt: Remove remaining references to checkpoints

Remove all remaining references to the checkpoint backend plugin,
which has been removed.

Signed-off-by: Ryan McCabe <rmccabe@redhat.com>
This commit is contained in:
Ryan McCabe 2017-05-29 14:45:59 -04:00
parent b0aa3ad784
commit f075a5b45b
2 changed files with 7 additions and 14 deletions

View File

@ -13,14 +13,10 @@
You should have received a copy of the GNU General Public License
along with this program; see the file COPYING. If not, write to the
Free Software Foundation, Inc., 675 Mass Ave, Cambridge,
Free Software Foundation, Inc., 675 Mass Ave, Cambridge,
MA 02139, USA.
*/
/*
* @file fence_virtd.c: Implementation of server daemon for Xen virtual
* machine fencing. This uses SA AIS CKPT b.1.0 checkpointing API to
* store virtual machine states.
*
* Author: Lon Hohberger <lhh at redhat.com>
*/
#include <stdio.h>
@ -197,7 +193,6 @@ send_multicast_packets(ip_list_t *ipl, fence_virt_args_t *args,
sizeof(struct sockaddr_in));
tgt = (struct sockaddr *)&tgt4;
tgt_len = sizeof(tgt4);
} else if (args->net.family == PF_INET6) {
mc_sock = ipv6_send_sk(ipa->ipa_address, args->net.addr,
args->net.port,
@ -264,7 +259,7 @@ mcast_fence_virt(fence_virt_args_t *args)
int lfd = -1, key_len = 0, fd, ret;
int attempts = 0;
uint32_t seqno;
/* Initialize NSS; required to do hashing, as silly as that
sounds... */
if (NSS_NoDB_Init(NULL) != SECSuccess) {
@ -374,7 +369,7 @@ mcast_fence_virt(fence_virt_args_t *args)
close(fd);
return ret;
break;
/* case AUTH_X509:
/* case AUTH_X509:
return ssl_exchange(...); */
default:
close(fd);

View File

@ -116,12 +116,10 @@ plugin is used (you could, if you wanted, use 'direct serial' with
'cluster cpg', or 'multicast' with 'RHEV-H' for example).
These plugins must also be able to discover where appropriate. For
example, the Checkpoint plugin can only be used if corosync/openais
is running. Likewise, the RHEV-M plugin may only be used in the
cases where the host operating system is a RHEV-H. A defined plugin
preference order should be specified/documented so that the host
daemon behaves in a predictable manner in absence of host-side
configuration data (about which plugin to use).
example, the cpg plugin can only be used if corosync/openais
is running. A defined plugin preference order should be specified/documented
so that the host daemon behaves in a predictable manner in absence of
host-side configuration data (about which plugin to use).
[1] TCP was also explored, however, the security is much better