kuryr-libnetwork config generation can produce the wrong output

[Antoni Segura Puimedon]

While generating the config sample with 'tox -egenconfig' works as expected, using plain oslo-config-generator can result in unexpected outcomes. This is due to the fact that oslo does a virtualenv that installs kuryr_libnetwork, so the current oslo.config entrypoints get used. However, with oslo-config-generator, if you have local oslo.config changes and you have also kuryr_libnetwork installed, it would use the old installed entrypoints.

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/364240
Committed: https://git.openstack.org/cgit/openstack/kuryr-libnetwork/commit/?id=7d2133d250fef378d4a827080f53bd118aaa76f6
Submitter: Jenkins
Branch: master

commit 7d2133d250fef378d4a827080f53bd118aaa76f6
Author: Antoni Segura Puimedon <email address hidden>
Date: Thu Sep 1 13:09:54 2016 +0200

    tools: config_file_generation

    With the advent of this tool. Generating the config for local usage and
    packaging will be much simpler.

    Closes-bug: #1619252
    Change-Id: I95f8f0ec76fb8a75153f6dac12c6ec1d2f485e8b
    Signed-off-by: Antoni Segura Puimedon <email address hidden>