From 86d24522f6f17f262661ff5a25f31fa49910b200 Mon Sep 17 00:00:00 2001 From: Hongbin Lu Date: Thu, 8 Mar 2018 04:40:47 +0000 Subject: [PATCH] Remove unsupported parameter from api-ref For container create, the 'nets' parameter doesn't support 'auto' and 'none' yet. This patch remove them from api-ref. Change-Id: I988c32e3e9ef998a928f5144e6a11d57f3b16f0d --- api-ref/source/parameters.yaml | 9 --------- 1 file changed, 9 deletions(-) diff --git a/api-ref/source/parameters.yaml b/api-ref/source/parameters.yaml index dc226f03e..57b2ee8df 100644 --- a/api-ref/source/parameters.yaml +++ b/api-ref/source/parameters.yaml @@ -455,15 +455,6 @@ nets: container will not necessarily reflect the order in which they are given in the request. Users should therefore not depend on device order to deduce any information about their network devices. - - The special values *auto* and can be specified for networks. *auto* tells - the Containers service to use a network that is available to the project, - if one exists. If one does not exist, the Containers service will attempt - to automatically allocate a network for the project (if possible). *none* - tells the Containers service to not allocate a network for the instance. - The *auto* and *none* values cannot be used with any other network values, - including other network uuids, ports, fixed IPs or device tags. These are - requested as strings for the networks value, not in a list. in: body type: object port_id: