Rick Harris 5613818b1d 'm1.tiny' now has root_gb=1 ... `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		2013-05-16 23:18:22 +00:00
..
server-post-req.json	Add api samples to simple tenant usage extension	2012-10-11 00:59:07 -04:00
server-post-req.xml	Add api samples to simple tenant usage extension	2012-10-11 00:59:07 -04:00
server-post-resp.json	Add api samples to simple tenant usage extension	2012-10-11 00:59:07 -04:00
server-post-resp.xml	Add api samples to simple tenant usage extension	2012-10-11 00:59:07 -04:00
simple-tenant-usage-get-specific.json	'm1.tiny' now has root_gb=1	2013-05-16 23:18:22 +00:00
simple-tenant-usage-get-specific.xml	'm1.tiny' now has root_gb=1	2013-05-16 23:18:22 +00:00
simple-tenant-usage-get.json	'm1.tiny' now has root_gb=1	2013-05-16 23:18:22 +00:00
simple-tenant-usage-get.xml	'm1.tiny' now has root_gb=1	2013-05-16 23:18:22 +00:00