通过keepalived实现多主集群方案

2024-03-03 04:59
文章标签 实现 集群 方案 keepalived 多主

本文主要是介绍通过keepalived实现多主集群方案，希望对大家解决编程问题提供一定的参考价值，需要的开发者们随着小编来一起学习吧！

一、 环境说明:
1、服务器列表：
proxy01:
eth0: 192.168.56.11 eth2: 192.168.156.11

proxy02:
eth0: 192.168.56.12 eth2: 192.168.156.12

proxy03:
eth0: 192.168.56.13 eth2: 192.168.156.13

 

2、拓扑图:

 

二、 实验步骤
1、 在所有节点上操作

# yum install –y keepalived haproxy

2、 proxy01节点配置

[root@proxy01 ~]# cat /etc/keepalived/keepalived.conf 
! Configuration File for keepalivedglobal_defs {router_id LVS_DEVELvrrp_skip_check_adv_addr
#   vrrp_strictvrrp_garp_interval 0vrrp_gna_interval 0
}vrrp_sync_group VG1 {group {VI_1VI_11}
}vrrp_sync_group VG2 {group {VI_2VI_12}
}vrrp_sync_group VG3 {group {VI_3VI_13}
}vrrp_instance VI_1 {state BACKUPinterface eth0virtual_router_id 51##nopreempt 启用抢占模式priority 10advert_int 1authentication {auth_type PASSauth_pass 1111
}use_vmac #启用vmac模式，会创建虚拟机接口，vip绑定到虚拟接口上vmac_xmit_base #发送和接收VRRP包的虚拟MAC地址unicast_src_ip 192.168.56.11unicast_peer {192.168.56.12192.168.56.13}virtual_ipaddress {192.168.56.101}
}vrrp_instance VI_2 {state BACKUPinterface eth0virtual_router_id 52priority 20##nopreemptadvert_int 1authentication {auth_type PASSauth_pass 1111
}use_vmacvmac_xmit_baseunicast_src_ip 192.168.56.11unicast_peer {192.168.56.12192.168.56.13
}virtual_ipaddress {192.168.56.102}
}vrrp_instance VI_3 {state BACKUPinterface eth0virtual_router_id 53priority 30advert_int 1##nopreemptauthentication {auth_type PASSauth_pass 1111
}use_vmacvmac_xmit_baseunicast_src_ip 192.168.56.11unicast_peer {192.168.56.12192.168.56.13}virtual_ipaddress {192.168.56.103}
}vrrp_instance VI_11 {state BACKUPinterface eth2virtual_router_id 51##nopreemptpriority 10advert_int 1authentication {auth_type PASSauth_pass 1111
}use_vmacvmac_xmit_baseunicast_src_ip 192.168.156.11unicast_peer {192.168.156.12192.168.156.13}virtual_ipaddress {192.168.156.101}
}vrrp_instance VI_12 {state BACKUPinterface eth2virtual_router_id 52priority 20#nopreemptadvert_int 1authentication {auth_type PASSauth_pass 1111
}use_vmacvmac_xmit_baseunicast_src_ip 192.168.156.11unicast_peer {192.168.156.12192.168.156.13}virtual_ipaddress {192.168.156.102}
}vrrp_instance VI_13 {state BACKUPinterface eth2virtual_router_id 53priority 30advert_int 1#nopreemptauthentication {auth_type PASSauth_pass 1111
}use_vmacvmac_xmit_baseunicast_src_ip 192.168.156.11unicast_peer {192.168.156.12192.168.156.13}virtual_ipaddress {192.168.156.103}
}

 

　　

 

3、 proxy02节点配置

