3. Service Offering Examples : 3.1 Service Offering – Basic : 3.1.2 Resource Allocation and Catalogs
   
3.1.2 Resource Allocation and Catalogs
The Pay-As-You-Go resource allocation model enables providers to deliver high levels of flexibility in the way resources are allocated, through published vApp catalogs in vCloud Director. vApp catalogs further enable providers to publish standard application images and pre-defined resource profiles that subscribers can customize, based on a given set of application workload requirements.
The following table provides an example of different sizing combinations that can be included in a vApp catalog with the Basic service offering.
Note: vCPU quantity is based on a multiple of 1GHz, as provided in the example in Table 12. Any quantity of memory or vRAM assigned from Table 13 is reserved at 75%. Subscribers’ ability to select specific quantities of resources, such as vCPU, memory, and storage for a given virtual machine or vApp dynamically may be governed as necessary by the provider. However, providers should first implement a pricing model commensurate with the range of scale for each resource type.
Table 13. Basic Service Offering Catalog Example
vApp Instance Size
vCPU/GHz
OS Bit Mode
Memory1.(MB)
Storage2 (GB)
Bandwidth3 (MBps)
Cost
Extra Small
1.0/1GHz
32/64-bit
500–100,000
10–2,000
Variable
Set by provider
Small
1.0/1GHz
32/64-bit
500–100,000
10–2,000
Variable
Set by provider
Medium
2.0/2GHz
64-bit
500–100,000
10–2,000
Variable
Set by provider
Large
4.0/4GHz
64-bit
500–100,000
10–2,000
Variable
Set by provider
Extra Large
8.0/8GHz
64-bit
500–100,000
10–2,000
Variable
Set by provider
 
1 Virtual memory allocation can be customized for all virtual machine instances from Small through Extra Large. The range provided takes into account the maximum amount of memory that can be allocated per virtual machine or vApp in vCloud Director.
2 Storage allocations may be selected individually and are customizable for all virtual machine instances from Small through Extra Large, based on individual subscriber requirements. The range provided takes into account the maximum amount of storage that can be allocated per virtual machine or vApp in vCloud Director.
3 Ingress/egress bandwidth allocation can be customized for all virtual machine instances from Small through Extra Large, based on individual subscriber requirements and the Internet service capabilities available at the provider.
 
The maximum virtual machine instance size is derived from the maximum amount of vCPU and the maximum amount of memory that a physical host has available in the environment. Although the supported ranges for memory and storage shown in Table 13 indicate configuration maximums for a vSphere and vCloud Director environment, these ranges differ for different providers, given the variance in hosting architectures and physical infrastructure designs.