From 74e022bbec1a84625417db69a174d224dfdc4cd2 Mon Sep 17 00:00:00 2001 From: Lorin Hochstein Date: Tue, 2 Apr 2013 10:43:53 -0400 Subject: [PATCH] Document how to modify flavors (you can't). Fixes bug 1163356 Change-Id: I8f18b946cc97b2d420662c1f30de6a29180755a9 --- .../openstack-ops/src/ch_ops_user_facing.xml | 190 +++++++++--------- 1 file changed, 99 insertions(+), 91 deletions(-) diff --git a/doc/src/docbkx/openstack-ops/src/ch_ops_user_facing.xml b/doc/src/docbkx/openstack-ops/src/ch_ops_user_facing.xml index 913d77adb7..c9d59e7ced 100644 --- a/doc/src/docbkx/openstack-ops/src/ch_ops_user_facing.xml +++ b/doc/src/docbkx/openstack-ops/src/ch_ops_user_facing.xml @@ -114,16 +114,12 @@
Flavors - Virtual hardware templates are called "flavors" in - OpenStack, defining sizes for RAM, disk, number of cores - and so on. The default install provides a range of five - flavors. These are configurable by admin users (this too - is configurable and may be delegated by redefining the - access controls for - compute_extension:flavormanage in - /etc/nova/policy.json on the - nova-api server). To get a list of - available flavors on your system run: + Virtual hardware templates are called "flavors" in OpenStack, defining sizes for RAM, + disk, number of cores and so on. The default install provides a range of five flavors. + These are configurable by admin users (this too is configurable and may be delegated by + redefining the access controls for compute_extension:flavormanage in + /etc/nova/policy.json on the nova-api server). To get a + list of available flavors on your system run: $ nova flavor-list @@ -137,9 +133,8 @@ | 5 | m1.xlarge | 16384 | 10 | 160 |/| 8 | /| {} | +----+-----------+-----------+------+-----------+\+-------+-\+-------------+ - The nova flavor-create command allows - authorized users to create new flavors. Additional flavor - manipulation commands can be shown with the command + The nova flavor-create command allows authorized users to create new + flavors. Additional flavor manipulation commands can be shown with the command nova help | grep flavor. Flavors define a number of elements: @@ -148,108 +143,121 @@ - + + Column - - - Description - + + + + + Description + + - ID - A unique numeric id. + + ID + + + A unique numeric id. + - Name - a descriptive name. xx.size_name is - conventional not required, though some - third party tools may rely on - it. + + Name + + + a descriptive name. xx.size_name is conventional not required, though + some third party tools may rely on it. + - Memory_MB - Memory_MB: virtual machine memory - in megabytes. + + Memory_MB + + + Memory_MB: virtual machine memory in megabytes. + - Disk - Virtual root disk size in - gigabytes. This is an ephemeral disk the - base image is copied into. When booting - from a persistent volume it is not used. - The "0" size is a special case which uses - the native base image size as the size of - the ephemeral root volume. + + Disk + + + Virtual root disk size in gigabytes. This is an ephemeral disk the + base image is copied into. When booting from a persistent volume it is + not used. The "0" size is a special case which uses the native base + image size as the size of the ephemeral root volume. + - Ephemeral - Specifies the size of a secondary - ephemeral data disk. This is an empty, - unformatted disk and exists only for the - life of the instance. + + Ephemeral + + + Specifies the size of a secondary ephemeral data disk. This is an + empty, unformatted disk and exists only for the life of the + instance. + - Swap - Optional swap space allocation for - the instance. + + Swap + + + Optional swap space allocation for the instance. + - VCPUs - Number of virtual CPUs presented to - the instance. + + VCPUs + + + Number of virtual CPUs presented to the instance. + - RXTX_Factor - Optional property allows created - servers to have a different bandwidth cap - than that defined in the network they are - attached to. This factor is multiplied by - the rxtx_base property of the network. - Default value is 1.0 (that is, the same as - attached network). + + RXTX_Factor + + + Optional property allows created servers to have a different bandwidth + cap than that defined in the network they are attached to. This factor + is multiplied by the rxtx_base property of the network. Default value is + 1.0 (that is, the same as attached network). + - Is_Public - Boolean value, whether flavor is - available to all users or private to the - tenant it was created in. Defaults to - True. + + Is_Public + + + Boolean value, whether flavor is available to all users or private to + the tenant it was created in. Defaults to True. + - extra_specs - Additional optional restrictions on - which compute nodes the flavor can run on. - This is implemented as key/value pairs - that must match against the corresponding - key/value pairs on compute nodes. Can be - used to implement things like special - resources (such as flavors that can only - run on compute nodes with GPU - hardware). + + extra_specs + + + Additional optional restrictions on which compute nodes the flavor can + run on. This is implemented as key/value pairs that must match against + the corresponding key/value pairs on compute nodes. Can be used to + implement things like special resources (such as flavors that can only + run on compute nodes with GPU hardware). + + + How do I modify an existing flavor? + Unfortunately, OpenStack does not provide an interface for modifying flavors, only + for creating and deleting them. The OpenStack Dashboard simulates the ability to + modify a flavor by deleting an existing flavor and creating a new one with the same + name. + +