Using the ovn-ctl script to start the OVN ovsdb-server is the better
way. This script is used to start and stop all OVN systemd services.
This script takes care of creating the database from the schema,
updating the database from the schema when the schema version gets
updated.
The present scripts - start_nb_db_server.sh and start_sb_db_server.sh
doesn't take care of schema updates.
With this, we don't need extend_start.sh in ovn-nb-db-server/ovn-sb-db-server
to create the database from the schema.
This patch also deletes kolla_ovn_extend_start from the ovn-base image as it
is not required.
Closes-bug: 1850025
Change-Id: I31a372d801dace92950cd85b29b308431f78bbdb
OVN has been split out from openvswitch and it's code is here [1].
With the split we have changed the ovn runtime/data dirs to
/etc/ovn and /usr/share/ovn respectively.
If a user uses latest OVN (when used after the split from
openvswitch), then the extend_start.sh of ovn-nb-db-server and
ovn-sb-db-server will fail because the OVN schema files will be in different
location (new location is /usr/share/ovn/ovn-nb.ovschema and /usr/share/ovn/ovn-sb.ovschema)
The old location is - /usr/share/openvswitch/ovn-nb.ovschema and
/usr/share/openvswitch/ovn-sb.ovschema
This patch checks for the presence of the schema files in the old location before
accessing them.
For latest OVN, it is advisable to use the "ovn-ctl" script to start
and stop OVN ovsdb-servers. ovn-citl script takes care of creating the dbs
and updating the dbs if the schema is updated.
[1] - https://github.com/ovn-org/ovnf3e24610ea
Change-Id: If2bab2fac5be28ae7e1cd02de13a2de94fe17bac
Closes-bug: 1849633
Signed-off-by: Numan Siddique <nusiddiq@redhat.com>
This patch adds kolla images for
- ovn-northd
- ovn-controller
- ovsdb-server for Northbound DB
- ovsdb-server for Southbound DB
Change-Id: I97f82395cb14108bdff57543e4847a5ece17fe69
Implements: blueprint ovn-controller-neutron
Signed-off-by: Numan Siddique <nusiddiq@redhat.com>
Numan Siddique