From f490b73f5f09fe1dceb02c260bcce30cd2e66d4d Mon Sep 17 00:00:00 2001 From: Eric Harney Date: Mon, 26 Mar 2018 11:44:51 -0400 Subject: [PATCH] Remove driver-specific notes from extend api-ref This is not part of the API contract. It should be documented elsewhere as a limitation of the volume driver. Change-Id: I3586853ce7e11150d54cc552863bd3d4f6db197b --- api-ref/source/v3/parameters.yaml | 10 ---------- 1 file changed, 10 deletions(-) diff --git a/api-ref/source/v3/parameters.yaml b/api-ref/source/v3/parameters.yaml index f136ad1d3d6..29a61a383bc 100644 --- a/api-ref/source/v3/parameters.yaml +++ b/api-ref/source/v3/parameters.yaml @@ -1881,16 +1881,6 @@ namespace_1: new_size: description: | The new size of the volume, in gibibytes (GiB). - - .. note:: Some volume backends require the storage to be in some multiple - value rather than incremental. For example, the EMC ScaleIO backend - requires storage in multiples of 8GB. There is a known limitation such - that a request to extend the size of a volume for these backends will be - rounded up to the nearest multiple but the actual physical size of the - storage will not be reflected back in the API for the volume size. For - example, a request to extend the size of an 8GB ScaleIO-backed volume - to 9GB will actually result in 16GB of physical storage but only 9GB will - be reflected in the API and counted for quota usage. in: body required: true type: integer