powervc-driver/neutron-powervc/etc/powervc-neutron.conf
Le Tian Ren 0eefba3f77 Add support for multiple AMQP rpc backends
This is based on Oslo messaging API that supports RPC and notifications over a
number of different messsaging transports.

* remove old powervc.common.messaging and create a new one to adapt to Oslo
messaging

* adapt all sync service managers to new messaging model

Change-Id: I0c9b4a9fa5bb5d0eaac1433e768a110871d8dab8
Closes-Bug: 1363618
2014-09-16 17:53:08 +08:00

20 lines
670 B
Plaintext

[DEFAULT]
debug = False
verbose = True
[AGENT]
# Agent's polling interval in seconds
polling_interval = 60
# (ListOpt) Comma-separated list of PowerVC network names to be mapped to
# local OS as networks. If the network does not exist in the local OS, it
# will be automatically created. PowerVC networks listed here do not have
# to exist prior to starting up the powervc_neutron_agent. Wildcard
# characters ('*') can be specified. By default, all PowerVC networks will
# be available in the local OS.
# map_powervc_networks = *
[DATABASE]
# Database where agent will store mapping data
connection = mysql://root:openstack1@localhost/powervc?charset=utf8