yahoo-eng-team team mailing list archive

[Armando Migliaccio <1405077@xxxxxxxxxxxxxxxxxx>]

Discussion [1] was not really conclusive, but we should look into
providing/refining a mechanism to reload config options via oslo.service
primitives and without API interruption. As commented before, we already
have some integration in place and more can be done, but it can be done
in the context of as separate individual bug fixes.

As for what we currently have captured in config options, I'd say let's
draw a line in the sand and assume that from here on out we consider
more carefully whether certain options are really meant to be statically
or manually configured, taking into consideration how often these
configs may change throughout the life cycle of the system, and whether
they apply across the entire set of plugins that integrate with Neutron.

For this reason, I think it's fair to say that this proposal should be
marked as "won't fix", because a) vlan range is a plugin/deployment
specific config option, and b) with small fixes, it can be reloaded
without API interruption, that can be supported via sys management
tools.

[1]
http://eavesdrop.openstack.org/meetings/neutron_drivers/2015/neutron_drivers.2015-12-15-15.01.log.html

** Changed in: neutron
       Status: Triaged => Won't Fix

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

Title:
  Provide API to manage segmentation ranges

Status in neutron:
  Won't Fix

Bug description:
  This bug was reported like this:

  I changed network_vlan_ranges configuration in configuration file, and I want changes to take effect without restarting the neutron server.
  It may not be a bug, but restarting the networking service itself could lead to some critical processes to stop temporarily.

  As some configurations are subjected to change often, automatic
  reloading of configurations without restarting the whole service may
  be a feasible solution.

  However, I think what this is asking for is this:

  As an administrator I would like to edit my segmentation range via an
  API (for vlan that would be network_vlan_ranges, vni_ranges for
  geneve/vxlan, and tunnel_id_ranges for gre), instead of editing the
  file in place. It would be beneficial for the admin, because if I run
  out of my range whilst my deployment is up and running I don't want to
  cause an operational downtime to expand it.

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