Ansible will exec a script in the OVS container to ensure the bridge and
ports are properly setup. The script is idempotent.
Change-Id: I5adca595a4d2ef4edf26c9635cfa5ceb30ca4a59
Closes-Bug: #1466375
Many of these were actually files containing the path to the real
script, instead of being symlinks.
config-{internal,external}.sh files in openvswitch/ovs-base were not
needed and were thus deleted.
Also update minimal-environment-vars.md after symlinks were fixed.
Change-Id: I11c3e735067b1feb83c3184c32333e598fbdf590
Closes-Bug: #1474227
Add openvswitch containers. Openvswitch is seperated into two running
containers:
ovs-db-server
ovs-vswitchd
The db container is what everything interacts with. Neutron tells the db
its information, the vswitchd container reads this db and talks to the
kernel module.
The db does not need to be persistent since the plugin agent will
repopulate all the information each time it is restarted and the plugin
agent is required to be restarted when the ovs-vswitchd container is
stopped/started to ensure the ports are setup properly.
This container requires /run for the socket and /lib/modules:ro to load
the appropriate host kernel module.
This userspace tools and the kernel module do _not_ have to match
versions. Additionally, even though it is recommended that the userspace
tool be newer than the kernel version to take advantage of all the
features, it is not required.
Partially Implements blueprint: openvswitch-container
Co-Authored-By: Sam Yaple <sam@yaple.net>
Change-Id: I70e3807be32c9a07346d316e7856421ecf468b9a