File: overview.rst

package info (click to toggle)
python-ovsdbapp 2.13.0-2
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid
  • size: 1,040 kB
  • sloc: python: 9,222; sh: 138; makefile: 21
file content (48 lines) | stat: -rw-r--r-- 2,122 bytes parent folder | download | duplicates (2)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
========
Overview
========

OVSDBapp is a library to make it easier to write applications that interact
with an Open vSwitch database server. It allows the user to separate support
for a particular OVSDB schema and the backend method of communication with the
OVSDB server.

OVSDBapp Concepts
-----------------

API
  The interface that an application will use for reading or modifying entries
  in the OVS database. Whatever backend communication method is used, as long
  as user code only accesses methods in this API, no user code should need to
  be changed when swapping between backends.
Backend
  The Backend handles the communication with Open vSwitch. Originally, there
  were two OVSDBapp backends: 1) one that used the ovs-vsctl CLI utility to
  interact with the OVS database and 2) one that maintains a persistent
  connection to an OVSDB server using the python-ovs library. Currently, only
  the python-ovs backend is being maintained.
Command
  OVSDBapp uses the `Command Pattern`_ to isolate individual units of work
  that will be run as part of an OVSDB transaction.
Event
  OVSDB provides the ability to monitor database changes as they happen.
  OVSDBapp backends each implement the :code:`RowEvent` and
  :code:`RowEventHandler` to handle delivering these events to user code.
API Implementations:
  The backend-specific implementation of an OVSDBapp API. Only this code
  should need to be implemented to support a new backend. All other user
  code should be backend-agnostic.
Schema
  The OVSDB database schema for which the API is implemented. In current
  ovsdbapp code, the schema and API are intrinsically linked in a
  1:1 manner, but ultimately they are independent. User code could easily
  define an API specific to their application that encompasses multiple
  OVSDB schemas as long as the Backend supported it.
Transaction
  An OVSDB transaction consisting of one or more Commands.
Virtual Environment
  OVSDBapp supports running OVS and OVN services in a virtual environment.
  This is primarily used for testing.


  .. _Command Pattern: https://en.wikipedia.org/wiki/Command_pattern