mir/ovs
2
0
Fork 0
mirror of https://github.com/openvswitch/ovs synced 2025-08-22 01:51:26 +00:00
Code Issues Releases Wiki Activity
ovs/ovsdb/automake.mk

175 lines
5.0 KiB
Makefile
Raw Normal View History

Initial implementation of OVSDB.
2009-11-04 15:11:44 -08:00
# libovsdb
openvswitch: Use libtool and allow building shared libs Currently openvswitch builds all libraries static only. However, libopenvswitch is linked into nearly all openvswitch executables making it hardly possible to run openvswitch on embedded devices (for example running OpenWrt). Convert openvswitch to use libtool for building its internal libs. This allows "--enable-shared" and "--enable-static" as configure arguments. Default is "--disable-shared" thus keeping the current behavior with the only change that static libs are installed by "make install". Since the openvswitch library interfaces are internal and thus not stable (yet) encode the openvswitch version into the library name: libopenvswitch-2.0.90.so Binary size is reduced to around 1/3 when using shared libs. Signed-off-by: Helmut Schaa <helmut.schaa@googlemail.com> Signed-off-by: Ben Pfaff <blp@nicira.com>
2013-12-13 18:54:28 +01:00
lib_LTLIBRARIES += ovsdb/libovsdb.la
Build: Add support for shared libraries and versioning. These changes allow for the building of shared libraries by providing the --enable-shared option to configure. In particular, lib/libopenvwitch.so, lib/libsflow.so, ofproto/libofproto.so, and ovsdb/libovsdb.so will be built. Original behavior of building static remains the same. Additionally, versioning is introduced to each of the libraries objects paving the way for APIs to be built around them. A detailed comment outlining the rules for changing a version number is provided in configure.ac. Note that at this time, the version number is set to 1.0.0, no API is specified yet, and there are no requirements to maintain any sort of compatibility in any of the libraries. Signed-off-by: Scott Mann <smann@noironetworks.com> Signed-off-by: Ben Pfaff <blp@nicira.com>
2014-11-07 19:02:09 -08:00
ovsdb_libovsdb_la_LDFLAGS = \
libX: add new release / version info tags This commit uses the $PACKAGE_VERSION automake variable to construct a release and version info combination which sets the library name to be: libfoo-$(OVS_MAJOR_VERSION).so.$(OVS_MINOR_VERSION).0.$(OVS_MICRO_VERSION) where formerly, it was always: libfoo.so.1.0.0 This allows releases of Open vSwitch libraries to reflect which specific versions they came with, and sets up a psuedo ABI-versioning scheme. In this fashion, future releases of Open vSwitch could be installed alongside older releases, allowing 3rd party utilities linked against previous versions to continue to function. ex: $ ldd /path/to/utility linux-vdso.so.1 (0x00007ffe92cf6000) libopenvswitch-2.so.6 => /lib64/libopenvswitch-2.so.6 (0x00007f733b7a3000) libssl.so.10 => /lib64/libssl.so.10 (0x00007f733b530000) ... Note the library name and version information. Signed-off-by: Aaron Conole <aconole@redhat.com> Signed-off-by: Ben Pfaff <blp@ovn.org>
2017-01-16 14:06:27 -05:00
$(OVS_LTINFO) \
lib: Correctly pass collected AM_LDFLAGS to linker AM_LDFLAGS is not automatically passed to individual library LDFLAGS and must be passed in explicitly. Signed-off-by: Thomas Graf <tgraf@noironetworks.com> Acked-by: Flavio Leitner <fbl@redhat.com> Signed-off-by: Ben Pfaff <blp@nicira.com>
2014-11-12 15:05:59 +01:00
-Wl,--version-script=$(top_builddir)/ovsdb/libovsdb.sym \
$(AM_LDFLAGS)
openvswitch: Use libtool and allow building shared libs Currently openvswitch builds all libraries static only. However, libopenvswitch is linked into nearly all openvswitch executables making it hardly possible to run openvswitch on embedded devices (for example running OpenWrt). Convert openvswitch to use libtool for building its internal libs. This allows "--enable-shared" and "--enable-static" as configure arguments. Default is "--disable-shared" thus keeping the current behavior with the only change that static libs are installed by "make install". Since the openvswitch library interfaces are internal and thus not stable (yet) encode the openvswitch version into the library name: libopenvswitch-2.0.90.so Binary size is reduced to around 1/3 when using shared libs. Signed-off-by: Helmut Schaa <helmut.schaa@googlemail.com> Signed-off-by: Ben Pfaff <blp@nicira.com>
2013-12-13 18:54:28 +01:00
ovsdb_libovsdb_la_SOURCES = \
Initial implementation of OVSDB.
2009-11-04 15:11:44 -08:00
ovsdb/column.c \
ovsdb/column.h \
ovsdb/condition.c \
ovsdb/condition.h \
ovsdb/execution.c \
ovsdb: Add replication support and refactor files in terms of replication. An upcoming commit will add support for replicating tables across JSON-RPC connection. As a prerequisite ovsdb itself must support basic replication. This commit adds that support and then reimplements the ovsdb file storage in terms of that replication.
2009-11-13 13:37:55 -08:00
ovsdb/file.c \
ovsdb/file.h \
Initial implementation of OVSDB.
2009-11-04 15:11:44 -08:00
ovsdb/jsonrpc-server.c \
ovsdb/jsonrpc-server.h \
ovsdb: Rename ovsdb_file to ovsdb_log. This prepares for introducing a new, higher-level ovsdb_file that encapsulates ovsdb storage in a file.
2009-11-13 13:23:35 -08:00
ovsdb/log.c \
ovsdb/log.h \
ovsdb: Add new "mutation" operation to transactions.
2009-12-16 10:49:31 -08:00
ovsdb/mutation.c \
ovsdb/mutation.h \
Initial implementation of OVSDB.
2009-11-04 15:11:44 -08:00
ovsdb/ovsdb.c \
ovsdb/ovsdb.h \
jsonrpc-server: Split out monitor backend functions to monitor.c/h Added new files monitor.[ch] for monitor backend functions. There is no functional changes. Signed-off-by: Andy Zhou <azhou@nicira.com> Acked-by: Ben Pfaff <blp@nicira.com>
2015-03-11 21:20:44 -07:00
ovsdb/monitor.c \
ovsdb/monitor.h \
Initial implementation of OVSDB.
2009-11-04 15:11:44 -08:00
ovsdb/query.c \
ovsdb/query.h \
ovsdb: Introduce experimental support for clustered databases. This commit adds support for OVSDB clustering via Raft. Please read ovsdb(7) for information on how to set up a clustered database. It is simple and boils down to running "ovsdb-tool create-cluster" on one server and "ovsdb-tool join-cluster" on each of the others and then starting ovsdb-server in the usual way on all of them. One you have a clustered database, you configure ovn-controller and ovn-northd to use it by pointing them to all of the servers, e.g. where previously you might have said "tcp:1.2.3.4" was the database server, now you say that it is "tcp:1.2.3.4,tcp:5.6.7.8,tcp:9.10.11.12". This also adds support for database clustering to ovs-sandbox. Acked-by: Justin Pettit <jpettit@ovn.org> Tested-by: aginwala <aginwala@asu.edu> Signed-off-by: Ben Pfaff <blp@ovn.org>
2017-12-31 21:15:58 -08:00
ovsdb/raft.c \
ovsdb/raft.h \
ovsdb/raft-private.c \
ovsdb/raft-private.h \
ovsdb/raft-rpc.c \
ovsdb/raft-rpc.h \
ovsdb: add support for role-based access controls Add suport for ovsdb RBAC (role-based access control). This includes: - Support for "RBAC_Role" table. A db schema containing a table by this name will enable role-based access controls using this table for RBAC role configuration. The "RBAC_Role" table has one row per role, with each row having a "name" column (role name) and a "permissions" column (map of table name to UUID of row in separate permission table.) The permission table has one row per access control configuration, with the following columns: "name" - name of table to which this row applies "authorization" - set of column names and column:key pairs to be compared against client ID to determine authorization status "insert_delete" - boolean, true if insertions and authorized deletions are allowed. "update" - Set of columns and column:key pairs for which authorized updates are allowed. - Support for a new "role" column in the remote configuration table. - Logic for applying the RBAC role and permission tables, in combination with session role from the remote connection table and client id, to determine whether operations modifying database contents should be permitted. - Support for specifying RBAC role string as a command-line option to ovsdb-tool (Ben Pfaff). Signed-off-by: Lance Richardson <lrichard@redhat.com> Co-authored-by: Ben Pfaff <blp@ovn.org> Signed-off-by: Ben Pfaff <blp@ovn.org>
2017-05-31 19:04:32 -04:00
ovsdb/rbac.c \
ovsdb/rbac.h \
ovsdb: Introduce OVSDB replication feature Replication is enabled by using the following option when starting the database server: --sync-from=server Where 'server' can take any form described in the ovsdb-client(1) manpage as an active connection. If this option is specified, the replication process is immediately started. Signed-off-by: Mario Cabrera <mario.cabrera@hpe.com> Signed-off-by: Ben Pfaff <blp@ovn.org>
2016-06-24 17:13:06 -07:00
ovsdb/replication.c \
ovsdb/replication.h \
ovsdb: New ovsdb 'relay' service model. New database service model 'relay' that is needed to scale out read-mostly database access, e.g. ovn-controller connections to OVN_Southbound. In this service model ovsdb-server connects to existing OVSDB server and maintains in-memory copy of the database. It serves read-only transactions and monitor requests by its own, but forwards write transactions to the relay source. Key differences from the active-backup replication: - support for "write" transactions (next commit). - no on-disk storage. (probably, faster operation) - support for multiple remotes (connect to the clustered db). - doesn't try to keep connection as long as possible, but faster reconnects to other remotes to avoid missing updates. - No need to know the complete database schema beforehand, only the schema name. - can be used along with other standalone and clustered databases by the same ovsdb-server process. (doesn't turn the whole jsonrpc server to read-only mode) - supports modern version of monitors (monitor_cond_since), because based on ovsdb-cs. - could be chained, i.e. multiple relays could be connected one to another in a row or in a tree-like form. - doesn't increase availability. - cannot be converted to other service models or become a main active server. Some performance test results can be found here: https://mail.openvswitch.org/pipermail/ovs-dev/2021-July/385825.html Acked-by: Mark D. Gray <mark.d.gray@redhat.com> Acked-by: Dumitru Ceara <dceara@redhat.com> Signed-off-by: Ilya Maximets <i.maximets@ovn.org>
2021-06-01 23:27:36 +02:00
ovsdb/relay.c \
ovsdb/relay.h \
Initial implementation of OVSDB.
2009-11-04 15:11:44 -08:00
ovsdb/row.c \
ovsdb/row.h \
ovsdb: Refactor jsonrpc-server to make the concept of a session public. An upcoming commit will need to expose the concept of a database session to the execution engine, to allow the execution engine to query the locks held by the session. This commit prepares for that by making sessions a publicly visible data structure.
2011-07-26 10:17:36 -07:00
ovsdb/server.c \
ovsdb/server.h \
ovsdb: Introduce experimental support for clustered databases. This commit adds support for OVSDB clustering via Raft. Please read ovsdb(7) for information on how to set up a clustered database. It is simple and boils down to running "ovsdb-tool create-cluster" on one server and "ovsdb-tool join-cluster" on each of the others and then starting ovsdb-server in the usual way on all of them. One you have a clustered database, you configure ovn-controller and ovn-northd to use it by pointing them to all of the servers, e.g. where previously you might have said "tcp:1.2.3.4" was the database server, now you say that it is "tcp:1.2.3.4,tcp:5.6.7.8,tcp:9.10.11.12". This also adds support for database clustering to ovs-sandbox. Acked-by: Justin Pettit <jpettit@ovn.org> Tested-by: aginwala <aginwala@asu.edu> Signed-off-by: Ben Pfaff <blp@ovn.org>
2017-12-31 21:15:58 -08:00
ovsdb/storage.c \
ovsdb/storage.h \
Initial implementation of OVSDB.
2009-11-04 15:11:44 -08:00
ovsdb/table.c \
ovsdb/table.h \
ovsdb/trigger.c \
ovsdb/trigger.h \
ovsdb/transaction.c \
ovsdb: refactor utility functions into separate file Move local db access functions to a new file and make give them global scope so they can be included in the ovsdb library and used by other ovsdb library functions. Signed-off-by: Lance Richardson <lrichard@redhat.com> Signed-off-by: Ben Pfaff <blp@ovn.org>
2017-05-01 10:13:11 -04:00
ovsdb/transaction.h \
ovsdb: relay: Add support for transaction forwarding. Current version of ovsdb relay allows to scale out read-only access to the primary database. However, many clients are not read-only but read-mostly. For example, ovn-controller. In order to scale out database access for this case ovsdb-server need to process transactions that are not read-only. Relay is not allowed to do that, i.e. not allowed to modify the database, but it can act like a proxy and forward transactions that includes database modifications to the primary server and forward replies back to a client. At the same time it may serve read-only transactions and monitor requests by itself greatly reducing the load on primary server. This configuration will slightly increase transaction latency, but it's not very important for read-mostly use cases. Implementation details: With this change instead of creating a trigger to commit the transaction, ovsdb-server will create a trigger for transaction forwarding. Later, ovsdb_relay_run() will send all new transactions to the relay source. Once transaction reply received from the relay source, ovsdb-relay module will update the state of the transaction forwarding with the reply. After that, trigger_run() will complete the trigger and jsonrpc_server_run() will send the reply back to the client. Since transaction reply from the relay source will be received after all the updates, client will receive all the updates before receiving the transaction reply as it is in a normal scenario with other database models. Acked-by: Mark D. Gray <mark.d.gray@redhat.com> Acked-by: Dumitru Ceara <dceara@redhat.com> Signed-off-by: Ilya Maximets <i.maximets@ovn.org>
2021-04-15 19:05:40 +02:00
ovsdb/transaction-forward.c \
ovsdb/transaction-forward.h \
ovsdb: refactor utility functions into separate file Move local db access functions to a new file and make give them global scope so they can be included in the ovsdb library and used by other ovsdb library functions. Signed-off-by: Lance Richardson <lrichard@redhat.com> Signed-off-by: Ben Pfaff <blp@ovn.org>
2017-05-01 10:13:11 -04:00
ovsdb/ovsdb-util.c \
ovsdb/ovsdb-util.h
openvswitch: Use libtool and allow building shared libs Currently openvswitch builds all libraries static only. However, libopenvswitch is linked into nearly all openvswitch executables making it hardly possible to run openvswitch on embedded devices (for example running OpenWrt). Convert openvswitch to use libtool for building its internal libs. This allows "--enable-shared" and "--enable-static" as configure arguments. Default is "--disable-shared" thus keeping the current behavior with the only change that static libs are installed by "make install". Since the openvswitch library interfaces are internal and thus not stable (yet) encode the openvswitch version into the library name: libopenvswitch-2.0.90.so Binary size is reduced to around 1/3 when using shared libs. Signed-off-by: Helmut Schaa <helmut.schaa@googlemail.com> Signed-off-by: Ben Pfaff <blp@nicira.com>
2013-12-13 18:54:28 +01:00
ovsdb_libovsdb_la_CFLAGS = $(AM_CFLAGS)
ovsdb_libovsdb_la_CPPFLAGS = $(AM_CPPFLAGS)
lib: Add support for pkgconfig for libovsdb. Signed-off-by: Thomas Graf <tgraf@noironetworks.com> Acked-by: Flavio Leitner <fbl@redhat.com> Signed-off-by: Ben Pfaff <blp@nicira.com>
2014-11-13 12:28:43 +01:00
pkgconfig_DATA += \
libX.pc: use the correct output directory When the ovsdb library pkgconfig changes were introduced, they placed generated output in the src directory. This is incorrect, however, as the output files should actually be placed in the build directory. It is only seen when running `make distcheck` after enabling shared libraries (ex: `./configure --enable-shared`). Fixes: commit e72e07a97e95 ("lib: Add support for pkgconfig for libovsdb.") Signed-off-by: Aaron Conole <aconole@redhat.com> Signed-off-by: Ben Pfaff <blp@ovn.org>
2017-01-26 14:07:00 -05:00
ovsdb/libovsdb.pc
lib: Add support for pkgconfig for libovsdb. Signed-off-by: Thomas Graf <tgraf@noironetworks.com> Acked-by: Flavio Leitner <fbl@redhat.com> Signed-off-by: Ben Pfaff <blp@nicira.com>
2014-11-13 12:28:43 +01:00
ovsdb: Improve documentation. Signed-off-by: Ben Pfaff <blp@ovn.org> Acked-by: Justin Pettit <jpettit@ovn.org>
2017-12-14 11:17:23 -08:00
MAN_FRAGMENTS += ovsdb/ovsdb-schemas.man
ovsdb: add xml equivalents of remote man page fragments Add XML equivalents for remote-active.man and remote-passive.man for inclusion by man pages using XML format. Signed-off-by: Lance Richardson <lrichard@redhat.com> Signed-off-by: Ben Pfaff <blp@ovn.org>
2017-04-24 14:57:11 -04:00
Initial implementation of OVSDB.
2009-11-04 15:11:44 -08:00
# ovsdb-tool
bin_PROGRAMS += ovsdb/ovsdb-tool
ovsdb_ovsdb_tool_SOURCES = ovsdb/ovsdb-tool.c
Makefile: Remove unnecessary includes of SSL_LIBS. SSL_LIBS are needed for libopenvswitch and we include that in lib/automake.mk. It is not necessary to include it for every executable. Signed-off-by: Gurucharan Shetty <gshetty@nicira.com> Acked-by: Ben Pfaff <blp@nicira.com>
2014-03-04 13:23:53 -08:00
ovsdb_ovsdb_tool_LDADD = ovsdb/libovsdb.la lib/libopenvswitch.la
ovsdb: Add documentation for ovsdb-server and ovsdb-tool programs.
2009-11-06 15:35:10 -08:00
# ovsdb-tool.1
man_MANS += ovsdb/ovsdb-tool.1
Remove build-time generated files when "make clean" is run. "make clean" should remove all files generated by building a program, while "make distclean" should also remove files generated by configuring the program. Previously some generated files during the build process, such as man pages, were left behind when "make clean" was run. This commit only leaves configuration files after "make clean" is run, and removes all other generated files. Signed-off-by: Justin Pettit <jpettit@ovn.org> Acked-by: Ben Pfaff <blp@ovn.org>
2017-02-13 17:20:56 -08:00
CLEANFILES += ovsdb/ovsdb-tool.1
Implement automatic dependency generation for manpages. This ensures that manpages actually get rebuilt if any of the lib/*.man fragments that they depend upon are modified.
2011-10-26 16:06:37 -07:00
MAN_ROOTS += ovsdb/ovsdb-tool.1.in
Initial implementation of OVSDB.
2009-11-04 15:11:44 -08:00
ovsdb: Add new ovsdb-client program.
2009-11-06 15:35:34 -08:00
# ovsdb-client
bin_PROGRAMS += ovsdb/ovsdb-client
ovsdb_ovsdb_client_SOURCES = ovsdb/ovsdb-client.c
Makefile: Remove unnecessary includes of SSL_LIBS. SSL_LIBS are needed for libopenvswitch and we include that in lib/automake.mk. It is not necessary to include it for every executable. Signed-off-by: Gurucharan Shetty <gshetty@nicira.com> Acked-by: Ben Pfaff <blp@nicira.com>
2014-03-04 13:23:53 -08:00
ovsdb_ovsdb_client_LDADD = ovsdb/libovsdb.la lib/libopenvswitch.la
ovsdb: Add new ovsdb-client program.
2009-11-06 15:35:34 -08:00
# ovsdb-client.1
man_MANS += ovsdb/ovsdb-client.1
Remove build-time generated files when "make clean" is run. "make clean" should remove all files generated by building a program, while "make distclean" should also remove files generated by configuring the program. Previously some generated files during the build process, such as man pages, were left behind when "make clean" was run. This commit only leaves configuration files after "make clean" is run, and removes all other generated files. Signed-off-by: Justin Pettit <jpettit@ovn.org> Acked-by: Ben Pfaff <blp@ovn.org>
2017-02-13 17:20:56 -08:00
CLEANFILES += ovsdb/ovsdb-client.1
Implement automatic dependency generation for manpages. This ensures that manpages actually get rebuilt if any of the lib/*.man fragments that they depend upon are modified.
2011-10-26 16:06:37 -07:00
MAN_ROOTS += ovsdb/ovsdb-client.1.in
ovsdb: Add new ovsdb-client program.
2009-11-06 15:35:34 -08:00
Initial implementation of OVSDB.
2009-11-04 15:11:44 -08:00
# ovsdb-server
sbin_PROGRAMS += ovsdb/ovsdb-server
ovsdb_ovsdb_server_SOURCES = ovsdb/ovsdb-server.c
Makefile: Remove unnecessary includes of SSL_LIBS. SSL_LIBS are needed for libopenvswitch and we include that in lib/automake.mk. It is not necessary to include it for every executable. Signed-off-by: Gurucharan Shetty <gshetty@nicira.com> Acked-by: Ben Pfaff <blp@nicira.com>
2014-03-04 13:23:53 -08:00
ovsdb_ovsdb_server_LDADD = ovsdb/libovsdb.la lib/libopenvswitch.la
ovsdb: Add documentation for ovsdb-server and ovsdb-tool programs.
2009-11-06 15:35:10 -08:00
# ovsdb-server.1
man_MANS += ovsdb/ovsdb-server.1
Remove build-time generated files when "make clean" is run. "make clean" should remove all files generated by building a program, while "make distclean" should also remove files generated by configuring the program. Previously some generated files during the build process, such as man pages, were left behind when "make clean" was run. This commit only leaves configuration files after "make clean" is run, and removes all other generated files. Signed-off-by: Justin Pettit <jpettit@ovn.org> Acked-by: Ben Pfaff <blp@ovn.org>
2017-02-13 17:20:56 -08:00
CLEANFILES += ovsdb/ovsdb-server.1
Implement automatic dependency generation for manpages. This ensures that manpages actually get rebuilt if any of the lib/*.man fragments that they depend upon are modified.
2011-10-26 16:06:37 -07:00
MAN_ROOTS += ovsdb/ovsdb-server.1.in
ovsdb: Add ovsdb IDL compiler to build system. This first stab at any interface definition language and compiler for OVSDB will give other developers a chance to look at it and try to integrate it. The IDL is not actually implemented yet; I am working on that.
2009-11-23 16:07:36 -08:00
# ovsdb-idlc
ovsdb: Remove trailing whitespace This commit removes trailing whitespace from the files in the ovsdb directory.
2010-11-24 01:57:45 -08:00
noinst_SCRIPTS += ovsdb/ovsdb-idlc
Implement automatic dependency generation for manpages. This ensures that manpages actually get rebuilt if any of the lib/*.man fragments that they depend upon are modified.
2011-10-26 16:06:37 -07:00
EXTRA_DIST += ovsdb/ovsdb-idlc.in
MAN_ROOTS += ovsdb/ovsdb-idlc.1
Remove build-time generated files when "make clean" is run. "make clean" should remove all files generated by building a program, while "make distclean" should also remove files generated by configuring the program. Previously some generated files during the build process, such as man pages, were left behind when "make clean" was run. This commit only leaves configuration files after "make clean" is run, and removes all other generated files. Signed-off-by: Justin Pettit <jpettit@ovn.org> Acked-by: Ben Pfaff <blp@ovn.org>
2017-02-13 17:20:56 -08:00
CLEANFILES += ovsdb/ovsdb-idlc
ovsdb: Remove dead Python-related code. Initial versions of commit 8cdf034974 "python: Implement write support in Python IDL for OVSDB" converted the OVSDB schemas to Python code so that their Python clients could just import them. The final version instead read the schemas from a file, but I forgot to remove some code that generated the Python schema modules. This commit removes that code. Reported-by: Ethan Jackson <ethan@nicira.com>
2011-10-18 09:29:54 -07:00
SUFFIXES += .ovsidl .ovsschema
Implement initial Python bindings for Open vSwitch database. These initial bindings pass a few hundred of the corresponding tests for C implementations of various bits of the Open vSwitch library API. The poorest part of them is actually the Python IDL interface in ovs.db.idl, which has not received enough attention yet. It appears to work, but it doesn't yet support writes (transactions) and it is difficult to use. I hope to improve it as it becomes clear what semantics Python applications actually want from an IDL.
2010-08-25 10:26:40 -07:00
OVSDB_IDLC = $(run_python) $(srcdir)/ovsdb/ovsdb-idlc.in
ovsdb: Implement C bindings for IDL.
2009-12-02 11:26:15 -08:00
.ovsidl.c:
Makefiles: Add $(AM_V_GEN) annotations to clean up "make" output. The Open vSwitch "make" output was still pretty verbose even when configured with --enable-silent-rules. This cleans it up. Signed-off-by: Ben Pfaff <blp@nicira.com> Acked-by: Joe Stringer <joestringer@nicira.com>
2014-09-29 14:34:11 -07:00
$(AM_V_GEN)$(OVSDB_IDLC) c-idl-source $< > $@.tmp && mv $@.tmp $@
ovsdb: Implement C bindings for IDL.
2009-12-02 11:26:15 -08:00
.ovsidl.h:
Makefiles: Add $(AM_V_GEN) annotations to clean up "make" output. The Open vSwitch "make" output was still pretty verbose even when configured with --enable-silent-rules. This cleans it up. Signed-off-by: Ben Pfaff <blp@nicira.com> Acked-by: Joe Stringer <joestringer@nicira.com>
2014-09-29 14:34:11 -07:00
$(AM_V_GEN)$(OVSDB_IDLC) c-idl-header $< > $@.tmp && mv $@.tmp $@
Cleanly separate IDL annotations from OVSDB schema information. Until now, the OVSDB IDL annotations have been glommed together with the schema information in a single file, and then we've used ovsdb-idlc to extract the schema from that file. This commit reverses the process: the schema and the annotations are stored separately and then glommed together as necessary at build time. This new arrangement has a few advantages: - We can now easily have multiple different sets of IDL annotations for a single OVSDB schema. For example, some users may not need access to columns that other users do. - Bugs in ovsdb-idlc cannot screw up the underlying schema (as shown by a recent commit).
2010-01-07 15:52:58 -08:00
BUILT_SOURCES += $(OVSIDL_BUILT)
Makefiles: Clean and do not distribute IDL-generated files. IDL-generated files don't need to be distributed, and distributing them puts them in the source directory rather than the build directory, which causes "make distcheck" to fail if any of them need to be remade. To prevent this, this commit this removes them from ..._SOURCES, moving them into nodist_..._SOURCES. IDL-generated files all need to be cleaned, so this commit adds all of them to CLEANFILES wholesale via a single CLEANFILES += $(OVSIDL_BUILT) line in ovsdb/automake.mk, removing the individual additions from various makefiles. With this commit, "make distcheck" passes for me. Signed-off-by: Ben Pfaff <blp@nicira.com> Acked-by: Aaron Conole <aaron@bytheb.org>
2015-07-21 11:15:06 -07:00
CLEANFILES += $(OVSIDL_BUILT)
Cleanly separate IDL annotations from OVSDB schema information. Until now, the OVSDB IDL annotations have been glommed together with the schema information in a single file, and then we've used ovsdb-idlc to extract the schema from that file. This commit reverses the process: the schema and the annotations are stored separately and then glommed together as necessary at build time. This new arrangement has a few advantages: - We can now easily have multiple different sets of IDL annotations for a single OVSDB schema. For example, some users may not need access to columns that other users do. - Bugs in ovsdb-idlc cannot screw up the underlying schema (as shown by a recent commit).
2010-01-07 15:52:58 -08:00
# This must be done late: macros in targets are expanded when the
# target line is read, so if this file were to be included before some
# other file that added to OVSIDL_BUILT, then those files wouldn't get
# the dependency.
#
# However, current versions of Automake seem to output all variable
# assignments before any targets, so it doesn't seem to be a problem,
# at least for now.
python: Update build system to ensure dirs.py is created. Update build system to ensure dirs.py is created when it is a dependency for a build target. Also, update setup.py to check for that dependency. Fixes: 943c4a325045 ("python: set ovs.dirs variables with build system values") Signed-off-by: Mark Gray <mark.d.gray@redhat.com> Signed-off-by: Ilya Maximets <i.maximets@ovn.org>
2020-11-19 03:44:34 -05:00
$(OVSIDL_BUILT): ovsdb/ovsdb-idlc.in python/ovs/dirs.py
Add documentation for the vswitch database schema. We can do better than this (I already have some comments) but this is still much better than what we had.
2010-03-03 14:47:46 -08:00
# ovsdb-doc
ovsdb-doc: Add ovsdb-doc to distribution tar ball. Certain platforms like xenserver do not have the latest python libraries that are needed by ovsdb-doc (which in-turn creates ovs-vswitchd.conf.db.5). When we run 'make dist' and copy over the tar ball to xenserver ddk environemt, we already include ovs-vswitchd.conf.db.5. But the absence of ovsdb-doc results in an attempt to regenerate ovs-vswitchd.conf.db.5 and that fails because of the missing python libraries. Instead of producing ovsdb-doc from ovsdb-doc.in dynamically, we statically provide ovsdb-doc and pass on the version information to it through the command line option --version. Signed-off-by: Gurucharan Shetty <gshetty@nicira.com> Acked-by: Ben Pfaff <blp@nicira.com>
2013-07-31 09:24:46 -07:00
EXTRA_DIST += ovsdb/ovsdb-doc
ovsdb-doc: Fix syntax warning with Python 3.12 and flake8 issues. ovsdb-doc script generates the following syntax warning while running with Python 3.12: /ovsdb/ovsdb-doc:240: SyntaxWarning: invalid escape sequence '\{' s += """ This doesn't cause a build failure because so far it's only a warning, but it will become a syntax error in the future. Fix that by converting to a raw string and removing unnecessary escape sequences. Adding ovsdb-doc to flake8-check to avoid re-introducing issues in the future. This means also fixing all the other issues with the script like unused imports and variables, long lines, missing empty lines, wildcarded imports. Also cleaning up one place that handles compatibility with Python 2 types, since we do not support Python 2 for a long time now. Acked-by: Simon Horman <horms@ovn.org> Signed-off-by: Ilya Maximets <i.maximets@ovn.org>
2024-04-11 00:43:28 +02:00
FLAKE8_PYFILES += ovsdb/ovsdb-doc
ovsdb-doc: Add ovsdb-doc to distribution tar ball. Certain platforms like xenserver do not have the latest python libraries that are needed by ovsdb-doc (which in-turn creates ovs-vswitchd.conf.db.5). When we run 'make dist' and copy over the tar ball to xenserver ddk environemt, we already include ovs-vswitchd.conf.db.5. But the absence of ovsdb-doc results in an attempt to regenerate ovs-vswitchd.conf.db.5 and that fails because of the missing python libraries. Instead of producing ovsdb-doc from ovsdb-doc.in dynamically, we statically provide ovsdb-doc and pass on the version information to it through the command line option --version. Signed-off-by: Gurucharan Shetty <gshetty@nicira.com> Acked-by: Ben Pfaff <blp@nicira.com>
2013-07-31 09:24:46 -07:00
OVSDB_DOC = $(run_python) $(srcdir)/ovsdb/ovsdb-doc
ovsdb-doc: Add build dependency on dirs.py. ovsdb-doc includes python code that requires dirs.py to exist. This change fixes broken 'make manpage-check' target: # make manpage-check Traceback (most recent call last): File "./ovsdb/ovsdb-doc", line 25, in <module> import ovs.db.schema File "/root/ovs/python/ovs/db/schema.py", line 19, in <module> import ovs.db.types File "/root/ovs/python/ovs/db/types.py", line 18, in <module> import ovs.db.data File "/root/ovs/python/ovs/db/data.py", line 22, in <module> import ovs.jsonrpc File "/root/ovs/python/ovs/jsonrpc.py", line 21, in <module> import ovs.poller File "/root/ovs/python/ovs/poller.py", line 23, in <module> import ovs.vlog File "/root/ovs/python/ovs/vlog.py", line 25, in <module> import ovs.dirs ModuleNotFoundError: No module named 'ovs.dirs' Fixes: 943c4a325045 ("python: set ovs.dirs variables with build system values") Acked-by: Mark Gray <mark.d.gray@redhat.com> Signed-off-by: Ilya Maximets <i.maximets@ovn.org>
2021-01-29 13:44:36 +01:00
ovsdb/ovsdb-doc: python/ovs/dirs.py
Add ovsdbmonitor GUI tool by Andy Southgate, contributed by Citrix. With Makefiles and Autoconfiscation by Ben Pfaff. Signed-off-by: Thomas Lacroix <thomas.lacroix@citrix.com> Signed-off-by: Ben Pfaff <blp@nicira.com>
2010-05-11 11:46:52 -07:00
vswitchd: Add entity-relationship diagram to ovs-vswitchd.conf.db.5. I've updated http://openvswitch.org/ovs-vswitchd.conf.db.5.pdf with example output.
2010-06-23 09:41:09 -07:00
# ovsdb-dot
ovsdb: Fix "make dist" by distributing dot2pic.
2010-11-09 10:33:17 -08:00
EXTRA_DIST += ovsdb/ovsdb-dot.in ovsdb/dot2pic
ovsdb-dot: Fix flake8 issues. Missing and extra spaces, missing empty lines, unused imports and variables, long lines. Decided to just comment out the unused 'tail' and 'head' as they seem useful in documenting the meaning of the words. Files added to flake8-check to avoid future issues. Acked-by: Simon Horman <horms@ovn.org> Signed-off-by: Ilya Maximets <i.maximets@ovn.org>
2024-04-11 00:43:29 +02:00
FLAKE8_PYFILES += ovsdb/ovsdb-dot.in ovsdb/dot2pic
vswitchd: Add entity-relationship diagram to ovs-vswitchd.conf.db.5. I've updated http://openvswitch.org/ovs-vswitchd.conf.db.5.pdf with example output.
2010-06-23 09:41:09 -07:00
noinst_SCRIPTS += ovsdb/ovsdb-dot
Remove build-time generated files when "make clean" is run. "make clean" should remove all files generated by building a program, while "make distclean" should also remove files generated by configuring the program. Previously some generated files during the build process, such as man pages, were left behind when "make clean" was run. This commit only leaves configuration files after "make clean" is run, and removes all other generated files. Signed-off-by: Justin Pettit <jpettit@ovn.org> Acked-by: Ben Pfaff <blp@ovn.org>
2017-02-13 17:20:56 -08:00
CLEANFILES += ovsdb/ovsdb-dot
Implement initial Python bindings for Open vSwitch database. These initial bindings pass a few hundred of the corresponding tests for C implementations of various bits of the Open vSwitch library API. The poorest part of them is actually the Python IDL interface in ovs.db.idl, which has not received enough attention yet. It appears to work, but it doesn't yet support writes (transactions) and it is difficult to use. I hope to improve it as it becomes clear what semantics Python applications actually want from an IDL.
2010-08-25 10:26:40 -07:00
OVSDB_DOT = $(run_python) $(srcdir)/ovsdb/ovsdb-dot.in
ovsdb-server: Add support for a built-in _Server database. The _Server database is valuable primarily because it provides database clients a way to find out the details of changes to databases, schemas, etc. in a granular, natural way. Until now, the only way that the server could notify clients about these kinds of changes was to close the session; when the client reconnects, it is expected to reassess the server's state. One way to provide this kind of granular information would be to add specific JSON-RPC requests to obtain notifications for different kinds of changes, but since ovsdb-server already provides granular and flexible notification support for databases, using a database for the purpose is convenient and avoids duplicating functionality. Initially this database only reports databases' names and schemas, but when clustering support is added in a later commit it will also report important aspects of clustering and cluster status. Thus, this database also reduces the need to add JSON-RPC calls to retrieve information about new features. Signed-off-by: Ben Pfaff <blp@ovn.org>
2017-12-15 11:14:55 -08:00
EXTRA_DIST += ovsdb/_server.ovsschema
CLEANFILES += ovsdb/_server.ovsschema.inc
Windows: Fix broken build caused by a bad file extension The compiler (cl) complains: `ovsdb/ovsdb-server.c(689) : fatal error C1083: Cannot open include file: 'ovsdb/_server.ovsschema.inc': No such file or directory` (https://ci.appveyor.com/project/blp/ovs/build/1.0.4079#L2586) Generated compiler objects have the extension `.obj` on Windows. This patch switches to `$(OBJEXT)` instead, so the schema will be generated. Signed-off-by: Alin Gabriel Serdean aserdean@ovn.org Acked-by: Ben Pfaff <blp@ovn.org>
2018-03-27 20:29:49 +03:00
ovsdb/ovsdb-server.$(OBJEXT): ovsdb/_server.ovsschema.inc
ovsdb-server: Add support for a built-in _Server database. The _Server database is valuable primarily because it provides database clients a way to find out the details of changes to databases, schemas, etc. in a granular, natural way. Until now, the only way that the server could notify clients about these kinds of changes was to close the session; when the client reconnects, it is expected to reassess the server's state. One way to provide this kind of granular information would be to add specific JSON-RPC requests to obtain notifications for different kinds of changes, but since ovsdb-server already provides granular and flexible notification support for databases, using a database for the purpose is convenient and avoids duplicating functionality. Initially this database only reports databases' names and schemas, but when clustering support is added in a later commit it will also report important aspects of clustering and cluster status. Thus, this database also reduces the need to add JSON-RPC calls to retrieve information about new features. Signed-off-by: Ben Pfaff <blp@ovn.org>
2017-12-15 11:14:55 -08:00
ovsdb/_server.ovsschema.inc: ovsdb/_server.ovsschema $(srcdir)/build-aux/text2c
$(AM_V_GEN)$(run_python) $(srcdir)/build-aux/text2c < $< > $@.tmp
$(AM_V_at)mv $@.tmp $@
# Version checking for _server.ovsschema.
ALL_LOCAL += ovsdb/_server.ovsschema.stamp
ovsdb/_server.ovsschema.stamp: ovsdb/_server.ovsschema
$(srcdir)/build-aux/cksum-schema-check $? $@
CLEANFILES += ovsdb/_server.ovsschema.stamp
# _Server schema documentation
EXTRA_DIST += ovsdb/_server.xml
CLEANFILES += ovsdb/ovsdb-server.5
man_MANS += ovsdb/ovsdb-server.5
ovsdb/ovsdb-server.5: \
ovsdb/ovsdb-doc ovsdb/_server.xml ovsdb/_server.ovsschema
$(AM_V_GEN)$(OVSDB_DOC) \
--version=$(VERSION) \
$(srcdir)/ovsdb/_server.ovsschema \
$(srcdir)/ovsdb/_server.xml > $@.tmp && \
mv $@.tmp $@
ovsdb: Introduce experimental support for clustered databases. This commit adds support for OVSDB clustering via Raft. Please read ovsdb(7) for information on how to set up a clustered database. It is simple and boils down to running "ovsdb-tool create-cluster" on one server and "ovsdb-tool join-cluster" on each of the others and then starting ovsdb-server in the usual way on all of them. One you have a clustered database, you configure ovn-controller and ovn-northd to use it by pointing them to all of the servers, e.g. where previously you might have said "tcp:1.2.3.4" was the database server, now you say that it is "tcp:1.2.3.4,tcp:5.6.7.8,tcp:9.10.11.12". This also adds support for database clustering to ovs-sandbox. Acked-by: Justin Pettit <jpettit@ovn.org> Tested-by: aginwala <aginwala@asu.edu> Signed-off-by: Ben Pfaff <blp@ovn.org>
2017-12-31 21:15:58 -08:00
ovsdb: Add Local_Config schema. The only way to configure settings on a remote (e.g. inactivity_probe) is via --remote=db:DB,table,row. There is no way to do this via the existing CLI options. For a clustered DB with multiple servers listening on unique addresses there is no way to store these entries in the DB as the DB is shared. For example, three servers listening on 1.1.1.1, 1.1.1.2, and 1.1.1.3 respectively would require a Manager/Connection row each, but then all three servers would try to listen on all three addresses. It is possible for ovsdb-server to serve multiple databases. This means that we can have a local "config" database in addition to the main database we are serving (Open_vSwitch, OVN_Southbound, etc.) and this patch adds a Local_Config schema that currently just mirrors the Connection table and a Config table with a 'connections' row that stores each Connection. Signed-off-by: Terry Wilson <twilson@redhat.com> Acked-by: Dumitru Ceara <dceara@redhat.com> Signed-off-by: Ilya Maximets <i.maximets@ovn.org>
2022-06-28 09:54:45 -05:00
EXTRA_DIST += ovsdb/local-config.ovsschema
pkgdata_DATA += ovsdb/local-config.ovsschema
# Version checking for local-config.ovsschema.
ALL_LOCAL += ovsdb/local-config.ovsschema.stamp
ovsdb/local-config.ovsschema.stamp: ovsdb/local-config.ovsschema
$(srcdir)/build-aux/cksum-schema-check $? $@
CLEANFILES += ovsdb/local-config.ovsschema.stamp
# Local_Config schema documentation
EXTRA_DIST += ovsdb/local-config.xml
CLEANFILES += ovsdb/ovsdb.local-config.5
man_MANS += ovsdb/ovsdb.local-config.5
ovsdb/ovsdb.local-config.5: \
ovsdb: Remove extra make target dependency for local-config.5. ovsdb/ directory should not be a dependency, otherwise the man page is getting re-built every time unrelated files are changed. Fixes: 6f24c2bc769a ("ovsdb: Add Local_Config schema.") Acked-by: Dumitru Ceara <dceara@redhat.com> Signed-off-by: Ilya Maximets <i.maximets@ovn.org>
2022-07-15 18:04:10 +02:00
ovsdb/ovsdb-doc ovsdb/local-config.xml ovsdb/local-config.ovsschema
ovsdb: Add Local_Config schema. The only way to configure settings on a remote (e.g. inactivity_probe) is via --remote=db:DB,table,row. There is no way to do this via the existing CLI options. For a clustered DB with multiple servers listening on unique addresses there is no way to store these entries in the DB as the DB is shared. For example, three servers listening on 1.1.1.1, 1.1.1.2, and 1.1.1.3 respectively would require a Manager/Connection row each, but then all three servers would try to listen on all three addresses. It is possible for ovsdb-server to serve multiple databases. This means that we can have a local "config" database in addition to the main database we are serving (Open_vSwitch, OVN_Southbound, etc.) and this patch adds a Local_Config schema that currently just mirrors the Connection table and a Config table with a 'connections' row that stores each Connection. Signed-off-by: Terry Wilson <twilson@redhat.com> Acked-by: Dumitru Ceara <dceara@redhat.com> Signed-off-by: Ilya Maximets <i.maximets@ovn.org>
2022-06-28 09:54:45 -05:00
$(AM_V_GEN)$(OVSDB_DOC) \
--version=$(VERSION) \
$(srcdir)/ovsdb/local-config.ovsschema \
$(srcdir)/ovsdb/local-config.xml > $@.tmp && \
mv $@.tmp $@
ovsdb: Introduce experimental support for clustered databases. This commit adds support for OVSDB clustering via Raft. Please read ovsdb(7) for information on how to set up a clustered database. It is simple and boils down to running "ovsdb-tool create-cluster" on one server and "ovsdb-tool join-cluster" on each of the others and then starting ovsdb-server in the usual way on all of them. One you have a clustered database, you configure ovn-controller and ovn-northd to use it by pointing them to all of the servers, e.g. where previously you might have said "tcp:1.2.3.4" was the database server, now you say that it is "tcp:1.2.3.4,tcp:5.6.7.8,tcp:9.10.11.12". This also adds support for database clustering to ovs-sandbox. Acked-by: Justin Pettit <jpettit@ovn.org> Tested-by: aginwala <aginwala@asu.edu> Signed-off-by: Ben Pfaff <blp@ovn.org>
2017-12-31 21:15:58 -08:00
EXTRA_DIST += ovsdb/TODO.rst
Reference in New Issue Copy Permalink