We have been using --db-nb-create-insecure-remote=yes - that results a TCP method is set by ovn-ctl script to run ovsdb-server. Downside is - we can't configure inactivity probe on that connection. Closes-Bug: #1917484 Change-Id: I550aa4fe92aadea2a49ca5aff49c0183609b9470
11 lines
778 B
Django/Jinja
11 lines
778 B
Django/Jinja
{
|
|
"command": "/usr/share/ovn/scripts/ovn-ctl run_nb_ovsdb --db-nb-addr={{ api_interface_address | put_address_in_context('url') }} --db-nb-cluster-local-addr={{ api_interface_address | put_address_in_context('url') }} {% if groups['ovn-nb-db'] | length > 1 and inventory_hostname != groups['ovn-nb-db'][0] %} --db-nb-cluster-remote-addr={{ 'api' | kolla_address(groups['ovn-nb-db'][0]) | put_address_in_context('url') }} {% endif %} --db-nb-sock=/run/ovn/ovnnb_db.sock --db-nb-pid=/run/ovn/ovnnb_db.pid --db-nb-file=/var/lib/openvswitch/ovn-nb/ovnnb.db --ovn-nb-logfile=/var/log/kolla/openvswitch/ovn-nb-db.log",
|
|
"permissions": [
|
|
{
|
|
"path": "/var/log/kolla/openvswitch",
|
|
"owner": "root:root",
|
|
"recurse": true
|
|
}
|
|
]
|
|
}
|