As we know Service Provider Foundation is the API of VMM. SPF is a web service that can execute tasks against VMM server and WAP just connects to SPF to communicate with VMM so we have the following communication path VMM<->SPF<->WAP. Continue reading “Working in VMM like Service Provider Foundation and Windows Azure Pack”
I would like to introduce a new whitepaper titled “Hybrid Cloud with NVGRE” that is authored by my mates Kristian Nese (MVP) and Flemming Riis (MVP). Daniel Neumann and me are technical reviewers and helpers with some knowledge. Flemming also provided us with the hardware for the lab and this wouldn’t be possible without him.
Please note that this white paper is in its first release.
Once we reach RTM, additional content will be added.
- Site-2-Site VPN
- Self-service and tenants with Windows Azure Pack
You can download the whitepaper from here.
You can leave any comments or questions on Kristian’s blogpost.
System Center 2012 Service Provider Foundation is a new component introduced in SP1. Actually it is still not with status component because it is included in the installation DVD of System Center 2012 Orchestrator SP1. Nevertheless it seems it will key part of System Center Family. And may be the only reason that is not with status component is probably this product will be developed further a lot more.
So what exactly is SPF?
As you probably know System Center Virtual Machine Manager does not have SDK so SPF is the SDK of VMM. This is of course the short explanation. Basically in order to develop web portal that will expose and interact with VMM data you need some programming language so you can write your code and connect to VMM. As VMM is based on PowerShell developers can actually use PowerShell to do that but PowerShell is not a programing language and this is the problem. Of course there are probably a lot more reasons why PowerShell is not the right way. So Microsoft created SPF that is basically API over a Representational State Transfer (REST) web service and this web service actually uses PowerShell to interact with VMM. REST web service is basically the standard for web services. As I am not developer and I might be in mistake for some of the terms but this is the way I understand it from IT Pro perspective. But the capabilities of SPF doesn’t end here. While the other System Center components have their own SDK each (exception is Orchestrator that have REST web service also) that can be used for developing web portals the SDK isn’t so appealing for web developers. For now SPF currently can be connected to VMM only but there are plans to be able to connect SPF to OpsMgr and DPM. With such plans why not in the distant future see also SPF to be able to connect to Service Manager and Configuration Manager.
With this short description let’s see what is Stamp and how we can connect SPF with VMM?
As there are other people who can describe better than me what is Stamp I will just borrow the description from Technet Wiki:
Management Stamps, or stamp, is a new concept introduced with Service Provider Foundation. A stamp represents a unit of virtualized platform infrastructure that includes System Center Virtual Machine Manager, one or more virtual machine hosts and the virtual machines that are managed in the context of the System Center Virtual Machine Manager instance within the stamp. Each stamp also includes the configuration unique to each stamp such as service accounts and user roles.
Stamps must be capable of being monitored; therefore a stamp also includes an instance of System Center Operations Manager. However an instance of System Center Operations Manager may provide monitoring for multiple stamps so there is not necessarily a 1:1 relationship between the number of stamps and instances of System Center Operations Manager.
Put another way a stamp is an instance of System Center that supports a virtualized platform infrastructure up to the maximum number of virtual machine hosts and virtual machines supported by System Center.
With this description in mind you can probably think of that you can use stamps do define different Datacenters. Let’s say have Datacenter in Europe that is managed by one set of System Center components and you have another datacenter in USA that is managed by another set of System Center components. You create two different Stamps for those datacenters so you can connect a different set of System Center to each Stamp. Imagine that you have a global web portal like Windows Azure and from that portal your customers deploy virtual machines. USA customers deploy virtual machines to USA datacenter and Europe customers deploy virtual machines to the Europe datacenter. This distinguishment is based on the Stamps that you have defined.
Now that we know what is Stamp we can create it.
Create the stamp is quite straightforward and it is document in in Technet. It can be done by PowerShell. What is not documented is that you have to import SPF PowerShell module first in order to use the cmlets. So to import open PowerShell as Administrator and execute this:
Than in order to create Stamp you first have to create connection to a VMM server. This can be done by executing this command:
$server = New-SCSPFServer -Name "VMMserver.contoso.com" -ServerType 0
In your case please the FQDN of your VMM server instead of VMMserver.contoso.com. By pointing out Servertype 0 you are indiciating it is VMM sever. 1 is for OpsMgr and 2 is for DPM but for now they cannot be used. Next command creates the stamp:
$stamp = New-SCSPFStamp –Name "Stamp_Europe" –Servers $server
You can put whatever name you want for your Stamp. Besides the name when the Stamp is created a unique identifier is assigned to it.
On the Technet link that I’ve provided you can see how you can create tenant, associate that tenant with a stamp and create Tenant Administrator role in VMM based on that Tenat you’ve created in SPF.
Note that by executing the commands for new server and new stamp you are creating records in the SPF database for them.
Definitely SPF is a interesting software that can be the key for the future of System Center family.