I'm happy with any reasonable choices here, except that to avoid an ugly
API, whatever set of words we pick should be single shortish words (not
multiple words, and preferably not abbreviations) of a grammatically
equivalent type:
compute, storage, networking
work, as do
{computers,guests,instances,servers,machines}, {stores,drives}, networks
but mixing between the groups is less good---I can create 'a drive' or 'a
computer' but not 'a compute'. Whatever happens, we don't want to leave an
illiterate legacy like HTTP's ghastly 'Referer:' header!
| Type | Sub-type | Description |
|---|---|---|
| compute | physical-machine | Physical machine |
| compute | virtual-machine | Virtual machine |
| compute | slice | Virtual private server, container, zone, etc. |
| network | physical-network | Physical network segment |
| network | virtual-network | Virtual network segment |
| network | load-balancer | Load balancer device |
| storage | drive | Hard disk drive |
| storage | snapshot | A snapshot of a storage resource at a point in time |