yahoo-eng-team team mailing list archive

[Ihar Hrachyshka <1431292@xxxxxxxxxxxxxxxxxx>]

It's up to deployment tool or packaging how to store and pass options to
services. Devstack may build multiple --config-file options to pass to
neutron-server; while distributions may go with a more dynamic approach,
maintaining specific config-dirs per service, and loading everything
inside with --config-dir (like RDO does). It is of no neutron business
to enforce a specific model, or implement any of those approaches for
distributions and even devstack. We will obviously need to make sure
devstack is adopting one of those approaches, and there are already
patches for that from YAMAMOTO
(https://review.openstack.org/#/c/342493/), but it's not correct to
track that kind of adoption as a neutron bug.

** Changed in: neutron
       Status: Confirmed => Invalid

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1431292

Title:
  neutron: use --config-dir for L3/VPN agent

Status in devstack:
  Invalid
Status in grenade:
  Invalid
Status in neutron:
  Invalid

Bug description:
  Since Kilo, neutron has split its advanced services into separate
  repositories that are now not guaranteed to be installed (including
  configuration files like fwaas_driver.ini or vpn_agent.ini). For
  devstack, we dynamically generate list of cli arguments to start
  l3/vpn agent based on which services are enabled in local.conf. This
  approach is not applicable for distributions though that usually ship
  a service manifest with the list of cli arguments hardcoded. Since now
  we cannot assume fwaas_driver.ini or other configuration files that
  may be read by L3 agent are present on the system, we should be more
  flexible.

  oslo.config allows to use --config-dir argument instead of --config-
  file arguments, and populate the directory on demand, based on which
  packages are installed in the system.

  Though devstack is strictly not affected by the problem, we should
  lead by example and adopt unified --config-dir argument to pass l3
  agent configuration via CLI. Distributions are free to adopt the
  approach on their own schedule.

To manage notifications about this bug go to:
https://bugs.launchpad.net/devstack/+bug/1431292/+subscriptions