[root@proxy02 ~]# cat /etc/keepalived/keepalived.conf 
! Configuration File for keepalivedglobal_defs {router_id LVS_DEVELvrrp_skip_check_adv_addr
#   vrrp_strictvrrp_garp_interval 0vrrp_gna_interval 0
}vrrp_sync_group VG1 {group {VI_1VI_11}
}vrrp_sync_group VG2 {group {VI_2VI_12}
}vrrp_sync_group VG3 {group {VI_3VI_13}
}vrrp_instance VI_1 {state BACKUPinterface eth0virtual_router_id 51#nopreemptpriority 20advert_int 1authentication {auth_type PASSauth_pass 1111
}use_vmacvmac_xmit_baseunicast_src_ip 192.168.56.12unicast_peer {192.168.56.11192.168.56.13}virtual_ipaddress {192.168.56.101}
}vrrp_instance VI_2 {state BACKUPinterface eth0virtual_router_id 52#nopreemptpriority 30advert_int 1authentication {auth_type PASSauth_pass 1111
}use_vmacvmac_xmit_baseunicast_src_ip 192.168.56.12unicast_peer {192.168.56.11192.168.56.13}virtual_ipaddress {192.168.56.102}
}vrrp_instance VI_3 {state BACKUPinterface eth0virtual_router_id 53#nopreemptpriority 10advert_int 1authentication {auth_type PASSauth_pass 1111
}use_vmacvmac_xmit_baseunicast_src_ip 192.168.56.12unicast_peer {192.168.56.11192.168.56.13}virtual_ipaddress {192.168.56.103}
}vrrp_instance VI_11 {state BACKUPinterface eth2virtual_router_id 51#nopreemptpriority 20advert_int 1authentication {auth_type PASSauth_pass 1111
}use_vmacvmac_xmit_baseunicast_src_ip 192.168.156.12unicast_peer {192.168.156.11192.168.156.13}virtual_ipaddress {192.168.156.101}
}vrrp_instance VI_12 {state BACKUPinterface eth2virtual_router_id 52#nopreemptpriority 30advert_int 1authentication {auth_type PASSauth_pass 1111
}use_vmacvmac_xmit_baseunicast_src_ip 192.168.156.12unicast_peer {192.168.156.11192.168.156.13}virtual_ipaddress {192.168.156.102}
}vrrp_instance VI_13 {state BACKUPinterface eth2virtual_router_id 53#nopreemptpriority 10advert_int 1authentication {auth_type PASSauth_pass 1111
}use_vmacvmac_xmit_baseunicast_src_ip 192.168.156.12unicast_peer {192.168.156.11192.168.156.13}virtual_ipaddress {192.168.156.103}
}

 

　　

 

4、 proxy03节点配置

[root@proxy03 ~]# cat /etc/keepalived/keepalived.conf 
! Configuration File for keepalivedglobal_defs {
#   notification_email {
#     acassen@firewall.loc
#     failover@firewall.loc
#     sysadmin@firewall.loc
#   }
#   notification_email_from Alexandre.Cassen@firewall.loc
#   smtp_server 192.168.200.1
#   smtp_connect_timeout 30router_id LVS_DEVELvrrp_skip_check_adv_addr
#   vrrp_strictvrrp_garp_interval 0vrrp_gna_interval 0
}vrrp_sync_group VG1 {group {VI_1VI_11}
}vrrp_sync_group VG2 {group {VI_2VI_12}
}vrrp_sync_group VG3 {group {VI_3VI_13}
}vrrp_instance VI_1 {state BACKUPinterface eth0virtual_router_id 51#nopreemptpriority 30advert_int 1authentication {auth_type PASSauth_pass 1111
}use_vmacvmac_xmit_baseunicast_src_ip 192.168.56.13unicast_peer {192.168.56.11192.168.56.12}virtual_ipaddress {192.168.56.101}
}vrrp_instance VI_2 {state BACKUPinterface eth0virtual_router_id 52#nopreemptpriority 10advert_int 1authentication {auth_type PASSauth_pass 1111
}use_vmacvmac_xmit_baseunicast_src_ip 192.168.56.13unicast_peer {192.168.56.11192.168.56.12}virtual_ipaddress {192.168.56.102}
}vrrp_instance VI_3 {state BACKUPinterface eth0virtual_router_id 53#nopreemptpriority 20advert_int 1authentication {auth_type PASSauth_pass 1111
}use_vmacvmac_xmit_baseunicast_src_ip 192.168.56.13unicast_peer {192.168.56.11192.168.56.12}virtual_ipaddress {192.168.56.103}
}vrrp_instance VI_11 {state BACKUPinterface eth2virtual_router_id 51#nopreemptpriority 30advert_int 1authentication {auth_type PASSauth_pass 1111
}use_vmacvmac_xmit_baseunicast_src_ip 192.168.156.13unicast_peer {192.168.156.11192.168.156.12}virtual_ipaddress {192.168.156.101}
}vrrp_instance VI_12 {state BACKUPinterface eth2virtual_router_id 52#nopreemptpriority 10advert_int 1authentication {auth_type PASSauth_pass 1111
}use_vmacvmac_xmit_baseunicast_src_ip 192.168.156.13unicast_peer {192.168.156.11192.168.156.12}virtual_ipaddress {192.168.156.102}
}vrrp_instance VI_13 {state BACKUPinterface eth2virtual_router_id 53#nopreemptpriority 20advert_int 1authentication {auth_type PASSauth_pass 1111
}use_vmacvmac_xmit_baseunicast_src_ip 192.168.156.13unicast_peer {192.168.156.11192.168.156.12}virtual_ipaddress {192.168.156.103}
}

 

　　

 

