私有云落地解决方案之openstack高可用(pike版本)-集群参数

标签: openstack crm 解决方案 私有云 集群
952人阅读 评论(0) 收藏 举报
分类:

作者:【吴业亮】

博客:http://blog.csdn.net/wylfengyujiancheng

一、添加服务

将消息队列加入集群监控中

crm configure primitive rabbitmq-server systemd:rabbitmq-server \
params environment_file="/etc/profile.d/rabbitmq-server.sh" \
op start interval=0s timeout=600 \
op stop interval=0s timeout=120 \
op monitor interval=10 timeout=20 \
meta priority=100

将消息队列克隆加入集群监控中

crm configure clone rabbitmq-server-clone rabbitmq-server meta target-role=Started

注意:
在三个控制节点上创建/etc/profile.d/rabbitmq-server.sh并写入

export RABBITMQ_USE_LONGNAME=true

将haproxy加入集群监控中

crm configure primitive haproxy systemd:haproxy \
op start interval=0s \
op start interval=0s timeout=20s \
op stop interval=0s timeout=20s \
op monitor interval=20s  timeout=30s \
meta priority=100 target-role=Started
colocation haproxy-with-vip inf: vip:Started haproxy:Started

将httpd加入集群监控中

crm configure primitive httpd systemd:httpd \
op start interval=0s timeout=40s \
op stop interval=0s timeout=60s \
op monitor interval=30s timeout=30s

将memcached加入集群监控中

crm configure primitive memcached systemd:memcached \
params \
op monitor interval=30s timeout=30s
crm configure clone openstack-dashboard-clone httpd meta
crm configure clone openstack-memcached-clone memcached

将openstack-glance-registry加入集群监控中

crm configure primitive openstack-glance-registry systemd:openstack-glance-registry \
op start interval=0s timeout=45s \
op stop interval=0s timeout=45s \
op monitor interval=30s timeout=30s

将openstack-glance-registry克隆加入集群监控中

crm configure clone openstack-glance-registry-clone openstack-glance-registry  metatarget-role=Started

将openstack-glance-api加入集群监控中

crm configure primitive openstack-glance-api systemd:openstack-glance-api \
op start interval=0s timeout=45s \
op stop interval=0s timeout=45s \
op monitor interval=30s timeout=30s

将openstack-glance-api克隆加入集群监控中

crm configure clone openstack-glance-api-clone openstack-glance-api  meta target-role=Started

将openstack-nova-cert加入集群监控中

crm configure primitive openstack-nova-cert systemd:openstack-nova-cert \
op start interval=0s timeout=45s \
op stop interval=0s timeout=45s \
op monitor interval=30s timeout=30s

将openstack-nova-cert克隆加入集群监控中

crm configure clone openstack-nova-cert-clone openstack-nova-cert  meta target-role=Started

将openstack-nova-api加入集群监控中

crm configure primitive openstack-nova-api systemd:openstack-nova-api \
op start interval=0s timeout=45s \
op stop interval=0s timeout=45s \
op monitor interval=30s timeout=30s

将openstack-nova-api克隆加入集群监控中

crm configure clone openstack-nova-api-clone openstack-nova-api  meta target-role=Started

将openstack-nova-conductor加入集群监控中

crm configure primitive openstack-nova-conductor systemd:openstack-nova-conductor   \
op start interval=0s timeout=45s \
op stop interval=0s timeout=45s \
op monitor interval=30s timeout=30s

将openstack-nova-conductor克隆加入集群监控中

crm configure clone openstack-nova-conductor-clone openstack-nova-conductor metatarget-role=Started

将openstack-nova-scheduler加入集群监控中

crm configure primitive openstack-nova-scheduler systemd:openstack-nova-scheduler \
op start interval=0s timeout=45s \
op stop interval=0s timeout=45s \
op monitor interval=30s timeout=30s

将openstack-nova-scheduler克隆加入集群监控中

crm configure clone openstack-nova-scheduler-clone openstack-nova-scheduler  metatarget-role=Started

将openstack-nova-novncproxy加入集群监控中

crm configure primitive openstack-nova-novncproxy systemd:openstack-nova-、
novncproxy \
op start interval=0s timeout=45s \
op stop interval=0s timeout=45s \
op monitor interval=30s timeout=30s

