openstack/openstack-manuals
Code Issues Proposed changes

Use RPC instead of neutron client in metadata agent

Browse Source 
Previously, neutron metadata agent connected to a neutron server via REST 
API using a neutron client. This is ineffective because keystone is then 
fully involved into the authentication process and gets overloaded. The 
neutron metadata agent has been reworked to use RPC by default to connect 
to a server since Kilo release.

Change-Id: Idaf9fbdb33ad3d5f68f40eef54344bffd842f0a0
Closes-Bug: #1386979
This commit is contained in:
Alexander Adamov 2014-12-24 17:35:32 +02:00
parent c0944fe601
commit 6887846a9e
1 changed files with 4 additions and 0 deletions

4
doc/config-reference/networking/section_networking-options-reference.xml

@ -112,6 +112,10 @@ Load-Balancer-as-a-Service related settings.</para>
<para>Use the following options in the
<filename>metadata_agent.ini</filename> file for the Metadata agent.</para>
<xi:include href="../../common/tables/neutron-metadata.xml"/>
<note>
<para>Previously, neutron metadata agent connected to a neutron server via REST API using a neutron client. This is ineffective because keystone is then fully involved into the authentication process and gets overloaded.</para>
<para>The neutron metadata agent has been reworked to use RPC by default to connect to a server since Kilo release. This is a typical way of interacting between neutron server and its agents. If neutron server does not support metadata RPC then neutron client will be used.</para>
</note>
</section>
<section xml:id="networking-options-metering_agent">