0
我具有由具有2楼的VIP资源类型的2节点起搏器的设定ocf::heartbeat:IPaddr2起搏器上的centos 7：用于在网络的blip类型心跳型IP地址2的取消管理资源释放VIP
VIP1：此VIP是不预计到自动故障切换所以这种资源类型为非托管
VIP2：此VIP有望自动故障切换，从而保持为管理
问题：我们有一个网络问题3分钟的情况，在这种情况下，
VIP1：我们用于VIP1的vip是为主机发布的，被标记为Stopped，因此我们用于VIP1的ip在host1或host2上都不存在。
VIP2：在这种情况下，ip在节点上回来，资源也被启动回来。
即使资源不受管理，我们也不希望资源VIP1释放IP。
`[[email protected] ~]# pcs config
Cluster Name: test-cluster
Corosync Nodes:
osboxes1 osboxes
Pacemaker Nodes:
osboxes osboxes1
Resources:
Resource: VIP2 (class=ocf provider=heartbeat type=IPaddr2)
Attributes: ip=192.168.50.54 nic=enp0s3:2 cidr_netmask=19
Operations: start interval=0s timeout=20s (VIP2-start-interval-0s)
stop interval=0s timeout=20s (VIP2-stop-interval-0s)
monitor interval=20s (VIP2-monitor-interval-20s)
Resource: VIP1 (class=ocf provider=heartbeat type=IPaddr2)
Attributes: ip=192.168.50.53 nic=enp0s3:1 cidr_netmask=19
Meta Attrs: is-managed=false
Operations: start interval=0s timeout=20s (VIP1-start-interval-0s)
stop interval=0s timeout=20s (VIP1-stop-interval-0s)
monitor interval=20s (VIP1-monitor-interval-20s)
Stonith Devices:
Fencing Levels:
Location Constraints:
Resource: VIP1
Enabled on: osboxes (score:50) (id:location-VIP1-osboxes-50)
Resource: VIP2
Enabled on: osboxes1 (score:50) (id:location-VIP2-osboxes1-50)
Ordering Constraints:
Colocation Constraints:
Ticket Constraints:
Alerts:
No alerts defined
Resources Defaults:
resource-stickiness: 100
Operations Defaults:
No defaults set
Cluster Properties:
cluster-infrastructure: corosync
cluster-name: test-cluster
dc-version: 1.1.15-11.el7_3.4-e174ec8
have-watchdog: false
no-quorum-policy: ignore
stonith-enabled: false
Quorum:
Options:`