Configuration Guide¶
A brief introduction to configure Tricircle service. Only the configuration items for Tricircle will be described here. Logging, messaging, database, keystonemiddleware etc configuration which are generated from OpenStack Oslo library, will not be described here. Since these configuration items are common to Nova, Cinder, Neutron. Please refer to corresponding description from Nova, Cinder or Neutron.
Common Options¶
In the common configuration options, the group of “client” need to be configured in Admin API, XJob, Local Plugin and Central Plugin. The “tricircle_db_connection” should be configured in Admin API, XJob and Central Plugin.
Configuration option = Default value |
Description |
|---|---|
[DEFAULT] |
|
|
(String) database connection string for Tricircle, for example, mysql+pymysql://root:password@127.0.0.1/tricircle?charset=utf8 |
[client] |
|
|
(String) password of admin account, needed when auto_refresh_endpoint set to True, for example, password. |
|
(String) tenant name of admin account, needed when auto_refresh_endpoint set to True, for example, demo. |
|
(String) tenant domain name of admin account, needed when auto_refresh_endpoint set to True. |
|
(String) user domain name of admin account, needed when auto_refresh_endpoint set to True. |
|
(String) username of admin account, needed when auto_refresh_endpoint set to True. |
|
(String) keystone authorization url, it’s basically the internal or public endpoint of keystone, depends on how the common.client module can reach keystone, for example, http://$service_host/identity |
|
[Deprecated] (String) keystone service url, for example, http://$service_host/identity/v3 (this option is not used in code since Pike release, you can simply ignore this option) |
|
(Boolean) if set to True, endpoint will be automatically refreshed if timeout accessing endpoint. |
|
(String) cidr pool of the bridge network, for example, 100.0.0.0/9 |
|
(Integer) timeout for neutron client in seconds. |
|
(String) region name of Central Neutron in which client needs to access, for example, CentralRegion. |
|
(String) Cross-pod VxLAN networking support mode, possible choices are p2p l2gw and noop |
Tricircle Admin API Settings¶
Tricircle Admin API servers for managing the mapping between OpenStack instances and availability zone, retrieving object uuid routing and exposing API for maintenance. The following items should be configured in Tricircle’s api.conf.
Configuration option = Default value |
Description |
|---|---|
[DEFAULT] |
|
|
(Integer) The port to bind to |
|
(String) The type of authentication to use |
|
(String) The host IP to bind to |
|
(Integer) The port to bind to |
Tricircle XJob Settings¶
Tricircle XJob serves for receiving and processing cross Neutron functionality and other async jobs from Admin API or Tricircle Central Neutron Plugin. The following items should be configured in Tricircle’s xjob.conf.
Configuration option = Default value |
Description |
|---|---|
[DEFAULT] |
|
|
(Boolean) Enable periodic tasks |
|
(Integer) Range of seconds to randomly delay when starting the periodic task scheduler to reduce stampeding. (Disable by setting to 0) |
|
(Integer) Seconds between nodes reporting state to datastore |
|
(String) The host name for RPC server, each node should have different host name. |
|
(Integer) Running job is considered expires after this time, in seconds |
|
(Integer) Number of workers |
|
(Integer) Timeout for worker’s one turn of processing, in seconds |
|
(Float) Seconds a worker sleeps after one run in a loop |
|
(Integer) Time span in seconds, we calculate the latest job timestamp by subtracting this time span from the current timestamp, jobs created between these two timestamps will be redone |
Networking Setting for Tricircle¶
To make the networking automation work, two plugins need to be configured: Tricircle Central Neutron Plugin and Tricircle Local Neutron Plugin.
Tricircle Central Neutron Plugin
The Tricircle Central Neutron Plugin serves for tenant level L2/L3 networking automation across multiple Neutron servers. The following items should be configured in central Neutron’s neutron.conf.
Configuration option = Default value |
Description |
|---|---|
[DEFAULT] |
|
|
(String) core plugin central Neutron server uses, should be set to tricircle.network.central_plugin.TricirclePlugin |
[tricircle] |
|
|
(String) Type of l3 bridge network, this type should be enabled in tenant_network_types and is not local type, for example, vlan or vxlan. |
|
(String) Default region where the external network belongs to, it must exist, for example, RegionOne. |
|
(String) List of <physical_network>:<vlan_min>:<vlan_max> or <physical_network> specifying physical_network names usable for VLAN provider and tenant networks, as well as ranges of VLAN tags on each available for allocation to tenant networks, for example, bridge:2001:3000. |
|
(String) Ordered list of network_types to allocate as tenant networks. The default value “local” is useful for single pod connectivity, for example, local vlan and vxlan. |
|
(String) List of network type driver entry points to be loaded from the tricircle.network.type_drivers namespace, for example, local vlan and vxlan. |
|
(String) Comma-separated list of <vni_min>:<vni_max> tuples enumerating ranges of VXLAN VNI IDs that are available for tenant network allocation, for example, 1001:2000 |
|
(String) List of physical_network names with which flat networks can be created. Use default ‘*’ to allow flat networks with arbitrary physical_network names. Use an empty list to disable flat networks. |
Tricircle Local Neutron Plugin
The Tricircle Local Neutron Plugin serves for cross Neutron networking automation triggering. It is a shim layer between real core plugin and Neutron API server. The following items should be configured in local Neutron’s neutron.conf
Configuration option = Default value |
Description and Example |
|---|---|
[DEFAULT] |
|
|
(String) core plugin local Neutron server uses, should be set to tricircle.network.local_plugin.TricirclePlugin |
[tricircle] |
|
|
(String) Central Neutron server url, for example, http://$service_host:9696 |
|
(String) The core plugin the Tricircle local plugin will invoke, for example, neutron.plugins.ml2.plugin.Ml2Plugin |
Tricircle Local Neutron L3 Plugin
In multiple OpenStack clouds, if the external network is located in the first OpenStack cloud, but the port which will be associated with one floating ip is located in the second OpenStack cloud, then the network for this port may not be able to be added to the router in the first OpenStack. In Tricircle, to address this scenario, a bridge network will be used to connect the routers in these two OpenStack clouds if the network is not a cross Neutron L2 network. To make it happen, the Tricircle Local Neutron L3 Plugin or other L3 service plugin should be able to associate a floating ip to a port whose network is not directly attached to the router. TricircleL3Plugin is inherited from Neutron original L3RouterPlugin, and overrides the original “get_router_for_floatingip” implementation to allow associating a floating ip to a port whose network is not directly attached to the router. If you want to configure local Neutron to use original L3RouterPlugin, then you need to patch the function “get_router_for_floatingip” as what has been done in TricircleL3Plugin.
If only cross Neutron L2 networking is needed in the deployment, it’s not necessary to configure the service plugins.
The following item should be configured in local Neutron’s neutron.conf
Configuration option = Default value |
Description and Example |
|---|---|
[DEFAULT] |
|
|
(String) service plugins local Neutron server uses, can be set to tricircle.network.local_l3_plugin.TricircleL3Plugin |
Except where otherwise noted, this document is licensed under Creative Commons Attribution 3.0 License. See all OpenStack Legal Documents.