Versions Compared

Old Version 8

changes.mady.by.user Eigil Obrestad

Saved on

compared with

New Version 9

changes.mady.by.user Eigil Obrestad

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Code Block
| Name       |  RAM MB|Disk GB| Ephemeral | VCPUs | Is Public | 
+------------+--------+-------+-----------+-------+-----------+
| m1.micro   |    512 |    5  |         0 |     1 | True      |    
| m1.tiny    |   1024 |   10  |         0 |     1 | True      |   
| m1.small   |   2048 |   20  |         0 |     1 | True      |   
| m1.medium  |   4096 |   40  |         0 |     2 | True      |   
| m1.large   |   8192 |   60  |         0 |     4 | True      |   
| m1.xlarge  |  16384 |   80  |         0 |     8 | True      |   
| m1.2xlarge |  32768 |  100  |         0 |    16 | True      |  
| r1.tiny    |  65536 |   40  |         0 |     8 | True      |   
| r1.small   |  98304 |   40  |         0 |    12 | True      |   
| r1.med     | 131072 |   40  |         0 |    16 | True      |   
| r1.large   | 196608 |   40  |         0 |    24 | True      |   
| r1.xlarge  | 262144 |   40  |         0 |    32 | True      |   
+------------+--------+-------+-----------+-------+-----------+

Flavor "Not available"

If a flavor get changed (ex: m1.medium gets more memory) the old flavor will be deleted and a new one will be created. In this case existing VM's would be listed with the flavor "Not Available". This does not really matter, as the quotas is counted correctly, and openstack knows which specs the machine is supposed to have, but if you would like to give the machine a new flavour you should simply resize it to a new flavor. If you resize to a flavor to small to support the machine nothing will happen, so you should not loose any data regardless of which flavor you decide to resize to.