目录:
第一节 多节点OpenStack Charms 部署指南0.0.1.dev223–1--OpenStack Charms 部署指南
第二节 多节点OpenStack Charms 部署指南0.0.1.dev223–2-安装MAAS
第三节 多节点OpenStack Charms 部署指南0.0.1.dev223–3-安装Juju
第四节 多节点OpenStack Charms 部署指南0.0.1.dev223–4-安装openstack
第五节 多节点OpenStack Charms 部署指南0.0.1.dev223–5--使bundle安装openstack
第六节 多节点OpenStack Charms 部署指南0.0.1.dev223–6--配置vault和设置数字证书生命周期
第七节 多节点OpenStack Charms 部署指南0.0.1.dev223–7--juju 离线部署bundle
第八节 多节点OpenStack Charms 部署指南0.0.1.dev223–8--配置 OpenStack
附录 t 多节点OpenStack Charms 部署指南0.0.1.dev223–附录T–OpenStack 高可用性
第九节 多节点OpenStack Charms 部署指南0.0.1.dev223–9--网络拓扑
第十节 多节点OpenStack Charms 部署指南0.0.1.dev223–10–OpenStack 高可用基础架构实际
第十一节 多节点OpenStack Charms 部署指南0.0.1.dev223–11–访问Juju仪表板
第十二节 多节点OpenStack Charms 部署指南0.0.1.dev223–12–OpenStack 配置openstack失败后处理
第十三节 多节点OpenStack Charms 部署指南0.0.1.dev223–13–OpenStack配置高可用后无法登陆openstack dashboard
第十四节 多节点OpenStack Charms 部署指南0.0.1.dev223–14–ssh端口转发解决IDC机房国际线路不良问题
第十五节 多节点OpenStack Charms 部署指南0.0.1.dev299–15–OpenStack 实例高可用
第十六节 多节点OpenStack Charms 部署指南0.0.1.dev299–16–OpenStack基础架构高可用The easyrsa resource is missing. .
第十七节 多节点OpenStack Charms 部署指南0.0.1.dev303–17–修改实例数量等quota上限
第十八节 多节点OpenStack Charms 部署指南0.0.1.dev303–18–backup备份
第十九节 多节点OpenStack Charms 部署指南0.0.1.dev303–19–juju log
第二十节 多节点OpenStack Charms 部署指南0.0.1.dev303–20–控制器高可用性
第二十一节 多节点OpenStack Charms 部署指南0.0.1.dev303–21–控制器备份和还原
第二十二节 多节点OpenStack Charms 部署指南0.0.1.dev223–22-- Resource: res_masakari_haproxy not running
第二十三节 多节点OpenStack Charms 部署指南0.0.1.dev223–23-登录openstack-dashboad,SSLError(SSLCertVerificationError
第二十四节 多节点OpenStack Charms 部署指南0.0.1.dev223–24-Resource: res_masakari_f8b6bde_vip not running
第二十五节 多节点OpenStack Charms 部署指南0.0.1.dev223–25–rsyslog 日志服务器构建实际
第二十六节 多节点OpenStack Charms 部署指南0.0.1.dev223–26–跨model 建立关系构建rsyslog 日志服务器构建实际
第二十七节 多节点OpenStack Charms 部署指南0.0.1.dev223–27–Charm Hook
第二十八节 多节点OpenStack Charms 部署指南0.0.1.dev223–28–Command run
第三十节 多节点OpenStack Charms 部署指南0.0.1.–30–参考体系结构—Dell EMC硬件上的Canonical Charmed OpenStack(Ussuri)
第三十一节 多节点OpenStack Charms 部署指南0.0.1.–31–vm hosting-1
第三十二节 多节点OpenStack Charms 部署指南0.0.1.–32–vm hosting-2-VM host networking (snap/2.9/UI)
第三十三节 多节点OpenStack Charms 部署指南0.0.1.–33–vm hosting-3-Adding a VM host (snap/2.9/UI)
第三十四节 多节点OpenStack Charms 部署指南0.0.1.–34–vm hosting-4-VM host存储池和创建和删除vm (snap/2.9/UI)
第三十五节 多节点OpenStack Charms 部署指南0.0.1.–35–Command export-bundle备份opensack并重新部署openstack
第三十六节 多节点openstack charms 部署指南0.0.1-36-graylog实际-1
第三十七节 多节点openstack charms 部署指南0.0.1-37-graylog实际-2
第三十八节 多节点openstack charms 部署指南0.0.1-38-graylog实际-3
第三十九节 多节点openstack charms 部署指南0.0.1-39-graylog-4-filebeat
第四十节 多节点openstack charms 部署指南0.0.1-40-prometheus2
参考文档:
Welcome to the OpenStack Charm Guide
重新部署masakari后,突然出现 Resource: res_masakari_haproxy not running。
masakari/0* active idle 1/lxd/2 10.0.2.123 15868/tcp Unit is ready
hacluster/0* blocked idle 10.0.2.123 Resource: res_masakari_haproxy not running
masakari-mysql-router/0* active idle 10.0.2.123 Unit is ready
masakari/1 active idle 2/lxd/2 10.0.2.134 15868/tcp Unit is ready
hacluster/2 blocked idle 10.0.2.134 Resource: res_masakari_haproxy not running
masakari-mysql-router/2 active idle 10.0.2.134 Unit is ready
masakari/2 active idle 3/lxd/0 10.0.2.120 15868/tcp Unit is ready
hacluster/1 blocked idle 10.0.2.120 Resource: res_masakari_haproxy not running
masakari-mysql-router/1 active idle 10.0.2.120 Unit is ready
开始以为又是keystone传递ssl的问题,就删除keystone,重新部署keystone,但是还是出现 Resource: res_masakari_haproxy not running。
查找资料后,发现以前有类似的Bug: #1839021,处理方法是重新激活下crm。
原文大意:
Bug:#1839021:高可用集群charm"Resource: res_ks_haproxy not running" 资源:res_ks_haproxy未运行。
对于高可用性部署,在执行从Trusty到Xenial的升级时,如果Keystone单元花费很长时间重新启动并重新启动其服务,则该Keystone的hacluster crm监视器可能会耗尽其重试并显示状态消息Resource处于阻止状态:res_ks_haproxy未运行。
在这种情况下,在关联的keystone单元完成升级后,对受影响的主机单元执行以下操作应该可以解决该问题
juju run --unit <unit> sudo crm resource refresh
这里用” <unit>
“代替的是keystone/0
根据这个,大致可以判断,使用hacluster的高可用集群,应该都使用了crm来监测状态并可能耗尽重试次数。所以可以试试类似的命令如下:
juju run --unit masakari/0 sudo crm resource refresh
juju run --unit masakari/1 sudo crm resource refresh
juju run --unit masakari/2 sudo crm resource refresh
果然,这样操作后,masakari/1和masakari/2陆续恢复了正常
masakari/0* active idle 1/lxd/2 10.0.2.123 15868/tcp Unit is ready
hacluster/0* blocked idle 10.0.2.123 Resource: res_masakari_haproxy not running
masakari-mysql-router/0* active idle 10.0.2.123 Unit is ready
masakari/1 active idle 2/lxd/2 10.0.2.134 15868/tcp Unit is ready
hacluster/2 active idle 10.0.2.134 Unit is ready and clustered
masakari-mysql-router/2 active idle 10.0.2.134 Unit is ready
masakari/2 active idle 3/lxd/0 10.0.2.120 15868/tcp Unit is ready
hacluster/1 active idle 10.0.2.120 Unit is ready and clustered
masakari-mysql-router/1 active idle 10.0.2.120 Unit is ready
看来需要将masakari/0暂停下:
juju run-action masakari/0 pause --wait
unit-masakari-0:
UnitId: masakari/0
id: "32"
results:
Stderr: |
Synchronizing state of apache2.service with SysV service script with /lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install disable apache2
Removed /etc/systemd/system/multi-user.target.wants/apache2.service.
Created symlink /etc/systemd/system/apache2.service → /dev/null.
Synchronizing state of masakari-engine.service with SysV service script with /lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install disable masakari-engine
Removed /etc/systemd/system/multi-user.target.wants/masakari-engine.service.
Created symlink /etc/systemd/system/masakari-engine.service → /dev/null.
Synchronizing state of memcached.service with SysV service script with /lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install disable memcached
Removed /etc/systemd/system/multi-user.target.wants/memcached.service.
Created symlink /etc/systemd/system/memcached.service → /dev/null.
Synchronizing state of haproxy.service with SysV service script with /lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install disable haproxy
Removed /etc/systemd/system/multi-user.target.wants/haproxy.service.
Created symlink /etc/systemd/system/haproxy.service → /dev/null.
Stdout: |
active
active
active
inactive
inactive
inactive
inactive
status: completed
timing:
completed: 2021-04-05 01:28:36 +0000 UTC
enqueued: 2021-04-05 01:27:58 +0000 UTC
started: 2021-04-05 01:28:09 +0000 UTC
再恢复masakari/0的运行:
juju run-action masakari/0 resume --wait
unit-masakari-0:
UnitId: masakari/0
id: "34"
results:
Stderr: |
Removed /etc/systemd/system/apache2.service.
Synchronizing state of apache2.service with SysV service script with /lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install enable apache2
Created symlink /etc/systemd/system/multi-user.target.wants/apache2.service → /lib/systemd/system/apache2.service.
Removed /etc/systemd/system/masakari-engine.service.
Synchronizing state of masakari-engine.service with SysV service script with /lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install enable masakari-engine
Created symlink /etc/systemd/system/multi-user.target.wants/masakari-engine.service → /lib/systemd/system/masakari-engine.service.
Removed /etc/systemd/system/memcached.service.
Synchronizing state of memcached.service with SysV service script with /lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install enable memcached
Created symlink /etc/systemd/system/multi-user.target.wants/memcached.service → /lib/systemd/system/memcached.service.
Removed /etc/systemd/system/haproxy.service.
Synchronizing state of haproxy.service with SysV service script with /lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install enable haproxy
Created symlink /etc/systemd/system/multi-user.target.wants/haproxy.service → /lib/systemd/system/haproxy.service.
Stdout: |
inactive
inactive
inactive
inactive
active
active
status: completed
timing:
completed: 2021-04-05 01:29:28 +0000 UTC
enqueued: 2021-04-05 01:29:16 +0000 UTC
started: 2021-04-05 01:29:16 +0000 UTC
juju status masakari
:
masakari/0* active idle 1/lxd/2 10.0.2.123 15868/tcp Unit is ready
hacluster/0* blocked idle 10.0.2.123 Resource: res_masakari_haproxy not running
masakari-mysql-router/0* active idle 10.0.2.123 Unit is ready
再次刷新:
juju run --unit masakari/0 sudo crm resource refresh
Waiting for 1 reply from the controller. OK
再过了一会,juju status masakari
:
masakari/0* active idle 1/lxd/2 10.0.2.123 15868/tcp Unit is ready
hacluster/0* active idle 10.0.2.123 Unit is ready and clustered
masakari-mysql-router/0* active idle 10.0.2.123 Unit is ready
masakari/1 active idle 2/lxd/2 10.0.2.134 15868/tcp Unit is ready
hacluster/2 active idle 10.0.2.134 Unit is ready and clustered
masakari-mysql-router/2 active idle 10.0.2.134 Unit is ready
masakari/2 active idle 3/lxd/0 10.0.2.120 15868/tcp Unit is ready
hacluster/1 active idle 10.0.2.120 Unit is ready and clustered
masakari-mysql-router/1 active idle 10.0.2.120 Unit is ready