Seamless cloud abstraction, model and interfaces

An enterprise, as a Cloud Service Consumer (E-CSC), may acquire and consume (off-premises) resources in one or more Public or Community Clouds owned and operated by one or more Cloud Service Providers (CSP). A CSP (as a CSC: S-CSC) may itself consume resources from other CSPs on behalf of an E-CSC. For seamless manageability an E-CSC may want to combine a select set of on-premises (intranet or private Cloud) resources with off-premises Cloud resources to create a Seamless Cloud (SCL). The E-CSC may also include in the SCL a select set of its (branch and DC) sites. Based on the definition an SCL subsumes various categories of Cloud, such as private, public, community, hybrid and inter-Cloud. A CSP can offer a service, which we call the Seamless Cloud service that will facilitate creation, deletion and update of an SCL on-demand. In a multitenant Cloud environment SCLs of each tenant should be isolated from each other end-to-end (from CSC enterprise to on-demand acquired resources in CSP DC). The SCL service will facilitate such isolation. By adding proper QoS capability to the SCL service, a CSP will be able to offer (what we call) Differentiated Quality of Seamless Cloud Services (DQSCS). In this paper we describe abstraction, model and interfaces (CSC to CSP) for SCL. It is expected that the interfaces will be standardized.