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
14 lines
447 B
XML
14 lines
447 B
XML
<?xml version='1.0' encoding='UTF-8'?>
|
|
<tenant_usages>
|
|
<tenant_usage>
|
|
<tenant_id>openstack</tenant_id>
|
|
<total_local_gb_usage>1.0</total_local_gb_usage>
|
|
<total_vcpus_usage>1.0</total_vcpus_usage>
|
|
<total_memory_mb_usage>512.0</total_memory_mb_usage>
|
|
<total_hours>1.0</total_hours>
|
|
<start>2012-10-08 21:10:51.902640</start>
|
|
<stop>2012-10-08 22:10:51.902640</stop>
|
|
<server_usages/>
|
|
</tenant_usage>
|
|
</tenant_usages>
|