5、 启动服务

在所有节点操作
# systemctl enable keepalived.service && systemctl start keepalived.service

6、 结果验证

[root@proxy01 ~]# ip add 
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN qlen 1link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00inet 127.0.0.1/8 scope host lovalid_lft forever preferred_lft foreverinet6 ::1/128 scope host valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000link/ether 08:00:27:4b:3e:34 brd ff:ff:ff:ff:ff:ffinet 192.168.56.11/24 brd 192.168.56.255 scope global eth0valid_lft forever preferred_lft foreverinet6 fe80::a00:27ff:fe4b:3e34/64 scope link valid_lft forever preferred_lft forever
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000link/ether 08:00:27:17:a2:bc brd ff:ff:ff:ff:ff:ffinet 10.0.3.15/24 brd 10.0.3.255 scope global dynamic eth1valid_lft 85732sec preferred_lft 85732secinet6 fe80::a00:27ff:fe17:a2bc/64 scope link valid_lft forever preferred_lft forever
4: eth2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000link/ether 08:00:27:ff:0e:a8 brd ff:ff:ff:ff:ff:ffinet 192.168.156.11/24 brd 192.168.156.255 scope global eth2valid_lft forever preferred_lft foreverinet6 fe80::a00:27ff:feff:ea8/64 scope link valid_lft forever preferred_lft forever
5: vrrp.51@eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN qlen 1000link/ether 00:00:5e:00:01:33 brd ff:ff:ff:ff:ff:ff
6: vrrp.52@eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN qlen 1000link/ether 00:00:5e:00:01:34 brd ff:ff:ff:ff:ff:ff
7: vrrp.53@eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN qlen 1000link/ether 00:00:5e:00:01:35 brd ff:ff:ff:ff:ff:ffinet 192.168.56.103/32 scope global vrrp.53valid_lft forever preferred_lft forever
8: vrrp1.51@eth2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN qlen 1000link/ether 00:00:5e:00:01:33 brd ff:ff:ff:ff:ff:ff
9: vrrp1.52@eth2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN qlen 1000link/ether 00:00:5e:00:01:34 brd ff:ff:ff:ff:ff:ff
10: vrrp1.53@eth2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN qlen 1000link/ether 00:00:5e:00:01:35 brd ff:ff:ff:ff:ff:ffinet 192.168.156.103/32 scope global vrrp1.53valid_lft forever preferred_lft forever[root@proxy02 ~]# ip add
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN qlen 1link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00inet 127.0.0.1/8 scope host lovalid_lft forever preferred_lft foreverinet6 ::1/128 scope host valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000link/ether 08:00:27:ee:7d:7e brd ff:ff:ff:ff:ff:ffinet 192.168.56.12/24 brd 192.168.56.255 scope global eth0valid_lft forever preferred_lft foreverinet6 fe80::a00:27ff:feee:7d7e/64 scope link valid_lft forever preferred_lft forever
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000link/ether 08:00:27:a4:ce:2f brd ff:ff:ff:ff:ff:ffinet 10.0.3.15/24 brd 10.0.3.255 scope global dynamic eth1valid_lft 85717sec preferred_lft 85717secinet6 fe80::a00:27ff:fea4:ce2f/64 scope link valid_lft forever preferred_lft forever
4: eth2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000link/ether 08:00:27:6c:16:4d brd ff:ff:ff:ff:ff:ffinet 192.168.156.12/24 brd 192.168.156.255 scope global eth2valid_lft forever preferred_lft foreverinet6 fe80::a00:27ff:fe6c:164d/64 scope link valid_lft forever preferred_lft forever
5: vrrp.51@eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN qlen 1000link/ether 00:00:5e:00:01:33 brd ff:ff:ff:ff:ff:ff
6: vrrp.52@eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN qlen 1000link/ether 00:00:5e:00:01:34 brd ff:ff:ff:ff:ff:ffinet 192.168.56.102/32 scope global vrrp.52valid_lft forever preferred_lft forever
7: vrrp.53@eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN qlen 1000link/ether 00:00:5e:00:01:35 brd ff:ff:ff:ff:ff:ff
8: vrrp1.51@eth2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN qlen 1000link/ether 00:00:5e:00:01:33 brd ff:ff:ff:ff:ff:ff
9: vrrp1.52@eth2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN qlen 1000link/ether 00:00:5e:00:01:34 brd ff:ff:ff:ff:ff:ffinet 192.168.156.102/32 scope global vrrp1.52valid_lft forever preferred_lft forever
10: vrrp1.53@eth2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN qlen 1000link/ether 00:00:5e:00:01:35 brd ff:ff:ff:ff:ff:ff[root@proxy03 ~]# ip add 
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN qlen 1link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00inet 127.0.0.1/8 scope host lovalid_lft forever preferred_lft foreverinet6 ::1/128 scope host valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000link/ether 08:00:27:87:1a:f0 brd ff:ff:ff:ff:ff:ffinet 192.168.56.13/24 brd 192.168.56.255 scope global eth0valid_lft forever preferred_lft foreverinet6 fe80::a00:27ff:fe87:1af0/64 scope link valid_lft forever preferred_lft forever
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000link/ether 08:00:27:6e:be:14 brd ff:ff:ff:ff:ff:ffinet 10.0.3.15/24 brd 10.0.3.255 scope global dynamic eth1valid_lft 85696sec preferred_lft 85696secinet6 fe80::a00:27ff:fe6e:be14/64 scope link valid_lft forever preferred_lft forever
4: eth2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000link/ether 08:00:27:b0:64:83 brd ff:ff:ff:ff:ff:ffinet 192.168.156.13/24 brd 192.168.156.255 scope global eth2valid_lft forever preferred_lft foreverinet6 fe80::a00:27ff:feb0:6483/64 scope link valid_lft forever preferred_lft forever
5: vrrp.51@eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN qlen 1000link/ether 00:00:5e:00:01:33 brd ff:ff:ff:ff:ff:ffinet 192.168.56.101/32 scope global vrrp.51valid_lft forever preferred_lft forever
6: vrrp.52@eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN qlen 1000link/ether 00:00:5e:00:01:34 brd ff:ff:ff:ff:ff:ff
7: vrrp.53@eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN qlen 1000link/ether 00:00:5e:00:01:35 brd ff:ff:ff:ff:ff:ff
8: vrrp1.51@eth2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN qlen 1000link/ether 00:00:5e:00:01:33 brd ff:ff:ff:ff:ff:ffinet 192.168.156.101/32 scope global vrrp1.51valid_lft forever preferred_lft forever
9: vrrp1.52@eth2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN qlen 1000link/ether 00:00:5e:00:01:34 brd ff:ff:ff:ff:ff:ff
10: vrrp1.53@eth2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN qlen 1000link/ether 00:00:5e:00:01:35 brd ff:ff:ff:ff:ff:ff

 

