Adding a New Compute Node to Existing Contrail Cluster
We recommend using Contrail Command to add compute nodes to existing Contrail clusters in most Contrail Networking deployments. See Adding a New Compute Node to Existing Contrail Cluster Using Contrail Command.
The procedure in this document should only be performed by network administrators with significant YAML file expertise in environments not using the Contrail Command GUI.
This is initial process for adding a new compute node to existing Contrail OpenStack cluster.
Assume Contrail cluster is successfully provisioned by the following instances.yaml file.
The password values in this output are included for illustrative purposes only. We strongly recommend creating a unique username and password combination whenever possible.
provider_config:
bms:
ssh_pwd: c0ntrail123
ssh_user: root
ntpserver: x.x.x.x
domainsuffix: local
instances:
srvr1:
provider: bms
ip: 192.168.1.51
roles:
config_database:
config:
control:
analytics_database:
analytics:
webui:
openstack:
srvr2:
provider: bms
ip: 192.168.1.52
roles:
config_database:
config:
control:
analytics_database:
analytics:
webui:
openstack:
srvr3:
provider: bms
ip: 192.168.1.53
roles:
config_database:
config:
control:
analytics_database:
analytics:
webui:
openstack:
srvr4:
provider: bms
ip: 192.168.1.54
roles:
vrouter:
openstack_compute:
contrail_configuration:
CONTRAIL_VERSION: 5.1.0-0.40-ocata
CONTROL_DATA_NET_LIST: 192.168.10.0/24
RABBITMQ_NODE_PORT: 5673
VROUTER_GATEWAY: 192.168.10.1
IPFABRIC_SERVICE_HOST: 192.168.10.150
KEYSTONE_AUTH_URL_VERSION: /v3
kolla_config:
kolla_globals:
kolla_internal_vip_address: 192.168.10.150
kolla_external_vip_address: 192.168.1.150Run the following commands to add a new compute node to an existing Contrail OpenStack cluster.
You can also add or remove a compute node to existing Contrail cluster using Contrail Command UI. For details, refer to Adding a New Compute Node to Existing Contrail Cluster Using Contrail Command.