Appendix

Comparison Standard versus Zero-Disk Flavors

Standard Flavors have a persistent Boot Disk integrated in the offering alongside the vCPU, RAM, and IOPS specifications. For a possible expansion of storage, e.g., for data and programs, additional Volumes are simply added to these Flavors. These additional Volumes can be combined from various Volume Offerings that enable different maximum IOPS. Depending on the requirements, one or the other Flavor variant may make more sense.

The following table shows the differences between the Standard Flavors (with Disk) and the Zero-Disk Flavors.

Function	Standard Flavors4	G - Flavors (Zero-Disk)5	Comment
Resize Instance	Yes 1	Yes 2	* Resize Instance by changing Flavor * Standard Flavor only from smaller to larger * VM reboot required
Instance Snapshot	Yes	Yes 3
Volume Snapshot	No	Yes 3
Volume Backup	No	Yes

Further OpenStack Documentation

Horizon

• Horizon User Guide

Client (CLI)

• OpenStack CLI Documentation
• General User Documentation
• CLI Cheat Sheet (Ocata)
• OpenStack Command List

Basic Load Balancing Cookbook

• Load Balancer Cookbook

Footnotes

---

1. Resize Instance of a Standard Flavor includes always CPU, RAM and Root-Disk size ↩

2. Resize Instance of a Zero-Disk Flavor includes only CPU and RAM (larger to smaller allowed). Resize of a Boot-Disk Volume only supported in the next OpenStack Release "Stein" ↩

3. Stored in Images: Disk Format: QCOW2, Size: 0 bytes, plus under Volumes => Snapshot, Size of the Boot-Disk e.g. 50 GB ↩↩

4. with fixed size integrated persistent Boot-Disk ↩

5. with custom sized persistent Boot-Disk Volume ↩