7、 总结
　　之前我们用keepalived做集群时一般使用它构建服务器主从，也就是只有一个vip，并且这个vip只是在主节点上，当主节点宕机时，vip漂移到从节点上，从而实现高可用。但随着业务的发展，单个节点随之成为业务的性能瓶颈，及时我们使用的负载均衡再强大，服务器配置再高，也不可能单节点抗住所有流量。而通过这种方案，在keepalived的主从基础上扩展一下，通过配置多个vip，每个keepalived节点互为主从，正常情况下保证所有服务器都能拥有一个vip，然后通过dns负载均衡技术，将业务流量转发到每个vip。从而在一定程度上避免了单服务器的性能瓶颈。

转载于:https://www.cnblogs.com/edenlong/p/10078975.html

这篇关于通过keepalived实现多主集群方案的文章就介绍到这儿，希望我们推荐的文章对编程师们有所帮助！


http://www.chinasem.cn/article/768521。

相关文章

服务器集群同步时间手记

服务器集群同步时间手记

1.时间服务器配置（必须root用户） （1）检查ntp是否安装 [root@node1 桌面]# rpm -qa|grep ntpntp-4.2.6p5-10.el6.centos.x86_64fontpackages-filesystem-1.41-1.1.el6.noarchntpdate-4.2.6p5-10.el6.centos.x86_64 （2）修改ntp配置文件 [r
阅读更多...
无人叉车3d激光slam多房间建图定位异常处理方案-墙体画线地图切分方案

无人叉车3d激光slam多房间建图定位异常处理方案-墙体画线地图切分方案

墙体画线地图切分方案 针对问题：墙体两侧特征混淆误匹配，导致建图和定位偏差，表现为过门跳变、外月台走歪等 ·解决思路：预期的根治方案IGICP需要较长时间完成上线，先使用切分地图的工程化方案，即墙体两侧切分为不同地图，在某一侧只使用该侧地图进行定位 方案思路 切分原理：切分地图基于关键帧位置，而非点云。 理论基础：光照是直线的，一帧点云必定只能照射到墙的一侧，无法同时照到两侧实践考虑：关
阅读更多...
HDFS—集群扩容及缩容

HDFS—集群扩容及缩容

