You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

Background:

There are situations where customers are willing to pay a premium to ensure their workloads are not shared with other customers i.e. their VMs are run on hosts that not shared with VMs of other accounts. This could be for security or performance reasons.There are also instances, such as Microsoft’s licensing of desktop class Operating Systems (specifically the absence of a SPLA model) means that traditional enterprise licenses of Windows must be used forcing cloud service providers dedicate hosts to tenants dynamically (so long as each host is for the exclusive use of a particular tenant).

Requirements:

VM service offerings can be created by the CloudStack administrator, which includes a field indicating that instances of the offering should be isolated onto dedicated hosts (per CloudStack account).

VM offerings that don’t indicate the need for dedicated hosts could be run on hosts dedicated to the domain or on hosts shared with other tenants.

The use case that will be satisfied by this requirement is as follows:

Service Provider SP1 operating a public cloud - provides AWS like features directly to end users - some of them might want dedicated hosts, that too for some apps only. In this case, a service offering needs to indicate that the VM needs to be on a host exclusive to this account, if exclusivity is required

COMBINED THIS WITH THE related dedicated resource requirement listed here

  • No labels