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
28 lines
839 B
JSON
28 lines
839 B
JSON
{
|
|
"tenant_usage": {
|
|
"server_usages": [
|
|
{
|
|
"ended_at": null,
|
|
"flavor": "m1.tiny",
|
|
"hours": 1.0,
|
|
"instance_id": "1f1deceb-17b5-4c04-84c7-e0d4499c8fe0",
|
|
"local_gb": 1,
|
|
"memory_mb": 512,
|
|
"name": "new-server-test",
|
|
"started_at": "2012-10-08T20:10:44.541277",
|
|
"state": "active",
|
|
"tenant_id": "openstack",
|
|
"uptime": 3600,
|
|
"vcpus": 1
|
|
}
|
|
],
|
|
"start": "2012-10-08T20:10:44.587336",
|
|
"stop": "2012-10-08T21:10:44.587336",
|
|
"tenant_id": "openstack",
|
|
"total_hours": 1.0,
|
|
"total_local_gb_usage": 1.0,
|
|
"total_memory_mb_usage": 512.0,
|
|
"total_vcpus_usage": 1.0
|
|
}
|
|
}
|