白名单：表示在白名单的主机IP地址可以，用来存储数据。 配置白名单步骤如下： 1）在NameNode节点的/opt/module/hadoop-3.1.4/etc/hadoop目录下分别创建whitelist 和blacklist文件 （1）创建白名单 [lytfly@hadoop102 hadoop]$ vim whitelist 在whitelist中添加如下主机名称，假如集群正常工作的节
阅读更多...
Hadoop集群数据均衡之磁盘间数据均衡

Hadoop集群数据均衡之磁盘间数据均衡

生产环境，由于硬盘空间不足，往往需要增加一块硬盘。刚加载的硬盘没有数据时，可以执行磁盘数据均衡命令。（Hadoop3.x新特性） plan后面带的节点的名字必须是已经存在的，并且是需要均衡的节点。 如果节点不存在，会报如下错误： 如果节点只有一个硬盘的话，不会创建均衡计划： （1）生成均衡计划 hdfs diskbalancer -plan hadoop102 （2）执行均衡计划 hd
阅读更多...
hdu1043（八数码问题，广搜 + hash（实现状态压缩） ）

hdu1043（八数码问题，广搜 + hash（实现状态压缩） ）

利用康拓展开将一个排列映射成一个自然数，然后就变成了普通的广搜题。 #include<iostream>#include<algorithm>#include<string>#include<stack>#include<queue>#include<map>#include<stdio.h>#include<stdlib.h>#include<ctype.h>#inclu
阅读更多...
高效+灵活，万博智云全球发布AWS无代理跨云容灾方案！

高效+灵活，万博智云全球发布AWS无代理跨云容灾方案！

摘要 近日，万博智云推出了基于AWS的无代理跨云容灾解决方案，并与拉丁美洲，中东，亚洲的合作伙伴面向全球开展了联合发布。这一方案以AWS应用环境为基础，将HyperBDR平台的高效、灵活和成本效益优势与无代理功能相结合，为全球企业带来实现了更便捷、经济的数据保护。 一、全球联合发布 9月2日，万博智云CEO Michael Wong在线上平台发布AWS无代理跨云容灾解决方案的阐述视频，介绍了
阅读更多...
【C++】_list常用方法解析及模拟实现

【C++】_list常用方法解析及模拟实现

相信自己的力量，只要对自己始终保持信心，尽自己最大努力去完成任何事，就算事情最终结果是失败了，努力了也不留遗憾。💓💓💓 目录   ✨说在前面 🍋知识点一：什么是list？ •🌰1.list的定义 •🌰2.list的基本特性 •🌰3.常用接口介绍 🍋知识点二：list常用接口 •🌰1.默认成员函数 🔥构造函数（⭐） 🔥析构函数 •🌰2.list对象
阅读更多...
【Prometheus】PromQL向量匹配实现不同标签的向量数据进行运算

【Prometheus】PromQL向量匹配实现不同标签的向量数据进行运算

✨✨ 欢迎大家来到景天科技苑✨✨ 🎈🎈 养成好习惯，先赞后看哦~🎈🎈 🏆 作者简介：景天科技苑 🏆《头衔》：大厂架构师，华为云开发者社区专家博主，阿里云开发者社区专家博主，CSDN全栈领域优质创作者，掘金优秀博主，51CTO博客专家等。 🏆《博客》：Python全栈，前后端开发，小程序开发，人工智能，js逆向，App逆向，网络系统安全，数据分析，Django，fastapi
阅读更多...
让树莓派智能语音助手实现定时提醒功能

让树莓派智能语音助手实现定时提醒功能

最初的时候是想直接在rasa 的chatbot上实现，因为rasa本身是带有remindschedule模块的。不过经过一番折腾后，忽然发现，chatbot上实现的定时，语音助手不一定会有响应。因为，我目前语音助手的代码设置了长时间无应答会结束对话，这样一来，chatbot定时提醒的触发就不会被语音助手获悉。那怎么让语音助手也具有定时提醒功能呢？ 我最后选择的方法是用threading.Time
阅读更多...
Android实现任意版本设置默认的锁屏壁纸和桌面壁纸（两张壁纸可不一致）

Android实现任意版本设置默认的锁屏壁纸和桌面壁纸（两张壁纸可不一致）

客户有些需求需要设置默认壁纸和锁屏壁纸  在默认情况下 这两个壁纸是相同的  如果需要默认的锁屏壁纸和桌面壁纸不一样 需要额外修改 Android13实现 替换默认桌面壁纸： 将图片文件替换frameworks/base/core/res/res/drawable-nodpi/default_wallpaper.*  （注意不能是bmp格式） 替换默认锁屏壁纸： 将图片资源放入vendo
阅读更多...

Copyright China编程 23002807@qq.com

沪ICP备2023033072号-2