Microsoft recently released the new Service Provider Foundation for use for Infrastructure-as-a-Service (IaaS) providers with System Center Orchestrator 2012 SP1. Service providers can use Service Provider Foundation technology to offer infrastructure as a service (IaaS) to their clients. If a service provider has a front-end portal for clients to interact with, Service Provider Foundation makes it possible for the clients to access the resources on their hosting provider’s system without making changes to the portal.
This diagram provides high-level view of how Service Provider Foundation operates
The tenant represents a hoster’s customer, and the tenant has assets on the hoster’s system.The tenant has its own administrators, applications, scripts, and other tools.
The hoster provides tenants with the environment, which can include virtual machines. The hoster has an existing front-end portal, which all tenants can use. On the back end, the hoster has a collection of resources, which is called the fabric . The hoster allocates those resources into discrete groups according to the hoster’s needs. Each of these groups is known as a stamp . The hoster can then assign the tenant’s resources to stamps in whatever manner is appropriate to the hoster. The resources may be divided across several stamps, according to the hoster’s business model scheme. Service Provider Foundation makes it possible for the hoster to present a seamless user experience to the tenant by aggregating the data from each stamp and allowing the tenant to use the Service Provider Foundation application programming interfaces (APIs) to access that data.
In Service Provider Foundation, a stamp is a logical scale unit that specifies an instance of a System Center component that is running on a server (a virtual machine). As tenants need additional capacity, additional stamps can be provided. Currently, Service Provider Foundation supports only one type of stamp: one instance of Virtual Machine Manager (VMM) on one server.
Service Provider Foundation does not configure clouds; instead, it manages their resources. Virtual machines are set to clouds, for example, when they are created for VMM or when they are created by the New-SCVirtualMachine cmdlet. We recommend a maximum of 450 virtual machines that are set to one cloud.
The follwing diagram shows the architecture of the Service Provider Foundation
The hoster can have a portal client, which faces the tenant, that provides access to the infrastructure that the hoster has granted. The portal uses an extensible representational state transfer (REST) API to communicate with the web service by using the OData protocol. The claims-based authentication verifies the tenant’s identity and associates it with the user role that the hoster assigns.
Service Provider Foundation uses a database to aggregate the tenant resources, which are managed with Windows PowerShell scripts and Orchestrator runbooks. This makes it possible for the hoster to distribute tenant resources among management stamps in whatever way it decides, while to the tenant the resources are easy to access and appear contiguous.