scripts/run_kuryr.sh now understands KURYR_USE_UWSGI. If set to "True" (default)
it would attempt to look for uwsgi executable and run kuryr-libnetwork
with it.
Number of spawned threads and processes can be controlled with
KURYR_UWSGI_THREADS and KURYR_UWSGI_PROCESSES env variables.
If uwsgi is not present or KURYR_USE_UWSGI is set to false the script
operates as usual.
Targets bp: deploy-kuryr-libnetwork-api-in-wsgi
Co-Authored-By: Kirill Zaitsev <k.zaitsev@me.com>
Change-Id: I821a78649ad6f07e4709fa343a0e678e4193a068
1. Drop the common(COE agnostic) code such as binding, exceptions
2. Renamed kuryr-libnetwork/kuryr to kuryr-libnetwork/kuryr_libnetwork
3. change default kuryr port from 2377 to 23750
4. Add Kuryr-lib(Kuryr) to requirements.txt:
Kuryr-lib(Kuryr) has also been cleaned to remove libnetwork specific
code(which is active in this repo such as libnetwork api handlers and
test cases). This patch is under review, [1]_. Meanwhile kuryr-lib
dependency is being resolved from external repo [2]. Exacltly same
changes, as present in under review kuryr-lib patch [1], are there on
external repo, [2]
[1] https://review.openstack.org/#/c/336784/
[2] https://github.com/vikaschoudhary16/kuryr/tree/drop_libnet_specific_code
Implements blueprint common-code-drop
Change-Id: If0823791463011dc395cd3390a7f4c187c9c2653
This patch modifies run_kuryr.sh to accept arguments and pass them down
to kuryr/server.py. This enables users to have more flexibility for
launching the Kuryr libenetwork remote plugin as follow.
$ ./scripts/run_kuryr.sh --log-dir . --log-file kuryr.log
Change-Id: I9aa6ea4b58b3485f49689dc46cb6924a3e70b5c9
Signed-off-by: Taku Fukushima <f.tac.mac@gmail.com>
Closes-Bug: #1570253
Adds support for providing a configuration file
for specifying Kuryr configuration options.
Updates the Kuryr scripts to use and if needed,
generate the configuration file.
Implements: blueprint kuryr-config
Change-Id: I6909ef21da13a7137ffff019383be19306f35152
Fix some spelling errors in the scripts and the Vagrant documentation.
Also, add a note about creating the default subnetpool in the Vagrant
documentation.
Change-Id: I13454328d7b4372d6773661b006466f3419c4fe0
Signed-off-by: Kyle Mestery <mestery@mestery.com>
This fix is to add support for checking subnetpool extension support
at Kuryr server startup time. If required extension is found missing,
startup script will exit and kuryr driver server will not start.
Change-Id: I264be36c1b3b23517f4f2ff741f51a5a86b2ae9f
Closes-Bug: #1498393
Now after running: $ sudo python setup.py develop one can start
kury-server by invoking: $ kuryr-server
Change-Id: I992967400b1b128707df7e79cd594eed5688b90f
This patch adds scripts/run_server.py to launch Kuryr with Fask's
development server. etc/kuryr.json is also introduced as the JSON spec
file for the remote driver. scripts/run_kuryr.sh manages them and starts
Kuryr appropriately as the following command:
$ ./scripts/run_kuryr.sh
Change-Id: Ie16a085dbf8fbb7dfdfaca009017ff7223cf1880
Signed-off-by: Taku Fukushima <f.tac.mac@gmail.com>