From 9d08e805a8889d84ff1076da2373c37057670f23 Mon Sep 17 00:00:00 2001 From: Balazs Gibizer Date: Thu, 7 Jul 2016 16:28:10 +0200 Subject: [PATCH] doc: fix disk=0 use case in flavor doc The 0 value of the disk parameter of the flavor is only meaningfull if the instance is booted from volume as in any other case the instance will use local disk and the scheduler will not be able to select the hosts based on the real image size as that information is not available for the scheduler. Change-Id: I6b3ba2fb323341071eae6b9e9f54ef833fdbaff7 Closes-Bug: #1599787 DocImpact: admin guide --- api-ref/source/parameters.yaml | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/api-ref/source/parameters.yaml b/api-ref/source/parameters.yaml index f72bf124e337..06c274382be1 100644 --- a/api-ref/source/parameters.yaml +++ b/api-ref/source/parameters.yaml @@ -1768,7 +1768,10 @@ flavor_disk: description: | The size of the root disk that will be created in GiB. If 0 the root disk will be set to exactly the size of the image used to - deploy the instance. + deploy the instance. However in this case filter scheduler cannot + select the compute host based on the virtual image size. Therefore + 0 should only be used for volume booted instances or for testing + purposes. flavor_ephem_disk: in: body required: true