anvil/conf/personas/in-a-box/basic-web.yaml
Ivan A. Melnikov d78a4076d6 Configure RPC for neutron and cinder
Cinder, neutron server and neutron plugins communicate via RPC (AMPQ),
so we should configure RPC backend and its parameters same way we do
for nova.

Change-Id: I9c8d8f66d9c4da1fb8d7b09de946c4a0cb31a56d
2013-08-09 18:15:00 +04:00

76 lines
1.2 KiB
YAML

---
components:
# Order matters here!
- general
- db
- rabbit-mq
- oslo-config
- keystone
# Client used by many components
- keystone-client
- glance
# Clients used by nova (+ others)
- glance-client
- cinder-client
- neutron-client
- swift-client # Seems only needed for horizon?
- neutron
- openvswitch
- cinder
- nova
- nova-client
- django-openstack-auth
- horizon
options:
nova:
db-sync: true
do-network-init: true
mq-type: rabbit
enable-cells: false
enable-spice: false
local-conductor: false
neutron-enabled: true
neutron-core-plugin: linuxbridge
glance:
db-sync: true
load-images: true
keystone:
db-sync: true
do-init: true
enable-pki: false
horizon:
make-blackhole: true
cinder:
db-sync: true
mq-type: rabbit
neutron:
db-sync: true
mq-type: rabbit
subsystems:
glance:
- api
- registry
keystone:
- all
nova:
- api
- cert
- compute
- conductor
- consoleauth
- network
- scheduler
- xvpvncproxy
- spicehtml5proxy
neutron:
- server
- agent
- l3-agent
cinder:
- api
- scheduler
- volume
supports:
- rhel
...