From: Sean M. Collins Date: Mon, 2 Nov 2015 19:47:13 +0000 (-0500) Subject: Docs: clarify that AnySubnetRequest is optional X-Git-Url: https://review.fuel-infra.org/gitweb?a=commitdiff_plain;h=8b26e0beb96025cfa4254c31a1129ec3e3e2a46f;p=openstack-build%2Fneutron-build.git Docs: clarify that AnySubnetRequest is optional The phrasing of "may not support" was a little confusing, mostly because I read it as an imperative - "you may not do this" instead of it being "you can do this if you want" Change-Id: Ia4fb87a649f1d4bc312f4ad3bb5c2f48a7b6741b --- diff --git a/neutron/ipam/requests.py b/neutron/ipam/requests.py index 76a6860f1..a2f1f05b5 100644 --- a/neutron/ipam/requests.py +++ b/neutron/ipam/requests.py @@ -121,9 +121,9 @@ class SubnetRequest(object): class AnySubnetRequest(SubnetRequest): """A template for allocating an unspecified subnet from IPAM - A driver may not implement this type of request. For example, The initial - reference implementation will not support this. The API has no way of - creating a subnet without a specific address until subnet-allocation is + Support for this type of request in a driver is optional. For example, the + initial reference implementation will not support this. The API has no way + of creating a subnet without a specific address until subnet-allocation is implemented. """ WILDCARDS = {constants.IPv4: '0.0.0.0',