Keepalived

在keep上如何自定义编排动作1.首页->全副课程->动作训练->自建编排

Keepalived装置部署 下载地址：点我下载通过ftp工具上传到linux中，/home/software解压tar -zxvf keepalived-2.0.18.tar.gz解压后进入到解压进去的目录，看到会有 configure ，那么就能够做配置了（配置装置和nginx截然不同）配置 Keepalived - 主 通过命令 vim keepalived.conf 关上配置文件 global_defs {# 路由id：以后装置keepalived的节点主机标识符，保障全局惟一router_id keep_171}vrrp_instance VI_1 {# 示意状态是MASTER主机还是备用机BACKUPstate MASTER# 该实例绑定的网卡interface ens33# 保障主备节点统一即可virtual_router_id 51# 权重，master权重个别高于backup，如果有多个，那就是选举，谁的权重高，谁就入选priority 100# 主备之间同步查看工夫距离，单位秒advert_int 2# 认证权限明码，避免非法节点进入authentication {auth_type PASSauth_pass 1111}# 虚构进去的ip，能够有多个（vip）virtual_ipaddress {192.168.1.161}}附：查看网卡名称 启动 Keepalived在sbin目录中进行启动（同nginx），如下图：配置 Keepalived - 备 通过命令 vim keepalived.conf 关上配置文件 global_defs {router_id keep_172}vrrp_instance VI_1 {# 备用机设置为BACKUPstate BACKUPinterface ens33virtual_router_id 51# 权重低于MASTERpriority 80advert_int 2authentication {auth_type PASSauth_pass 1111}virtual_ipaddress {# 留神：主备两台的vip都是一样的，绑定到同一个vip192.168.1.161}}启动 Keepalived # 启动keepalivedsystemctl start keepalived# 进行keepalivedsystemctl stop keepalived# 重启keepalivedsystemctl restart keepalived查看过程 ...

每一台配置下keepalived #master01 配置：cat >/etc/keepalived/keepalived.conf<<"EOF"! Configuration File for keepalivedglobal_defs { router_id LVS_DEVEL script_user root enable_script_security}vrrp_script chk_apiserver { script "/etc/keepalived/check_apiserver.sh" interval 5 weight -5 fall 2 rise 1 #检测一次胜利，则认为在线}vrrp_instance VI_1 { state BACKUP nopreempt interface ens160 mcast_src_ip 10.0.0.20 virtual_router_id 51 priority 100 advert_int 2 authentication { auth_type PASS auth_pass K8SHA_KA_AUTH } virtual_ipaddress { 10.0.0.30 } track_script { chk_apiserver }}EOF#Master02 配置：cat >/etc/keepalived/keepalived.conf<<"EOF"! Configuration File for keepalivedglobal_defs { router_id LVS_DEVEL script_user root enable_script_security}vrrp_script chk_apiserver { script "/etc/keepalived/check_apiserver.sh" interval 5 weight -5 fall 2 rise 1}vrrp_instance VI_1 { state BACKUP nopreempt interface ens160 mcast_src_ip 10.0.0.21 virtual_router_id 51 priority 99 advert_int 2 authentication { auth_type PASS auth_pass K8SHA_KA_AUTH } virtual_ipaddress { 10.0.0.30 } track_script { chk_apiserver }}EOF#Master03 配置：cat >/etc/keepalived/keepalived.conf<<"EOF"! Configuration File for keepalivedglobal_defs { router_id LVS_DEVEL script_user root enable_script_security}vrrp_script chk_apiserver { script "/etc/keepalived/check_apiserver.sh" interval 5 weight -5 fall 2 rise 1}vrrp_instance VI_1 { state BACKUP nopreempt interface ens160 mcast_src_ip 10.0.0.22 virtual_router_id 51 priority 98 advert_int 2 authentication { auth_type PASS auth_pass K8SHA_KA_AUTH } virtual_ipaddress { 10.0.0.30 } track_script { chk_apiserver }EOF健康检查脚本 ...

yum install keepalivedvi /etc/keepalived/keepalived.conf<code>vrrp_script chk_haproxy {script "pidof haproxy" interval 2}vrrp_instance VI_1 { debug 2 interface eth0 # interface to monitor state MASTER virtual_router_id 51 # Assign one ID for this route priority 101 # 101 on master, 100 on backup unicast_src_ip x.x.x.x # My IP unicast_peer { x.x.x.x # Peer IP } track_script { chk_haproxy } virtual_ipaddress { x.x.x.x dev eth0 }}</code>Backupvi /etc/keepalived/keepalived.conf<code>vrrp_script chk_haproxy {script "pidof haproxy" interval 2}vrrp_instance VI_1 { debug 2 interface eth0 # interface to monitor state BACKUP virtual_router_id 51 # Assign one ID for this route priority 100 # 101 on master, 100 on backup unicast_src_ip x.x.x.x # My IP unicast_peer { x.x.x.x # Peer IP } track_script { chk_haproxy } virtual_ipaddress { x.x.x.x dev eth0 }}</code>ip a

问题咱们常常应用浮动 IP（SIP，或叫 VIP），来实现数据库的高可用部署。业务通过拜访浮动 IP，始终拜访主数据库。如果业务正在拜访数据库时，数据库主从产生切换，导致 SIP 漂移，那正在应用的数据库连贯会受到影响么? 试验咱们创立同子网的两台虚拟机，别离装置 MySQL。再筹备一台额定的虚拟机，用来模仿业务，拜访数据库，此处省略装置过程。这两台虚拟机的 IP 别离是 x.x.x.37 和 x.x.x.39，为了容易辨别，咱们设置 PS1，来辨别两个 linux 的会话。下图以 37 为例，这里设置了 PS1，并确认机器上有创立好数据库， 39 与之相似： 咱们再选取一个 SIP: x.x.x.200，将其绑定到 37 上， 向子网进行 arp 宣告，告诉大家 ip 变更了： 当初业务机器上，测试一下拜访 SIP 胜利： 咱们在数据库中用 sysbench 灌入数据，此处省略步骤，只看后果： 而后向数据库执行一个 select，这里咱们用了一个 sleep，使得数据库返回后果集慢一些，大略每秒输入 1000 行左右： 执行 SQL 后，MySQL 客户端会不停输入后果，如果产生了任何连贯问题，咱们能够立即发现。当初让 SIP 产生一次切换。筹备好如下命令：先在 37 上卸下 SIP，再在 39 上加上 SIP，发送 arp 宣告。 ...