yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #45870
[Bug 1507950] Re: The metadata_proxy for a network will never be deleted even if it is not needed.
Reviewed: https://review.openstack.org/237618
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=dc0c7b5588409fe64d7680e94f50279ab9ec4043
Submitter: Jenkins
Branch: master
commit dc0c7b5588409fe64d7680e94f50279ab9ec4043
Author: Hong Hui Xiao <xiaohhui@xxxxxxxxxx>
Date: Tue Oct 20 05:31:46 2015 -0400
Delete metadata_proxy for network if it is not needed
Currently, once the metadata_process is created for the network,
it will never be eliminated unless the network is deleted. Even if
user disable the metadata for network and restart dhcp agent, the
metdata proxy for network will still be there. This will waste the
resource of neutron host. This patch will let the dhcp-agent
delete useless metadata_proxy at startup.
Additional functional tests are added to for related scenario.
Change-Id: Id867b211fe7c01a11ba73a5ebc275c595933becf
Closes-Bug: #1507950
** Changed in: neutron
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1507950
Title:
The metadata_proxy for a network will never be deleted even if it is
not needed.
Status in neutron:
Fix Released
Bug description:
Find this issue in a large scale test. Steps to reproduce:
(1) I have about 1000 networks and set enable_isolated_metadata=True firstly.
(2) But then I find the metadata_proxy process is too many, and I want to disable it. So I set the enable_isolated_metadata=False.
(3) restart dhcp-agent
(4) The metdata_proxy are still there.
To eliminate the metadata_proxy process for networks, it looks like
that I can delete the networks or kill the metadata_proxy process
manually(or just restart the host). And, obviously, I want to keep
the networks.
neutron-dhcp-agent should try to kill the useless metadata_proxy to
keep the neutron host clean and with less burden.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1507950/+subscriptions
References