yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #28253
[Bug 1405077] Re: VLAN configuration changes made is not updated until neutron server is restarted
You may need to consider many other configuration parameters like:
[ml2_type_gre]
tunnel_id_ranges = 1:1000
Also, what about if I may need to add type driver and mechanism_driver
in ml2_conf.ini dynamically.
[ml2]
tenant_network_types = vxlan
type_drivers = local,flat,vlan,gre,vxlan
mechanism_drivers = openvswitch,l2population
I feel you need to propose a neutron-specs for the same and ask the
community what needs to be considered for dynamic configurations.
It shouldn't be considered as bug.
** Changed in: neutron
Status: New => 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/1405077
Title:
VLAN configuration changes made is not updated until neutron server is
restarted
Status in OpenStack Neutron (virtual network service):
Invalid
Bug description:
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.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1405077/+subscriptions
References