run_kuryr.sh doesn't accept arugments

Bug #1570253 reported by Taku Fukushima
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
kuryr
Fix Released
Undecided
Taku Fukushima

Bug Description

scripts/run_kuryr.sh doesn't accept arguments and users always have to use the configuration file to configure the behaviour of the Kuryr libnetwork remote plugin. For instance, now Kuryr accepts options for oslo.log such as --log-dir or --log-file and they should be able to be passed to scripts/run_kuryr.sh.

Changed in kuryr:
assignee: nobody → Taku Fukushima (tfukushima)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to kuryr (master)

Reviewed: https://review.openstack.org/305697
Committed: https://git.openstack.org/cgit/openstack/kuryr/commit/?id=45edc61f94687b54e49c0836965415908fb2c628
Submitter: Jenkins
Branch: master

commit 45edc61f94687b54e49c0836965415908fb2c628
Author: Taku Fukushima <email address hidden>
Date: Thu Apr 14 18:15:01 2016 +0900

    Modify run_kuryr.sh to accepts arguments

    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 <email address hidden>
    Closes-Bug: #1570253

Changed in kuryr:
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.