O slideshow foi denunciado.
Utilizamos seu perfil e dados de atividades no LinkedIn para personalizar e exibir anúncios mais relevantes. Altere suas preferências de anúncios quando desejar.

OpenStack Control Plane High Availability

2.330 visualizações

Publicada em

Presentation I gave to the Atlanta OpenStack Meetup on November 20th on Control Plane high availability for OpenStack.

Publicada em: Tecnologia
  • Seja o primeiro a comentar

OpenStack Control Plane High Availability

  1. 1. OpenStack Control Plane High Availability Michael Solberg Principal Architect, Red Hat November 20th, 2014
  2. 2. H/A Architecture
  3. 3. Control Plane Cluster
  4. 4. Active/Passive Service Architecture
  5. 5. Active/Passive Service Architecture
  6. 6. Load Balanced Clone Set Architecture
  7. 7. Load Balanced Clone Set Architecture
  8. 8. Infrastructure H/A Notes RabbitMQ ●Configured to use active/active mirrored queues. ● Incoming requests are load balanced round robin at layer 4 by HAProxy. Memcached ● Services which leverage memcached (Horizon, Swift) only use a local instance. HAProxy ●Run as a clone set across the Cloud Controller cluster. ● All nodes are configured to balance all services - Active/Hot Standby configuration. ●VIPs are managed as H/A resources by Pacemaker.
  9. 9. Infrastructure H/A Notes Keystone ●API Services are Active/Active behind HAProxy. ●PKI Infrastructure (CA, etc) is manually synced between nodes at installation. Glance ●API Services are Active/Active behind HAProxy. ●Backend Image Store is provide by shared storage (HA). Cinder ●API and Scheduler services are Active/Active behind HAProxy. ●Volume Services are managed by the Scheduler service.
  10. 10. Infrastructure H/A Notes Swift ●Proxy Service is Active/Active behind HAProxy. ●Object Expirer runs Active/Passive ●Availability of Object, Container, and Account services is managed by the Proxy service. ●Replication is configured when the Ring is created/modified. Neutron ●API Services are Active/Active behind HAProxy. ●Availability of Agent services is managed by API service - plugin dependent. Nova ●API, Metadata, and VNC Services are Active/Active behind HAProxy. ●Availability of Nova Compute services is managed by Scheduler service.
  11. 11. Infrastructure H/A Notes Horizon ●HTTP service are not managed by Pacemaker. ●HAProxy performs Layer 7 load balancing for this service. Heat ●API, CloudFormation, and CloudWatch services run Active/Active behind HAProxy. ●Engine service is Active/Passive. Ceilometer ●API and Collector services run Active/Active behind HAProxy. ●Central Agent runs Active/Passive. ●Compute Agents run on the Compute Nodes ●Mongo Database is configured with replicas across the cluster (no sharding).

×