openstack
/
neutron
Code Issues Proposed changes

Removes redundant "and", "this" and "the" 

This patch removes redundant "and", "this" and "the" in Networking.

Change-Id: I37cf23b197d926b055ea28fca13642e420e3d199
This commit is contained in:
Nguyen Hung Phuong 2016-03-24 11:14:45 +07:00
parent b6b26b8b9a
commit 2870e0a4a2
4 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
doc/source/devref/alembic_migrations.rst
View File

@ -249,7 +249,7 @@ a virtualenv + testdb environment as described in
:ref:`neutron-db-manage-without-devstack`.
Stop the neutron service. Work from the base directory of the neutron (or
sub-project) repo. Check out the master branch and and do ``git pull`` to
sub-project) repo. Check out the master branch and do ``git pull`` to
ensure it is fully up to date. Check out your development branch and rebase to
master.

2
doc/source/devref/network_ip_availability.rst
View File

@ -35,7 +35,7 @@ are:
* Consumed from the subnet's allocation pools (derives total IPs)
This API tracks consumable IPs so network administrators know when their
subnet's IP pools (and and ultimately a network's) IPs are about to run out.
subnet's IP pools (and ultimately a network's) IPs are about to run out.
This API does not account reserved IPs such as a subnet's gateway IP or other
reserved or unused IPs of a subnet's cidr that are consumed as a result of
the subnet creation itself.

4
neutron/agent/linux/dhcp.py
View File

@ -492,7 +492,7 @@ class Dnsmasq(DhcpLocalProcess):
fa:16:3e:8f:9d:65,set:aabc7d33-4874-429e-9637-436e4232d2cd
3) But dnsmasq doesn't have sufficient checks to skip this entry and
pick next entry, to process dhcp IPv4 request.
4) So dnsmasq uses this this entry to process dhcp IPv4 request.
4) So dnsmasq uses this entry to process dhcp IPv4 request.
5) As there is no ip in this entry, dnsmasq logs "no address available"
and fails to send DHCPOFFER message.
@ -501,7 +501,7 @@ class Dnsmasq(DhcpLocalProcess):
http://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/2015q2/
009650.html
So If we reverse the order of writing entries in host file,
So if we reverse the order of writing entries in host file,
so that entry for stateless IPv6 comes first,
then dnsmasq can correctly fetch the IPv4 address.
"""

2
neutron/tests/api/test_subnetpools_negative.py
View File

@ -95,7 +95,7 @@ class SubnetPoolsNegativeTestJSON(test_subnetpools.SubnetPoolsTestBase):
subnet = self.create_subnet(
network, cidr=netaddr.IPNetwork('10.10.10.0/24'), ip_version=4,
gateway=None, client=self.admin_client)
# add the subnet created by admin to the cleanUp because the
# add the subnet created by admin to the cleanUp because
# the base.py doesn't delete it using the admin client
self.addCleanup(self.admin_client.delete_subnet, subnet['id'])
self.assertRaises(lib_exc.BadRequest, self.create_subnet, network,