5613818b1d
`root_gb=0` indicates that a disk-resize shouldn't occur which is not something that a default flavor should have enabled. This is especially true of one named 'tiny' since the unresized image could potentially be very large, leading to the unexpected result of a 'tiny' instance consuming a massive amount of disk. The no-resize behavior is still supported, so if it's being relied on for testing, additional, non-default flavors can still be created that enable it. DocImpact Fixes bug 1175383 Change-Id: Ifa5827c7f87dae95214bc4a585adce5735a05d83
6 lines
755 B
XML
6 lines
755 B
XML
<?xml version='1.0' encoding='UTF-8'?>
|
|
<flavor xmlns:OS-FLV-DISABLED="http://docs.openstack.org/compute/ext/flavor_disabled/api/v1.1" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:OS-FLV-EXT-DATA="http://docs.openstack.org/compute/ext/flavor_extra_data/api/v1.1" xmlns:os-flavor-access="http://docs.openstack.org/compute/ext/flavor_access/api/v2" xmlns="http://docs.openstack.org/compute/api/v1.1" name="m1.tiny" ram="512" vcpus="1" swap="" rxtx_factor="1.0" disk="1" id="1" os-flavor-access:is_public="True" OS-FLV-EXT-DATA:ephemeral="0" OS-FLV-DISABLED:disabled="False">
|
|
<atom:link href="http://openstack.example.com/v2/openstack/flavors/1" rel="self"/>
|
|
<atom:link href="http://openstack.example.com/openstack/flavors/1" rel="bookmark"/>
|
|
</flavor>
|