In venv --upgrade does nothing good since venv have constraints-bound
versions of everything installed. It does bad thing though: it tries to
upgrade setuptools (they are not mentioned in upstream constraints.txt)
and break further building.
Change-Id: Idc8ae229479fcbf9f524703df2f74e1f83016a7f
* Add Dockerfile template for Opendaylight. ODL image depends
on a base-tools image and additionally includes Java 8.
* Add a new service "opendaylight", configure neutron to use
ml2 opendaylight plugin, configure ovs to be managed by
opendaylight.
Co-Authored-By: Elena Ezhova <eezhova@mirantis.com>
Change-Id: I0125075440d788437672b1980473e8a5ecffd29e
With this patch one can deploy any OpenVSwitch version
specified in ccp.yaml. Corresponding tarball will be
downloaded from http://openvswitch.org/releases/,
compiled and installed
Change-Id: I760512da59258b16749b144e9a980c88526fce54
It speeds up agents significantly halfing the time needed to reestablish
router on L3 agent which means way less external connectivity downtime
during upgrades
Change-Id: I8fb28e9e35f361fc95c90769a2981f3059744178
Images will be built with sources from master branch of
https://github.com/openstack/neutron.git repository by default.
Change-Id: I1087b005e4437978afb5d7ef44bbe82aaa8025f1
Depends-On: I4d91aa8632fcd55735d791300fde475696b435b5
By default neutron openvswitch and dhcp agents try to use 'native'
ovsdb_interface: see I2632b0e21edd61536867a9fc830a45d9899091e4
It's not working from containers properly because tcp:127.0.0.1:6640
is not accessible. This patch adds new config option to control
ovsdb_interface and changes ovsdb connection to socket. Also agents
should be run under root user in order to have access to ovsb socket.
Change-Id: I9cea2fa8a1f94fbf73f31e146a29b3c7dc56e868
Reworked Aleksandr Mogylchenko neutron work to be compatible with application
definition framework. Removed a lot of hand made workarounds.
Change-Id: I674b897dd3f0566a9879024d20afe763ba68a791