• Buy Now
    • Rackspace Cloud
    • Email & Apps
    • Fanatical Support for AWS
    • Managed Google Cloud Platform
    • Office 365
  • Log In
    • MyRackspace Portal
    • Cloud Control Panel
    • Rackspace Webmail Login
    • Cloud Office Control Panel
  • Rackspace Logo
  • Developer Home
  • Developer Documentation
  • Blogs ▼
    • Technical Blog
    • Rackspace Blog
    • Solve: Thought Leadership
  • Support Documentation

Developer Docs


Let’s Build Something Powerful Together!

End-to-End Multicloud Solutions.   Solving Together.™   Learn more at Rackspace.com

Submit an issue
  • Rackspace Private Cloud, v14
  • Technical FAQ
    • Preface
      • About Rackspace Private Cloud Powered By Openstack
      • RPCO configuration
      • Rackspace Private Cloud support
    • FAQ
      • Operating system and architecture
      • Networking
      • Database architecture
      • Clustered queue management
      • Failover and high availability
      • Load balancing
      • Log aggregation and management
    • Supported Software
      • Rackspace Private Cloud v14
      • Rackspace Private Cloud v13
      • Special Notes
    • Document history and additional information
      • Additional resources
    • Disclaimer
  • Optimization and Visualization User Guide
    • RPCO Optimization and Visualization User Guide
    • Product overview
      • Architecture
      • Features
        • Alarms
        • Ceph monitor
        • Chargeback
        • Charts
        • Heat map
        • Metrics
        • Reports
    • How-To
      • Configure a dynamic threshold
      • Configure chargeback costs
  • Release Notes
    • Preface
      • About Rackspace Private Cloud Powered By Openstack
      • RPCO configuration
      • Rackspace Private Cloud support
    • Known issues
    • What's new
      • Block Storage service (cinder)
        • Prelude
        • Features
        • Unsupported
      • Compute service (nova)
        • Prelude
        • Critical
        • Upgrade
        • Deprecations
        • Unsupported
        • Features
      • Dashboard (horizon)
        • Prelude
        • Fixes
        • Features
      • Identity service (keystone)
        • Prelude
        • Security
        • Features
        • Deprecations
        • Unsupported
      • Image service (glance)
        • Prelude
        • Critical
        • Upgrade
        • Deprecations
        • Features
      • Networking service (neutron)
        • Prelude
        • Deprecations
        • Unsupported
      • Object Storage (swift)
        • Prelude
        • Fixes
        • Features
      • Orchestration (heat)
        • Prelude
        • Features
    • What's changed
      • RPCO changelog by release
    • Document history and additional information
      • Additional resources
    • Disclaimer
  • Stand-alone Object Storage for RPCO Guide
    • Preface
      • About Rackspace Private Cloud Powered By Openstack
      • RPCO configuration
      • Rackspace Private Cloud support
    • Object Storage overview
      • Components
      • Configuration
      • System requirements
    • Prerequisites
    • Install Object Storage
      • Example Object Storage installation architecture
      • Configure and mount storage devices
      • Create networks
      • Configure an Object Storage deployment
        • Update the stand-alone Object Storage configuration files
        • Allow Identity users to use Object Storage
      • Run the Object Storage playbooks
      • Verify the installation
    • Object Storage monitoring
      • Service and response
      • Object Storage monitors
    • Object Storage configuration files
    • Document history and additional information
      • Additional resources

Load balancing#

Get answers to common technical questions about failover and high availability for Rackspace Private Cloud Powered By OpenStack (RPCO) 14.0.

Do the services need to be modified to enable load balancing in one-arm mode?

No.

What load balancing options can Rackspace provide in a customer data center?

RPCO supports two models for load balancing in a customer data center:

  • Unmanaged Load Balancers (a.k.a customer managed)
  • Managed Load Balancers
    • Support for hardware based HAProxy
    • Support for hardware based F5 BigIP

What is the load balancer configuration for the reference architecture?

The load balancers should be a high availability (HA) pair, so that at least two load balancers are available to balance the traffic across the infrastructure.

Can the same load balancer be used for service and VM traffic?

This depends on the devices being used. If the HAProxy option is employed, those devices cannot be used to balance Data Plane traffic (they are restricted to Control Plane only). If the F5 BigIP devices are being utilized, those devices can be used to balance Data Plane traffic. The only limitation is the capacity of the physical devices.

What services should be load balanced?

All services should be load balanced, even if the service is running on a single container. This ensures that the traffic is managed by the load balancer and that failovers are graceful.

What if customers require API access to the load balancer to manage floating IP addresses and VIP pools?

RPCO does not provide customer API access to any Control Plane load balancers. RPCO also does not support customer API access to the F5 Local Traffic Manager (LTM). A separate customer-managed LTM must be configured to handle VM (Data Plane) Load Balancing.

Previous Failover and high availability
Next Log aggregation and management
Developer Network
  • Developer Center
  • API Documentation and User Guides
  • SDKs
  • Rackspace How-To
Blogs
  • Technical Blog
  • Rackspace Blog
  • Solve: Thought Leadership
Other Information
  • Customer Stories
  • Events
  • Programs
  • Careers
  • Style Guide for Technical Content
©2020 Rackspace US, Inc.
  • ©2020 Rackspace US, Inc.
  • About Rackspace
  • Privacy Statement
  • Website Terms
  • Trademarks