61a0350695
This patch implements /NetworkDriver.Join, which goes through the following steps: 1. Find the Neutron port associated with the given EndpointID 2. Create the veth pair based on the info of the retrieved port 3. Bind the port to the veth endpoint 4. Construct the response with the port and return it In the process 3, Kuryr executes the binding script specified in the binding:vif_type attribute of the retrieved Neutron port. Although Neutron plugin can put arbitrary types in that attribute, if the attribute was not specified it defaults to "unbound" and Kuryr invokes "unbound" executable, which always fails with the status code 1. This patch also includes the unit tests cover the successful case and the failures. Change-Id: Id3a8288199975d86812c7c1d210c7e11ae58d7b8 Signed-off-by: Taku Fukushima <f.tac.mac@gmail.com>
15 lines
539 B
Plaintext
15 lines
539 B
Plaintext
# The order of packages is significant, because pip processes them in the order
|
|
# of appearance. Changing the order has an impact on the overall integration
|
|
# process, which may cause wedges in the gate later.
|
|
|
|
pbr<2.0,>=1.3
|
|
Babel>=1.3
|
|
Flask>=0.10,<1.0
|
|
jsonschema!=2.5.0,<3.0.0,>=2.0.0
|
|
netaddr>=0.7.12
|
|
oslo.concurrency>=2.3.0 # Apache-2.0
|
|
oslo.serialization>=1.4.0 # Apache-2.0
|
|
oslo.utils>=2.0.0 # Apache-2.0
|
|
python-neutronclient>=2.3.11,<3
|
|
pyroute2>=0.3.10 # Apache-2.0 (+ dual licensed GPL2)
|