Welcome to the first part in this series. In this series I am going to walk through the setup of the Service Provider Foundation. This is a key part to using the Windows Azure Pack (which will be posted in a different series).
So let’s begin with an introduction.
Introduction to Service Provider Foundation
Service Provider Foundation is provided with System Center 2012 – Orchestrator, a component of System Center 2012 R2 (and System Center 2012 SP1). Service Provider Foundation exposes an extensible OData web service that interacts with Virtual Machine Manager (VMM). This enables service providers and hosters to design and implement multi-tenant self-service portals that integrate IaaS capabilities available on System Center 2012 R2.
The following information is taken directly from the Architecture Overview TechNet article, found here: http://technet.microsoft.com/en-us/library/jj642897.aspx.
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.
The following illustration provides a 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. Each tenant has their 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.
A stamp in Service Provider Foundation is a logical scale unit designed for scalability that provides an association between a server and its System Center 2012 Service Pack 1 (SP1) components. As tenant demand increases, the hoster provides additional stamps to meet the demand. Note that Service Provider Foundation System Center 2012 SP1 supported only one type of stamp; that is a single server that has Virtual Machine Manager (VMM) installed.
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.
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.
That’s enough starter info, let’s get into preparing the environment and system requirements.