Directory
Openstack-mitaka Overview of High Availability
Openstack-mitaka High-availability environment initialization
Openstack-mitaka High-availability Mariadb-galera cluster deployment
Openstack-mitaka High Availability of memcache
Openstack-mitaka High Availability pacemaker+corosync+pcs High availability cluster
Openstack-mitaka Highly Available certification services (Keystone)
Openstack-mitaka High Availability Computing Service (Nova)
Openstack-mitaka High-Availability Network Service (Neutron)
Openstack-mitaka High Availability of Dashboard
Openstack-mitaka high Availability to start an instance
Openstack-mitaka High Availability Test
Cluster introduction
The Authentication Service authentication cache uses the Memcache cache token. The cache service Memcache runs on the control node and Memcache is configured with a native HA configuration in most openstack configurations, but calls in dashboard need to be used by the Haproxy proxy
Installation deployment
The following operations are performed on three nodes:
#Yum InstallMemcached python-memcached-y# Vim/etc/sysconfig/memcached PORT="11211"USER="memcached"Maxconn="1024x768"CACHESIZE=" -"OPTIONS="- L 192.168.0.11"# Modify the management address of the corresponding host # Systemctl enable memcached.service# systemctl start Memcached.service
[Openstack] Openstack-mitaka High Availability of memcache