Scaling Up Contrail Networking Configuration API
Starting from Contrail Networking Release 2011, config-api can be scaled vertically, to run up to 10 workers in a single container by using uWSGI. However, the recommended maximum number of workers in each config_api container is 5.
The steps described in this topic are valid for Contrail Networking Releases 2011 and later releases. To see these procedures for earlier releases, seeScaling Up Contrail Networking Configuration API Server Instances.
From Contrail Ansible Deployer
If you are deploying Contrail Networking using Ansible Deployer
, you should specify CONFIG_API_WORKER_COUNT parameter
in the contrail_configuration section of the instances.yml file as
shown below.
contrail_configuration: CONFIG_API_WORKER_COUNT: 5
From Contrail Command UI
If you are deploying Contrail Networking from Contrail Command UI, you should specify a new key / value pair (CONFIG_API_WORKER_COUNT / value) in the Contrail Configuration section as shown in Figure 1.
From RHOSP Deployer
If you are deploying Contrail Networking using RHOSP deployer,
you should specify the desired value for the parameter CONFIG_API_WORKER_COUNT in the ContrailSettings section of the contrail-services.yaml
file as shown below.
ContrailSettings: CONFIG_API_WORKER_COUNT: 3
From JUJU Deployer
If you are deploying Contrail Networking using JUJU deployer,
you must specify the desired value for config-api-worker-count in the config.yaml file.
config-api-worker-count:
default: 1
type: int
description: |
Number of workers spawned inside config-api container.