将openstack-nova-novncproxy克隆加入集群监控中

crm configure clone openstack-nova-novncproxy-clone openstack-nova-novncproxy    metatarget-role=Started

将openstack-nova-consoleauth加入集群监控中

crm configure primitive openstack-nova-consoleauth systemd:openstack-nova-consoleauth \
op start interval=0s timeout=45s \
op stop interval=0s timeout=45s \
op monitor interval=30s timeout=30s \
meta target-role=Started

将openstack-nova-consoleauth克隆加入集群监控中

crm configure clone openstack-nova-consoleauth-clone openstack-nova-consoleauth   metatarget-role=Started

将openstack-cinder-api加入集群监控中

crm configure primitive openstack-cinder-api systemd:openstack-cinder-api \
op start interval=0s timeout=45s \
op stop interval=0s timeout=45s \
op monitor interval=30s timeout=30s

将openstack-cinder-api克隆加入集群监控中

crm configure clone openstack-cinder-api-clone openstack-cinder-api meta target-role=Started

将openstack-cinder-scheduler加入集群监控中

crm configure primitive openstack-cinder-scheduler systemd:openstack-cinder-scheduler \
op start interval=0s timeout=45s \
op stop interval=0s timeout=45s \
op monitor interval=30s timeout=30s

将openstack-cinder-scheduler克隆加入集群监控中

crm configure clone openstack-cinder-scheduler-clone openstack-cinder-scheduler   metatarget-role=Started

将neutron-server 加入集群监控中

crm configure primitive neutron-server systemd:neutron-server \
op start interval=0s timeout=45s \
op stop interval=0s timeout=45s \
op monitor interval=30s timeout=30s

将neutron-server克隆资源加入集群监控中

crm configure clone neutron-server-clone neutron-server  meta target-role=Started

将neutron-openvswitch-agent 加入集群监控中

crm configure primitive neutron-openvswitch-agent systemd:neutron-openvswitch-agent \
op start interval=0s timeout=45s \
op stop interval=0s timeout=45s \
op monitor interval=30s timeout=30s

将neutron-openvswitch-agent克隆 加入集群监控中

crm configure clone neutron-openvswitch-agent-clone neutron-openvswitch-agent metatarget-role=Started

将neutron-dhcp-agent 加入集群监控中

crm configure primitive neutron-dhcp-agent systemd:neutron-dhcp-agent \
op start interval=0s timeout=45s \
op stop interval=0s timeout=45s \
op monitor interval=30s timeout=30s

将neutron-dhcp-agent克隆加入集群监控中

crm configure clone neutron-dhcp-agent-clone neutron-dhcp-agent  meta target-role=Started

将neutron-metadata-agent 加入集群监控中

crm configure primitive neutron-metadata-agent systemd:neutron-metadata-agent  \
op start interval=0s timeout=45s \
op stop interval=0s timeout=45s \
op monitor interval=30s timeout=30s

将neutron-metadata-agent克隆加入集群监控中

crm configure clone neutron-metadata-agent-clone neutron-metadata-agent metatarget-role=Started

将systemd:neutron-l3-agent加入集群监控中

crm configure primitive neutron-l3-agent systemd:neutron-l3-agent \
op start interval=0s timeout=45s \
op stop interval=0s timeout=45s \
op monitor interval=30s timeout=30s

将systemd:neutron-l3-agent克隆加入集群监控中

crm configure clone neutron-l3-agent-clone neutron-l3-agent meta target-role=Started

二、定义服务启动顺序

定义neutron-metadata-agent-clone和neutron-dhcp-agent-clone:start启动

pcs constraint order order_neutron-metadata-agent_neutron-dhcp-agent \
neutron-metadata-agent-clone:start neutron-dhcp-agent-clone:start    \
symmetrical=true

定义openstack-memcached-clone和openstack-dashboard-clone启动

pcs constraint order order_memcached_httpd openstack-memcached-clone:start\
openstack-dashboard-clone:start \
symmetrical=true

定义vip、haproxy和openstack-neutron-server-clone启动

pcs constraint order order_vip_haproxy vip:start haproxy:start \
pcs constraint order order_vip_neutron-server vip:start \
openstack-neutron-server-clone:start

