Skip to content
Snippets Groups Projects
multinode 2.92 KiB
Newer Older
# These initial groups are the only groups required to be modified. The
# additional groups are for more control of the environment.
Sam Yaple's avatar
Sam Yaple committed
[control]
# These hostname must be resolvable from your deployment host
control01
control02
control03

# The above can also be specified as follows:
#control[01:03]     ansible_ssh_user=kolla
# The network nodes are where your l3-agent and loadbalancers will run
# This can be the same as a host in the control group
[network]
network01

[compute]
compute01

# When compute nodes and control nodes use different interfaces,
# you can specify "api_interface" and another interfaces like below:
#compute01 neutron_external_interface=eth0 api_interface=em1 storage_interface=em1 tunnel_interface=em1

[storage]
storage01
# You can explicitly specify which hosts run each project by updating the
# groups in the sections below. Common services are grouped together.
[haproxy:children]
[mariadb:children]
Sam Yaple's avatar
Sam Yaple committed
control
[rabbitmq:children]
Sam Yaple's avatar
Sam Yaple committed
control
Sam Yaple's avatar
Sam Yaple committed

[keystone:children]
Sam Yaple's avatar
Sam Yaple committed
control
Sam Yaple's avatar
Sam Yaple committed

[glance:children]
Sam Yaple's avatar
Sam Yaple committed
control

[nova:children]
Sam Yaple's avatar
Sam Yaple committed
control
[neutron:children]
network

[cinder:children]
Sam Yaple's avatar
Sam Yaple committed
control
[memcached:children]
control

[horizon:children]
control

[swift:children]
control

[heat:children]
control

[murano:children]
control

[ironic:children]
control

Sam Yaple's avatar
Sam Yaple committed
[ceph-mon:children]
control

Sam Yaple's avatar
Sam Yaple committed
[ceph-osd:children]
storage

[magnum:children]
control

[mistral:children]
control

# Additional control implemented here. These groups allow you to control which
# services run on which hosts at a per-service level.
#
# Word of caution: Some services are required to run on the same host to
# function appropriately. For example, neutron-metadata-agent must run on the
# same host as the l3-agent and (depending on configuration) the dhcp-agent.

# Glance
[glance-api:children]
glance

[glance-registry:children]
glance

# Nova
[nova-api:children]
nova

[nova-conductor:children]
nova

[nova-consoleauth:children]
nova

[nova-novncproxy:children]
nova

[nova-scheduler:children]
nova
[nova-spicehtml5proxy:children]
nova

[nova-compute-ironic:children]
nova

# Neutron
[neutron-server:children]

[neutron-agents:children]
neutron
# Cinder
[cinder-api:children]
cinder

[cinder-backup:children]
storage

[cinder-scheduler:children]
cinder

[cinder-volume:children]
storage

# Swift
[swift-proxy-server:children]

[swift-account-server:children]
storage

[swift-container-server:children]
storage

[swift-object-server:children]
storage

# Heat
[heat-api:children]
heat

[heat-api-cfn:children]
heat

[heat-engine:children]
heat

# Murano
[murano-api:children]
murano

[murano-engine:children]
murano

# Ironic
[ironic-api:children]
ironic

[ironic-conductor:children]
ironic

[ironic-discoverd:children]
ironic

[ironic-pxe:children]
ironic

# Magnum
[magnum-api:children]
magnum

[magnum-conductor:children]
magnum

# Mistral
[mistral-api:children]
mistral

[mistral-executor:children]
mistral

[mistral-engine:children]
mistral