5 File formats

3,927 pages in section 5.

o2

o2cb.sysconfig Cluster configuration file for the o2cb cluster stack.

ob

object-expirer.conf configuration file for the OpenStack Swift object expirer daemon
object-server.conf configuration file for the OpenStack Swift object server

oc

od

og

oglerc ogle configuration file

oi

ol

oo

op

or

os

ou

ov

ovdb Overview storage method for INN
override.conf logwatch configuration files
overview.ctl configuration file for unified overview
overview.fmt format of news overview database
ovn-ic-nb OVN_IC_Northbound database schema This database is the interface for cloud management system (CMS), such as OpenStack, to configure OVN interconnection settings. The CMS produces almost all of the contents of the database. The ovn-ic program monitors the database contents, transforms it, and stores it into the OVN_IC_Southbound database. We generally speak of ``the’’ CMS, but one can imagine scenarios in which multiple CMSes manage different parts of OVN interconnection.
ovn-ic-sb OVN_IC_Southbound database schema This database holds configuration and state for interconnecting different OVN deployments. The content of the database is populated and used by the ovn-ic program in each OVN deployment, and not supposed to be directly used by CMS or end user. The OVN Interconnection Southbound database is shared by ovn-ic program in each OVN deployment. It contains interconnection information from all related OVN deployments, and is used as the intermediate store for each OVN deployment to exchange the information. The ovn-ic program in each deployment is responsible for syncing the data between this database and the its own northbound and southbound databases.
ovn-nb OVN_Northbound database schema This database is the interface between OVN and the cloud management system (CMS), such as OpenStack, running above it. The CMS produces almost all of the contents of the database. The ovn-northd program monitors the database contents, transforms it, and stores it into the OVN_Southbound database. We generally speak of ``the’’ CMS, but one can imagine scenarios in which multiple CMSes manage different parts of an OVN deployment.
ovn-sb OVN_Southbound database schema This database holds logical and physical configuration and state for the Open Virtual Network (OVN) system to support virtual network abstraction. For an introduction to OVN, please see ovn-architecture(7). The OVN Southbound database sits at the center of the OVN architecture. It is the one component that speaks both southbound directly to all the hypervisors and gateways, via ovn-controller/ovn-controller-vtep, and northbound to the Cloud Management System, via ovn-northd:
ovs-vswitchd.conf.db Open_vSwitch database schema A database with this schema holds the configuration for one Open vSwitch daemon. The top-level configuration for the daemon is the Open_vSwitch table, which must have exactly one record. Records in other tables are significant only when they can be reached directly or indirectly from the Open_vSwitch table. Records that are not reachable from the Open_vSwitch table are automatically deleted from the database, except for records in a few distinguished ``root set’’ tables.
ovsdb Open vSwitch Database (File Formats)
ovsdb-server _Server database schema Every ovsdb-server (version 2.9 or later) always hosts an instance of this schema, which holds information on the status and configuration of the server itself. This database is read-only. This manpage describes the schema for this database.
ovsdb.local-config Local_Config database schema This database is for local configuration of an ovsdb-server. The database is meant to be unique, even among multiple clustered db servers, so that configuration that is local to that server can be configured separately (e.g. Connection information).
ovsqlite SQLite-based overview storage method for INN

ow