定义neutron-openvswitch-agent-clone和neutron-metadata-agent-clone启动

pcs constraint order order_neutron-openvswitch-agent_neutron-metadata-agent \
neutron-openvswitch-agent-clone:start  neutron-metadata-agent-clone:start \
symmetrical=true

定义openstack-memcached-clone和openstack-nova-consoleauth-clone启动

pcs constraint order order_memcached_nova-consoleauth \
openstack-memcached-clone:start openstack-nova-consoleauth-clone:start\
symmetrical=true

定义neutron-metadata-agent-clone和neutron-l3-agent-clone启动

pcs constraint order order_neutron-metadata-agent_neutron-l3-agent \
neutron-metadata-agent-clone:start neutron-l3-agent-clone:start \
symmetrical=true
查看评论

ceph分布式存储实战

  • 2017年12月23日 10:16
  • 10.06MB
  • 下载

构建OpenStack的高可用性(HA,High Availability)

1、CAP理论 1) CAP 理论给出了3个基本要素: 一致性 ( Consistency) :任何一个读操作总是能读取到之前完成的写操作结果; 可用性 ( Availabi...
  • hilyoo
  • hilyoo
  • 2012-06-30 19:27:32
  • 49739

OpenStack Liberty 高可用性概述和参考-第一部分

这篇文章由Avishay Traeger 和 Shimshom Zimmerman编写。       OpenStack设计目的是在商用硬件上运行,但是没有自身的机制处理硬件和软件故障。OpenSt...
  • zjluobing
  • zjluobing
  • 2016-06-10 23:08:10
  • 1945

私有云落地解决方案之openstack高可用(pike版本)-集群参数

作者:【吴业亮】博客:http://blog.csdn.net/wylfengyujiancheng一、添加服务将消息队列加入集群监控中crm configure primitive rabbitmq...
  • wylfengyujiancheng
  • wylfengyujiancheng
  • 2017-11-28 10:29:45
  • 952

Openstack高可用之基础环境配置

作者:【吴业亮】云计算开发工程师 博客:http://blog.csdn.net/wylfengyujiancheng一、操作系统配置 1.1、准备: 两个节点ha-node1和ha-node...
  • wylfengyujiancheng
  • wylfengyujiancheng
  • 2017-04-29 11:23:18
  • 2371

私有云落地解决方案之openstack高可用(pike版本)-horizon

作者:【吴业亮】博客:http://blog.csdn.net/wylfengyujiancheng安装rpm包# yum -y install openstack-dashboard修改配置文件 ...
  • wylfengyujiancheng
  • wylfengyujiancheng
  • 2017-11-28 09:20:23
  • 447

OpenStack高可用核心架构分析

一、OpenStack架构与HA分析 OpenStack实际上是由众多服务组合而成,它们之间的关联或多或少,而且具有一定的层次关系,每个服务就像积木块一样,你可以根据实际需要进行取舍并组合搭建,...
  • moonpure
  • moonpure
  • 2016-10-22 19:16:57
  • 1770

私有云落地解决方案之openstack高可用(pike版本)-添加存储节点

作者:【吴业亮】博客:http://blog.csdn.net/wylfengyujiancheng一、前提条件 各个节点的时间同步二、基础配置 1、安装软件包# yum -y install ...
  • wylfengyujiancheng
  • wylfengyujiancheng
  • 2017-11-28 09:40:19
  • 668

私有云落地解决方案之openstack高可用(pike版本)-架构

作者:【吴业亮】博客:http://blog.csdn.net/wylfengyujiancheng本架构借鉴redhat架构1、API 服务:包括 *-api, neutron-server,gla...
  • wylfengyujiancheng
  • wylfengyujiancheng
  • 2017-11-27 22:15:39
  • 841

[译] OpenStack Pike 版本中的 53 个新功能盘点

原文:https://www.mirantis.com/blog/53-things-to-look-for-in-openstack-pike/ 作者:Mirantis Nick Chase 发...
  • buyaoxx
  • buyaoxx
  • 2017-08-31 12:21:33
  • 2159
    个人资料
    持之以恒
    等级:
    访问量: 44万+
    积分: 4725
    排名: 7407
    最新评论