aboutsummaryrefslogtreecommitdiff
path: root/docker/common/openvswitch/ovs-vswitchd/start.sh
AgeCommit message (Collapse)AuthorFilesLines
2015-08-28Move scripts for openvswitch to docker_templatesSteven Dake1-19/+0
Change-Id: I04e804bb36daf53ce2eb0db804008deb7ebc6b11 Partially-Implements: blueprint remove-docker-dir
2015-08-07Remove config-internal for openvswitchSam Yaple1-1/+1
Change-Id: I4b8f275b670a1ac3b72b2af34b53bddca4a63cb2 Partially-Implements: blueprint remove-config-internal
2015-07-09Add config-internal/config-external to OpenvSwitch containersdigambar1-6/+11
Partially Implements: Blueprint standard-start Co-Authored-By: Swapnil Kulkarni <me@coolsvap.net> Change-Id: I52ed4b56efe3fc4ebbc108b2fe7e9d69eb0f0928
2015-06-20Add openvswitch containerFang Fenghua1-0/+14
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