openstack/openstack-manuals
Code Issues Proposed changes

Fixed L3 metering agent copy/paste issue

Browse Source 
The L3 metering agent section appears to have been originally copied from
the Metadata agent section, but one of the references to the Metadata
agent may not have been updated.  This fix updates the reference.

Some double spacing that appeasr to have been added during the copy/paste
has been reduced to single spacing as well.

Change-Id: Iaa4d4143a9b8cfb0dc035ddeb5e9415c3c99d909
Closes-Bug: #1606059
This commit is contained in:
Matt McEuen 2016-07-24 15:20:46 -05:00
parent 2c0c7c06f3
commit 1ad7ff6c61
1 changed files with 3 additions and 3 deletions

6
doc/networking-guide/source/config-ml2-plug-in.rst

@ -340,7 +340,7 @@ The DHCP agent is responsible for :term:`DHCP` (Dynamic Host Configuration
Protocol) and RADVD (Router Advertisement Daemon) services. It requires a
running L2 agent on the same node.
Configuration for the DHCP agent is typically done in the
Configuration for the DHCP agent is typically done in the
``dhcp_agent.ini`` configuration file. Make sure that on agent start
you pass this configuration file as argument.
@ -353,7 +353,7 @@ Metadata agent
The Metadata agent allows instances to access cloud-init meta data and user
data via the network. It requires a running L2 agent on the same node.
Configuration for the Metadata agent is typically done in the
Configuration for the Metadata agent is typically done in the
``metadata_agent.ini`` configuration file. Make sure that on agent start
you pass this configuration file as argument.
@ -366,7 +366,7 @@ L3 metering agent
The L3 metering agent enables layer3 traffic metering. It requires a running L3
agent on the same node.
Configuration for the Metadata agent is typically done in the
Configuration for the L3 metering agent is typically done in the
``metering_agent.ini`` configuration file. Make sure that on agent start
you pass this configuration file as argument.