From 60b55ad1d94299d498d5c0edb39b119adc28b68b Mon Sep 17 00:00:00 2001 From: Matt Riedemann Date: Thu, 1 Jun 2017 16:30:48 -0400 Subject: [PATCH] Update server create networks API reference description for tags Artom ruined my day by pointing out that with microversion 2.37 and specifying the enum "auto" for the networks entry in a server create request, you can't also apply a device tag to the port that's auto-created for the server. This change updates the networks API reference parameter description to note that wrinkle since it's not obvious otherwise without looking at the API schema. Change-Id: I1e39aa5a41befb24bb947be060f43f0a96134139 --- api-ref/source/parameters.yaml | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/api-ref/source/parameters.yaml b/api-ref/source/parameters.yaml index 3a572160a424..3411c93d6881 100644 --- a/api-ref/source/parameters.yaml +++ b/api-ref/source/parameters.yaml @@ -3525,8 +3525,9 @@ networks: automatically allocate a network for the project (if possible). *none* tells the Compute 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 or fixed IPs. These are requested as - strings for the networks value, not in a list. See the associated example. + including other network uuids, ports, fixed IPs or device tags. These are + requested as strings for the networks value, not in a list. See the + associated example. in: body required: true type: object